Re: "goals" for slink: FHS
Hi,
>>"Raul" == Raul Miller <rdm@test.legislate.com> writes:
Raul> I suppose another option is to upgrade support programs only
Raul> for slink (making it a slink requirement that any program with
Raul> a reference to /usr/man also supports /usr/share/man in the
Raul> same fashion, and similarly for info, and doc (dwww)).
I think this should also be back-ported to hamm-update/2.0r1.
Doing s would make transition easier, and also make it possible for
people running stable to try out a Slink package.
Raul> After slink we could start moving the referenced files. We'd
Raul> then insist that people must upgrade everything to slink before
Raul> upgrading beyond that point. [Or that they upgrade everything
Raul> in their distribution.]
I Object strongly!!! Incremental upgrades is what we have
promised our users forever. If I am running a mission critical
server, I want to stay with Hamm. But if there is a bugfix enhanced
apache relerase, I want to use that from Slink, if it has things I
require. However, I do not want to risk the stability of the
system. I should be able to do this. Nothing should force users to
upgrade all or else!!
We should make it possible for people on 20r1 to be able to
upgrade single packages to Slink. That is why 2.0r1 has to have
patched Slink-compatible versions of the programsthat need to read
/usr/share/{doc,man,info} as well.
manoj
--
If you're not careful, you're going to catch something.
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: