unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Cyril Roelandt <tipecaml@gmail.com>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH 02/11] gnu: Add oslotest.
Date: Thu, 23 Jul 2015 00:13:22 +0200	[thread overview]
Message-ID: <55B01582.5050609@gmail.com> (raw)
In-Reply-To: <CAJ=RwfaqwJN4ZdLM+cnGAGp1SX1N-aA33z=vQecvxci_xF7+pw@mail.gmail.com>

On 07/20/2015 06:14 PM, Thompson, David wrote:
> On Wed, Jul 15, 2015 at 7:32 PM, Cyril Roelandt <tipecaml@gmail.com> wrote:
>> * gnu/packages/openstack.scm: New file.
>> * gnu-system.am (GNU_SYSTEM_MODULES): Add it here.
>> * gnu/packages/python.scm (python-appdirs, python2-appdirs): New variables.
> 
> Could you break this patch so that there is one package per patch?

Hum, I'm not sure whether that really makes sense. The main "feature" I
want to add is the package for oslotest, so it seemed natural to add its
dependencies in the same patch, especially since there is only one.
Plus, this would make this patch series *huge*. Do we really want that?

> Also, all of the Python packages in openstack.scm look like they
> really belong in python.scm.  Could you move them?
> 

Well, in the end, we could have everything from PyPI in python.scm.
OpenStack is a huge project, so I thought it would make sense to have
its packages in their own file. WDYT?


Thanks for the review,
Cyril.

  reply	other threads:[~2015-07-22 22:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-15 23:32 [PATCH 00/11] Add a few modules from the Oslo library Cyril Roelandt
2015-07-15 23:32 ` [PATCH 01/11] gnu: Bump python-six to 1.9.0 Cyril Roelandt
2015-07-20 17:41   ` Thompson, David
2015-08-09 15:32     ` Cyril Roelandt
2015-07-15 23:32 ` [PATCH 02/11] gnu: Add oslotest Cyril Roelandt
2015-07-16 11:10   ` Mathieu Lirzin
2015-07-22 22:09     ` Cyril Roelandt
2015-07-20 16:14   ` Thompson, David
2015-07-22 22:13     ` Cyril Roelandt [this message]
2015-07-23  1:54       ` Ian Denhardt
2015-07-23  2:06       ` Thompson, David
2015-07-23 13:47         ` Ludovic Courtès
2015-07-23 16:46         ` Cyril Roelandt
2015-07-23 17:13           ` Thompson, David
2015-07-15 23:32 ` [PATCH 03/11] gnu: Add oslo.i18n Cyril Roelandt
2015-07-15 23:32 ` [PATCH 04/11] gnu: Add oslo.config Cyril Roelandt
2015-07-15 23:32 ` [PATCH 05/11] gnu: Add oslo.utils Cyril Roelandt
2015-07-15 23:32 ` [PATCH 06/11] gnu: Add oslo.context Cyril Roelandt
2015-07-15 23:32 ` [PATCH 07/11] gnu: Add oslo.serialization Cyril Roelandt
2015-07-15 23:32 ` [PATCH 08/11] gnu: Add oslo.log Cyril Roelandt
2015-07-15 23:32 ` [PATCH 09/11] gnu: Add oslo.cache Cyril Roelandt
2015-07-22 22:14   ` Cyril Roelandt
2015-07-15 23:32 ` [PATCH 10/11] gnu: Add oslo.middleware Cyril Roelandt
2015-07-15 23:32 ` [PATCH 11/11] gnu: Add oslosphinx Cyril Roelandt

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55B01582.5050609@gmail.com \
    --to=tipecaml@gmail.com \
    --cc=dthompson2@worcester.edu \
    --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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).