Bug 59606 - RFE: Emit warning when "rpm -ba" is used
Summary: RFE: Emit warning when "rpm -ba" is used
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: rpm   
(Show other bugs)
Version: 1.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeff Johnson
QA Contact:
URL:
Whiteboard:
Keywords: FutureFeature
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-02-11 02:49 UTC by R P Herrold
Modified: 2008-05-01 15:38 UTC (History)
0 users

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-02-11 02:49:08 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description R P Herrold 2002-02-11 02:49:03 UTC
It has been over 20 months now.

  https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=13277

And as is apparent from the rpm-list traffic, and the problems developers
encounter who are new to RPM, the message in the man page:

   Use: rpmbuild -ba

is not being heard.  This is causing 'mysterious' failures. Please consider
adding (I take it in the popt expansions):

   $ rpm -ba wheatever.spec
   "Warning: rpm -ba" is deprecated - Use: "rpmbuild -ba"

to pound the point in and prepare the way to un-overburden 'rpm'.

Comment 1 Jeff Johnson 2002-02-11 15:52:06 UTC
The popt interface would need to change incompatibly
to emit the warning, as the rpm executable is not supposed
to know it's helpers, that's what a popt alias is for.

The fix -- when I am permitted -- is gonna be to rip out
the popt alias legacy compatibility crap. Users will invoke
rpmbuild when building, otherwise rpm itself. Continuing to
fiddle around with "legacy compatibility" and better warnings
etc doesn't even begin to touch the root of the problem:

	The build modes have moved out of the /bin/rpm
	executable, and they're not going back again.


Note You need to log in before you can comment on or make changes to this bug.