Lars Wirzenius writes (Re: Name clash in prospective package ):
...
For instance, there's no guarantee that /usr/local/lib exists, or that
the admin wants it to exist, or that it won't cause any trouble if it
does exist. I can't think of anything that would break, but admins
are allowed to do
Lars Wirzenius writes (Re: Name clash in prospective package ):
Ian Jackson:
The point of not putting things in /usr/local isn't, as I see it, so
Well, I'm not in full agreement, but it's not important enough.
Fair enough.
I propose the following resolution:
I can live with the what you
I think it would be better to change the name of the Mercury Compiler to
something like mercc.
The reasons are:
1) Minimal disturbance to current debian users. They now use mc to
launch Midnight Comander.
2) Seniority (?). Midnight Commander took the name first (within
Debian,
Not completely alone---I'd prefer prompting about /usr/local. Why?
Because /usr/local on all our machines here (not just debian) is an
nfs-mounted directory, and typically mounted readonly or root-squash
so that I know nothing on the client machines is going to be able to
diddle with it.
It seems obvious from the responses I've had, that one of the programs needs
to be renamed (no other solutions were presented, and, frankly, I can't
really think of one that won't cause problems). If we assume this is the
case, it is fairly obvious which one should be renamed: the Mercury one.
BCW == Brian C White [EMAIL PROTECTED] wrote:
BCW I don't see a problem with packages creating directories and
BCW other necessary framework in /usr/local. In some cases, this can
BCW be quite complex and without which it isn't possible for there to
BCW be local extensions.
Besides, it let the
6 matches
Mail list logo
