This (for better or worse) is used by people bundling up binary components into RPM packages.
If you change the behavior.. you'll force them to have to do a copy in the %install (or before), instead of just providing a %files. --Mark Tom 'spot' Callaway wrote: > On Thu, 2007-02-15 at 14:42 -0500, Bill Nottingham wrote: >> Tom 'spot' Callaway ([EMAIL PROTECTED]) said: >>> On Thu, 2007-02-15 at 14:35 -0500, Bill Nottingham wrote: >>>> Paul Nasrat ([EMAIL PROTECTED]) said: >>>>> Could you supply an updated patch in a new thread. >>>> Will do. Note that setting it in the macros by default means that >>>> the behavior will change on any package that includes BuildRoot >>>> (as the macro value will be used over that.) >>> Is this really what we want? >>> >>> IMHO, it should be: >>> >>> rpm's default is trumped by system wide macro is trumped by local spec >>> defines. >> At this point, I'll settle for whatever upstream wants - what was >> suggested is that rpm defaults to none to preserve compatibility, and >> you can set it in a system-wide macro. > > But that's patently dangerous. > > When do we EVER want the default buildroot to be none (which equates > to /) ? There's never a good case in my mind for that. > > ~spot > > _______________________________________________ > Rpm-maint mailing list > [email protected] > https://lists.rpm.org/mailman/listinfo/rpm-maint _______________________________________________ Rpm-maint mailing list [email protected] https://lists.rpm.org/mailman/listinfo/rpm-maint
