From: Eric Bavier <ericbavier@openmailbox.org>
To: Andreas Enge <andreas@enge.fr>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add Scikit-learn.
Date: Thu, 26 Feb 2015 14:03:37 -0600 [thread overview]
Message-ID: <648692e7170fada41ebd45ebe0724e42@openmailbox.org> (raw)
In-Reply-To: <20150226175900.GA3835@debian>
On 2015-02-26 11:59, Andreas Enge wrote:
> On Thu, Feb 26, 2015 at 06:11:03PM +0100, Ludovic Courtès wrote:
>> I think a Python “module” is a single .py file. In that case
>> “package”
>> seems more accurate, no?
>
> Indeed, that is true. Still I am looking for a justification to rename
> "python2-py2cairo" to "python2-cairo"
The issue in this case is that py2cairo and pycairo are actually
different projects. I chose to use the name python2-py2cairo, to go
with our "least divergence from upstream" method.
> that is, use the module name for
> a package containing a single module.
This could become error-prone. The packager needs to check the
interface of the library before deciding on a package name? It might
also not be future-proof, in the event that a project updates its public
interface.
--
`~Eric
next prev parent reply other threads:[~2015-02-26 20:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 16:24 [PATCH] gnu: Add Scikit-learn Ricardo Wurmus
2015-02-23 17:17 ` Ricardo Wurmus
2015-02-23 17:36 ` Andreas Enge
2015-02-26 11:28 ` Ricardo Wurmus
2015-02-26 20:44 ` Andreas Enge
2015-02-23 17:52 ` Andreas Enge
2015-02-25 22:52 ` Andreas Enge
2015-02-25 22:57 ` Andreas Enge
2015-02-26 17:11 ` Ludovic Courtès
2015-02-26 17:59 ` Andreas Enge
2015-02-26 18:20 ` Ludovic Courtès
2015-02-26 18:23 ` Andreas Enge
2015-02-26 20:03 ` Eric Bavier [this message]
2015-02-26 20:43 ` Andreas Enge
2015-02-26 21:10 ` Eric Bavier
2015-02-27 9:41 ` Andreas Enge
2015-02-27 22:48 ` Andreas Enge
2015-02-27 23:53 ` Andreas Enge
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=648692e7170fada41ebd45ebe0724e42@openmailbox.org \
--to=ericbavier@openmailbox.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.