Re: [kde] setting an /opt precedent
>>"Jim" == Jim Gettys <firstname.lastname@example.org> writes:
Jim> My point is that often, in these large systems, you need both
Jim> systems in parallel, simultaneously, both for developers and users.
Jim> You can't just say: "we'll only have one version of nautilus installed
Jim> at once", for example; people, particularly on shared systems will need
Jim> both versions available simultaneously.
We can do that, I guess, without resorting to /opt
Jim> And I think Debian owes the KDE packaging folks some guidance on
Jim> if not /opt, then where....
KDE folks do not have to follow Debian policy, so they can go
right ahead and put things into /opt.
We have access to mechanisms that the KDE folks do not. (I am
talking about the alternatives stuff, the whole emacsen mechanism,
perl policy). We'll come up with a way to handle this. The KDE folks
have to come to terms with their own issues (unless they default to
using Debgian as the preferred OS, which we'll welcome with open
When neither their poverty nor their honor is touched, the majority
of men live content. Niccolo Machiavelli
Manoj Srivastava <email@example.com> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C