On Mon, 6 Mar 2006 01:09:58 +0000 Marius Mauch <[EMAIL PROTECTED]> wrote: | > Hm, that one needs clarifying. Do we even want it to be based upon | > inherit path rather than filesystem path? | | If this is intended to replace deprected files one day I think we want | (implementation isn't the problem one way or the other btw).
Except... That deprecated isn't inherited, and with good reason. There's been at least one instance where we've wanted to move users onto one of several subprofiles of a profile. I forget whether it was actually used in the end and I'm too lazy to check, but the way this was going to be handled was by deprecating the parent profile with a message telling the users to select the correct subprofile. | > | As any substantial change results in a new news item should there | > | be an optional "Obsoletes" header? Could be used to make sure | > | people only see the most current version (without relying on | > | rsync to wipe deleted files). | > | > I'd really rather not. That makes writing clients a lot harder. | | It does? Just requires them to parse news items upfront and then | remove all items matched by an Obsoletes header from the processing | queue. Doesn't seem so tricky. That's exactly it. It requires a client to look at and be able to handle all other news items just to read a single item. -- Ciaran McCreesh : Gentoo Developer (Wearer of the shiny hat) Mail : ciaranm at gentoo.org Web : http://dev.gentoo.org/~ciaranm
signature.asc
Description: PGP signature
