Mailinglist Archive: opensuse-buildservice (354 mails)

< Previous Next >
Re: [opensuse-buildservice] python naming standard?
  • From: "Claes Bäckström" <claes.backstrom@xxxxxxxxx>
  • Date: Thu, 1 Feb 2007 19:38:18 +0100
  • Message-id: <f7ddb9110702011038i2b98e700s3b154071da992850@xxxxxxxxxxxxxx>
On 2/1/07, Michael Schroeder <mls@xxxxxxx> wrote:
On Thu, Feb 01, 2007 at 06:46:47PM +0100, Marcus Hüwe wrote:
> On 2007-02-01 18:15:19 +0100, andreas.hanke@xxxxxxxxxxxxxx wrote:
> > Marcus Rueckert wrote:
> >
> > > python-<originalpackagename>
> > >
> > > python-pychm in your case
> >
> > Really? I thought the convention was
> >
> > python-<importablepackagename>
> >
> No. According to the suse package conventions it is:
> python-XXX (XXX means original module name).
>
> See http://forge.novell.com/modules/xfcontent/private.php/library/SUSE%20Package%20Conventions/spc.pdf
> for more information.

Sounds to me like the package conventions are wrong. Just have a look
at our python packages...


To be honest I didn't get any wiser.
Both ways sounds sane. But my main problem is still there. Which
should I choose?

python-pychm or python-chm

Warm Regards,
Claes Backstrom
< Previous Next >
Follow Ups