Re: Bug#698164: mandate unique package names in Debian Java policy

2013-01-16 Thread Daniel Pocock
On 16/01/13 09:05, Eric Lavarde - Debian wrote: > Hi, > > Daniel Pocock said: >>> B. I doubt that such a badly named package would be of enough interest / >>> quality for Debian packaging (but I might be wrong, I don't know any >>> example) >> >> There are examples like this. It has been argued

Re: Bug#698164: mandate unique package names in Debian Java policy

2013-01-16 Thread Eric Lavarde - Debian
Hi, Daniel Pocock said: >> B. I doubt that such a badly named package would be of enough interest / >> quality for Debian packaging (but I might be wrong, I don't know any >> example) > > There are examples like this. It has been argued by some developers > that to compile using some toolchains (

Re: Bug#698164: mandate unique package names in Debian Java policy

2013-01-15 Thread Sylvestre Ledru
On 14/01/2013 21:25, Tomasz Muras wrote: > On 01/14/2013 09:16 PM, Eric Lavarde wrote: >> Hello, >> >> On 14/01/13 19:48, Daniel Pocock wrote: >>> A few projects exist without following this convention, and sooner or >>> later somebody may try to package one of them. >>> >>> According to the Java L

Re: Bug#698164: mandate unique package names in Debian Java policy

2013-01-14 Thread Tomasz Muras
On 01/14/2013 09:16 PM, Eric Lavarde wrote: Hello, On 14/01/13 19:48, Daniel Pocock wrote: A few projects exist without following this convention, and sooner or later somebody may try to package one of them. According to the Java Language Specification, using a domain name is a "suggested conv

Re: Bug#698164: mandate unique package names in Debian Java policy

2013-01-14 Thread Eric Lavarde
Hello, On 14/01/13 19:48, Daniel Pocock wrote: A few projects exist without following this convention, and sooner or later somebody may try to package one of them. According to the Java Language Specification, using a domain name is a "suggested convention" and not a mandatory obligation. None