---------- Forwarded message ---------- From: Nelson Marques <nmo.marques@gmail.com> Date: Fri, Apr 15, 2011 at 7:49 PM Subject: Re: [opensuse-packaging] Re: On Python packages naming To: Jan Matejek <jan.matejek@novell.com> Hi, As far as I understood and it was pointed to me, python extensions, modules, bindings and friends are to be packaged as python-$whatever, while user applications are not to follow that and to be packaged by their name. I would love to see a more friendlier solution, but I don't find the current way also too complex... as long as the packager knows what he is packaging it should be cake... Yeah, I know the nasty RPMLINT warning, but that can either be worked with rpmlint or it really doesn't hurt to be ignored. Most people will be aware of it's meaning and will why it's there (a user application). It will be far more complicated to identify python modules/extensions following other ways... By the way, I might be wrong, but isn't PyEnchant already a part of python or python-xml ? NM On Fri, Apr 15, 2011 at 7:27 PM, Jan Matejek <jan.matejek@novell.com> wrote:

Dne 15.4.2011 17:02, Sascha Peilicke napsal(a):

...

On Friday 15 April 2011 16:13:49 İsmail Dönmez wrote:

...

On Friday, April 15, 2011 04:13:00 PM Andreas Jaeger wrote:

...

On Friday, April 15, 2011 03:46:34 PM Sascha Peilicke wrote:

...

Hi guys,

currently most Python packages in the Build Service are inconsistently named. For instance, upstream 'pyenchant' is named python-enchant, 'Cheetah' is named python-cheetah. There are plenty of other examples. I'd like to propose a different scheme (much like our Ruby and Perl packages):

* Python application packages are named like $UPSTREAM_NAME * Python libraries are named python-$UPSTREAM_NAME

Sascha, what are other projects like Debian, Ubuntu and Fedora doing? Let's talk with other rpm based distros on whether we can implement the same scheme - this make cross-distribution building much saner...

This is a good idea, python-python-twitter looks really counter-intuitive though, maybe there should be an exception if the package already has a python- prefix.

Yeah, if it's 'python-' we may want to drop that prefix. This seems to be the case for our Perl and Ruby packages, too.

+1 to this -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org

-- Nelson Marques /* As cicatrizes lembram-nos de onde estivemos, mas não ditam para onde vamos */ -- Nelson Marques /* As cicatrizes lembram-nos de onde estivemos, mas não ditam para onde vamos */ -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-packaging+help@opensuse.org