On Wednesday 20 June 2007, Chris Gianelloni wrote: > On Wed, 2007-06-20 at 18:50 -0400, Mike Frysinger wrote: > > > Well, I often use quickpkg when I want to try a new version of a > > > package (I quickpkg the currently installed one.. and I want to keep > > > all the config files). Then I emerge the new one, and I absolutely want > > > to be able to restore the config files if I want to revert to an older > > > version, either because they have been broken by the pkg_postinst or > > > something else. I still haven't heard a good reason to change anything > > > thats not the printing in quickpkg. > > > > i didnt say i was going to be disallowing this, i said i'd be making it > > no longer the default behavior ... what you want to do will still be > > perfectly possible > > Is quickpkg a candidate for FEATURES? I'd much prefer this be able to > be controlled by a configuration file (and overridden on the command > line) so I don't have to remember to put --iamsureidontcareaboutsecurity > or whatever on the command line every time.
there's a new quickpkg default opts ala emerge default opts env var -mike
signature.asc
Description: This is a digitally signed message part.
