On Tue, 10 Nov 2009 16:50:30 -0500 (EST) "Benjamin R. Haskell" <[email protected]> wrote: > > --skip-phase tidyup > > Hmm. Thanks. That'll do for this case. > > Is there no way to influence it via bashrc, though? (I assumed > correctly that altering PALUDIS_OPTIONS doesn't have an effect there.)
Correct, can't be done. > I like keeping the build directory around whenever I build anything > matching */*::local, for example. (i.e. things for which I get into > an install-tweak_ebuild-repeat cycle.) It'd be fairly easy to introduce a few build_options to deal with this kind of thing (probably one to avoid cleaning up temporary files, and one that guarantees a non-destructive merge). Dunno if there's sufficient interest to make it worth it. > ...oops... And on second glance, what I'm looking for apparently > isn't part of 'tidyup' anyway. I wanted to keep the > /var/log/paludis/*-hilite*.out file. Any way to do that if the > install succeeds? Not a documented way. The output management framework supports it, but I'm not done tinkering with how all that works yet, and there will be changes to the formats of the files involved in the future. Rather than handle a messy upgrade process, I've just chosen not to tell people who can't work it out from the source how to tinker with all that. -- Ciaran McCreesh
signature.asc
Description: PGP signature
_______________________________________________ paludis-user mailing list [email protected] http://lists.pioto.org/mailman/listinfo/paludis-user
