it`s realy strange that there need to be _GUIDELINES_ to fix bugs in the specfiles.
Bugs that should just be fixed in RPM itself.
@Jesse Keating
you say that there are far bigger issues. why not just fix all the current rpm bugs and release a fully patched version? than from a good working version you can start adding in the bigger stuff.. whatever that might be.
There are far bigger issues that
our RPM team are trying to tackle.
Like?
2007/4/10, Tom spot Callaway <tcallawa@xxxxxxxxxx>:
On Mon, 2007-04-09 at 23:44 -0400, Tom Lane wrote:
> "Tom \"spot\" Callaway" < tcallawa@xxxxxxxxxx> writes:
> > It is important to properly prepare the BuildRoot in the %install
> > section of your package before it is used. Every Fedora package MUST
> > have an %install section that begins with either:
> > %install
> > rm -rf %{buildroot}
> > or
> > %install
> > rm -rf $RPM_BUILD_ROOT
>
> Just outta curiosity, why is it not considered an RPM bug that every
> specfile has to take care of this detail? Seems like it'd be trivial
> to fix it once instead of memorializing this oversight in every package
> till the end of time.
This is absolutely an RPM bug. However, since RPM is riddled with bugs,
we can either hope they get fixed, or work around them with guidelines
until they get fixed.
Historically, filing bugs against items like this have been futile since
it would "change RPM's behavior", as broken as it may be.
I've personally had my fun with trying to submit RPM patches, and I'm
not interested in that sort of pain again. If you're motivated to get
this fixed in Fedora's RPM, please, feel free. We'll be happy to remove
any guidelines made obsolete by bugfixes.
~spot
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
-- fedora-devel-list mailing list fedora-devel-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-devel-list
