all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add Scikit-learn.
Date: Fri, 27 Feb 2015 10:41:51 +0100	[thread overview]
Message-ID: <20150227094151.GA4043@debian.eduroam.u-bordeaux.fr> (raw)
In-Reply-To: <34d78aa36c64669e2a26bc58b3fa9de6@openmailbox.org>

On Thu, Feb 26, 2015 at 03:10:51PM -0600, Eric Bavier wrote:
> On 2015-02-26 14:43, Andreas Enge wrote:
> >So you would suggest to always use the "project name" and not the "module
> >name" for Python packages?
> Yes.

Okay, you are definitely more knowledgeable in that matter, so I would like
to follow your advice. I will add a sentence stating that one should thrive
to choose a common base name independently of the tarball name.

So let us rename python(2)-py(2)cairo to python(2)-pycairo. If nobody beats
me to it, I can do it tomorrow.

Andreas

  reply	other threads:[~2015-02-27  9:42 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
2015-02-26 20:43               ` Andreas Enge
2015-02-26 21:10                 ` Eric Bavier
2015-02-27  9:41                   ` Andreas Enge [this message]
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=20150227094151.GA4043@debian.eduroam.u-bordeaux.fr \
    --to=andreas@enge.fr \
    --cc=ericbavier@openmailbox.org \
    --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.