On Tue, Feb 26, 2002 at 05:32:37PM -0700, Jason Gunthorpe <[EMAIL PROTECTED]> was heard to say: > IMHO you should take the approach that the user of aptitude should expect > that such changes are permanent and write it to the preferences file. It > was intended to be written by a GUI to retain exactly these sorts of > things.
Hm, ok. I'll take a serious look at it sometime. Clobbering the whole file isn't nice, but maybe I can use a "## BEGIN APTITUDE SETTINGS" approach. (although that means they can't edit the whole file from aptitude) > > in; however, no-one has yet stepped forward to suggest a solution to the > > issue of "what do I do when there are multiple available releases?" > > Show the newest release in the column I'd say. Are releases always well-ordered? I guess I could hack this for "unstable", "testing", and "stable", but what about "progeny" (they had their own Release file, did't they?) or "bobsrandomarchive"? Daniel -- /-------------------- Daniel Burrows <[EMAIL PROTECTED]> -------------------\ | "A game which, from the viewpoint of the other players (ie, everyone) might | | be compared to playing poker with blank cards, for infinite stakes, with a | | Dealer who won't tell you the rules and who /smiles all the time/." | | -- Terry Pratchett, _Good Omens_ | \---------------------- A duck! -- http://www.python.org ---------------------/
