On 8/10/07, Anders F Björklund <afb@algonet.se> wrote:
>
> After first getting "bitten" in RPM 4.4.9 by the fact that
> ${prefix}/var/spool/repackage wasn't created by the install,
> but was still *mandatory* for the default package erasure
> to work (since %_repackage_all_erasures defaults to 1 now);
>
> 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.
Cheers...james
Received on Fri Aug 10 21:21:55 2007