From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Package naming convention [was: Re: [PATCH 1/2] scanpypi: new utility]
Date: Sat, 8 Aug 2015 12:59:25 +0200 [thread overview]
Message-ID: <20150808125925.66e32bfb@free-electrons.com> (raw)
In-Reply-To: <55A66B64.5090603@mind.be>
Dear Arnout Vandecappelle,
On Wed, 15 Jul 2015 16:17:08 +0200, Arnout Vandecappelle wrote:
> Good question, we indeed have no real convention of what the buildroot name is
> for packages with weird characters.
>
> Actually, we do: keep the upstream name as much as possible. So python-webpy,
> for instance, keeps the upstream webpy name (note that the upstream name is
> webpy, even though the package is identified in PyPI as web.py. PyPI isn't very
> consistent either). For zope.interface, I actually see no reason not to keep the
> upstream name, so the package really should have been called
> python-zope.interface IMHO.
>
> What do the others think?
I missed this message. On my side, I would prefer to not have a
package named python-zope.interface. It should be named
python-zope-interface instead. I.e all weird characters should be
replaced by '-' in package names.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-08 10:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 13:31 [Buildroot] [PATCH 0/2] python-package-generator Denis THULIN
2015-07-09 13:31 ` [Buildroot] [PATCH 1/2] scanpypi: new utility Denis THULIN
2015-07-11 12:56 ` Arnout Vandecappelle
2015-07-15 14:08 ` Denis Thulin
2015-07-15 14:17 ` [Buildroot] Package naming convention [was: Re: [PATCH 1/2] scanpypi: new utility] Arnout Vandecappelle
2015-08-08 10:59 ` Thomas Petazzoni [this message]
2015-07-09 13:31 ` [Buildroot] [PATCH 2/2] python-robotframework: New package Denis THULIN
2015-07-11 15:39 ` Arnout Vandecappelle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150808125925.66e32bfb@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.