URGENT: Naming conflict in Cyrus-IMAP 2.2 vs. leafnode 1.9

Henrique de Moraes Holschuh hmh at debian.org
Mon May 3 14:52:53 EDT 2004

Debian has been renaming any potential offenders (reconstruct, master, etc)
by prefixing them with "cyr" for a VERY long time now.  I will do so for
Cyrus 2.2 as well, for every potential offender that has not a "cyr" or "cyr_"
prefix already...

I don't know what to do with borderline stuff like mbpath, though.  I might
end up prefixing everything with "cyr" for completeness.  The services
aren't a problem, since I package them in a directory of their own.

I document this throughoutly on the READMEs, and it is an already more or
less well known fact that such renames are sometimes done in Cyrus

So fetchnews would just be one more player in this rename dance.

On Mon, 03 May 2004, Rob Siemborski wrote:
> quite successfully.  I don't see why this is significantly any different
> (especially when it can be delt with, minimally, in the way that FreeBSD
> does).

How does FreeBSD deal with this? I'm curious :)

> I appreciate the problems with the namespace conflict, but if we were to
> do this for all of our binaries every time a conflict was discovered, I

There is one answer for that, which is to prefix everything that is not a
service with cyr_ for 2.3, and have all services installed in a separate
directory (which is already possible, but it is not strongly suggested or
anything).  After all, services are to be run by master, only...

  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

More information about the Info-cyrus mailing list