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

2004-05-10 Thread Marco Colombo
[recipient list purged] On Mon, 3 May 2004, Rob Siemborski wrote: > On Mon, 3 May 2004, Henrique de Moraes Holschuh wrote: > > > > 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

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

2004-05-04 Thread Rob Siemborski
On Sun, 2 May 2004, Matthias Andree wrote: > Given that Cyrus-IMAPd 2.2.3 has been released only this January, and > has not yet been adopted by all distributions (most are still shipping > Cyrus-IMAPd 2.1.N), renaming fetchnews to cyr_fetchnews would have > little impact _now_ but be a major inc

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

2004-05-04 Thread Rob Siemborski
On Mon, 3 May 2004, Henrique de Moraes Holschuh wrote: > > 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 w

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

2004-05-03 Thread Henrique de Moraes Holschuh
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 m