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