Re: Python 2/3 package naming

2016-12-07 Thread Adam Williamson
On Wed, 2016-12-07 at 20:51 +0100, Jakub Jedelsky wrote: > On Wed, Dec 07, 2016 at 09:09:48AM -0800, Adam Williamson wrote: > > On Wed, 2016-12-07 at 16:26 +0100, Vít Ondruch wrote: > > > Generally it is bad idea to differ from the name platform package > > > manager uses. > > > > The packages

Re: Python 2/3 package naming

2016-12-07 Thread Jakub Jedelsky
On Wed, Dec 07, 2016 at 09:09:48AM -0800, Adam Williamson wrote: > On Wed, 2016-12-07 at 16:26 +0100, Vít Ondruch wrote: > > Generally it is bad idea to differ from the name platform package > > manager uses. > > The packages *must* by policy Provide python2-vertica-python and >

Re: Python 2/3 package naming

2016-12-07 Thread Adam Williamson
On Wed, 2016-12-07 at 16:26 +0100, Vít Ondruch wrote: > Generally it is bad idea to differ from the name platform package > manager uses. The packages *must* by policy Provide python2-vertica-python and python3-vertica-python respectively, but they don't absolutely have to be named that way. The

Re: Python 2/3 package naming

2016-12-07 Thread Vít Ondruch
Dne 7.12.2016 v 14:46 Neal Gompa napsal(a): > On Wed, Dec 7, 2016 at 8:13 AM, James Hogarth wrote: >> On 7 December 2016 at 13:07, Jakub Jedelsky wrote: >>> On Wed, Dec 07, 2016 at 11:48:55AM +0100, Igor Gnatenko wrote: On Wed, Dec 7,

Re: Python 2/3 package naming

2016-12-07 Thread Zbigniew Jędrzejewski-Szmek
On Wed, Dec 07, 2016 at 08:46:22AM -0500, Neal Gompa wrote: > Unless there's some kind of naming conflict, I'd call it pythonX-vertica. +1 (srpm python-vertica, and then python2-vertica, python3-vertica) Zbyszek ___ devel mailing list --

Re: Python 2/3 package naming

2016-12-07 Thread Neal Gompa
On Wed, Dec 7, 2016 at 8:13 AM, James Hogarth wrote: > On 7 December 2016 at 13:07, Jakub Jedelsky wrote: >> On Wed, Dec 07, 2016 at 11:48:55AM +0100, Igor Gnatenko wrote: >>> On Wed, Dec 7, 2016 at 10:48 AM, James Hogarth

Re: Python 2/3 package naming

2016-12-07 Thread James Hogarth
On 7 December 2016 at 13:07, Jakub Jedelsky wrote: > On Wed, Dec 07, 2016 at 11:48:55AM +0100, Igor Gnatenko wrote: >> On Wed, Dec 7, 2016 at 10:48 AM, James Hogarth >> wrote: >> > On 7 December 2016 at 09:39, Jakub Jedelsky

Re: Python 2/3 package naming

2016-12-07 Thread Igor Gnatenko
On Wed, Dec 7, 2016 at 2:07 PM, Jakub Jedelsky wrote: > On Wed, Dec 07, 2016 at 11:48:55AM +0100, Igor Gnatenko wrote: >> On Wed, Dec 7, 2016 at 10:48 AM, James Hogarth >> wrote: >> > On 7 December 2016 at 09:39, Jakub Jedelsky

Re: Python 2/3 package naming

2016-12-07 Thread Jakub Jedelsky
On Wed, Dec 07, 2016 at 11:48:55AM +0100, Igor Gnatenko wrote: > On Wed, Dec 7, 2016 at 10:48 AM, James Hogarth > wrote: > > On 7 December 2016 at 09:39, Jakub Jedelsky > > wrote: > >> Hi there, > >> > >> I'm maintainer of vertica-python

Re: Python 2/3 package naming

2016-12-07 Thread Igor Gnatenko
On Wed, Dec 7, 2016 at 10:48 AM, James Hogarth wrote: > On 7 December 2016 at 09:39, Jakub Jedelsky wrote: >> Hi there, >> >> I'm maintainer of vertica-python package and want to add support for >> python3, but I'm a little bit lost in naming.

Re: Python 2/3 package naming

2016-12-07 Thread James Hogarth
On 7 December 2016 at 09:39, Jakub Jedelsky wrote: > Hi there, > > I'm maintainer of vertica-python package and want to add support for > python3, but I'm a little bit lost in naming. > > I named package as a upstream 'vertica-python', because (if I remember > correctly)

Python 2/3 package naming

2016-12-07 Thread Jakub Jedelsky
Hi there, I'm maintainer of vertica-python package and want to add support for python3, but I'm a little bit lost in naming. I named package as a upstream 'vertica-python', because (if I remember correctly) naming guidelines told, that if upstream has 'python' in the name it should stay there