From: Leo Famulari <leo@famulari.name>
To: Dylan Jeffers <sapientech@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add python-pypump
Date: Mon, 15 Aug 2016 14:41:28 -0400 [thread overview]
Message-ID: <20160815184128.GA11573@jasmine> (raw)
In-Reply-To: <20160814160711.5c87d31e@openmailbox.org>
On Sun, Aug 14, 2016 at 04:07:11PM -0700, Dylan Jeffers wrote:
> > The latest upstream version 0.7. Is there a reason not to use the
> > latest version in this case?
>
> For my immediate purposes, I need pypump 0.6, since thats the version
> used in my projects. Since the versions are quite different, maybe we
> include both of them?
I think we should package the latest version, at least.
Maybe we could also package 0.6 with a package 'python-pypump-0.6' that
inherits from python-pypump. Or, you could keep that inherited
python-pypump-0.6 in a private package repo, and use GUIX_PACKAGE_PATH.
I'd prefer the latter option. I don't think we have a precedent of
adding old releases, although we do sometimes keep them around for
compatibility. But I could be mistaken.
What do people think we should do?
next prev parent reply other threads:[~2016-08-15 18:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 1:31 [PATCH] gnu: Add python-pypump Dylan Jeffers
2016-08-13 12:57 ` Leo Famulari
2016-08-13 19:32 ` Dylan Jeffers
2016-08-13 23:07 ` Leo Famulari
2016-08-14 23:07 ` Dylan Jeffers
2016-08-15 18:41 ` Leo Famulari [this message]
2016-08-15 22:17 ` Dylan Jeffers
2016-08-19 22:17 ` Leo Famulari
2016-09-05 9:21 ` Efraim Flashner
2016-08-15 22:29 ` Danny Milosavljevic
2016-08-15 22:41 ` Leo Famulari
2016-08-16 18:02 ` Leo Famulari
-- strict thread matches above, loose matches on Subject: below --
2017-01-09 10:03 [PATCH 0/9] Add more qtmodules Efraim Flashner
2017-01-09 10:03 ` [PATCH] gnu: Add python-pypump Efraim Flashner
2017-01-09 11:03 ` Efraim Flashner
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=20160815184128.GA11573@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=sapientech@openmailbox.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.