RPM Community Forums

Mailing List Message of <rpm-devel>

Re: /var/spool/repackage vs %{_topdir}/TR

From: Anders F Björklund <afb@algonet.se>
Date: Fri 10 Aug 2007 - 23:23:42 CEST
Message-Id: <9f3a44b3eb71ccd6dd304faa4107d3e9@algonet.se>
Jeff Johnson wrote:

>>> When upgrading to RPM 5.0 CVS I now find that it has been
>>> moved to the development directory (%{_topdir}) instead...
>>> Although I do agree that hardcoding /var/spool/repackage
>>> is bad, I had placed %{_topdir} in the developer category.
>>>
>> That sounds like a bad place to me.  Personally though I simply put it
>> where I want it to be based on storage available.  Your right though
>> that is a bad default.   The old one as far as defaults go at least
>> made sense.
>>
>
> The choice _IS_ a bad place for default, but is certainly configurable.

I'll probably change it back to my previous, 
@prefix@/var/spool/repackage
(but I'll wait for the rationale from cse, for keeping TR in the 
_topdir)

> The default will almost certainly get changed. There's certainly lots 
> of
> reasons _NOT_ to change locations arbitrarily in order to "drop in" on
> new ports with alternative prefixes.

I wonder if I shouldn't turn %_repackage_all_erasures off too, or if it
offers any advantages I'm unaware of to the casual RPM user on Mac OS X 
?

--anders
Received on Fri Aug 10 23:23:43 2007
Driven by Jeff Johnson and the RPM project team.
Hosted by OpenPKG and Ralf S. Engelschall.
Powered by FreeBSD and OpenPKG.