On Mon, Jan 09, 2017 at 12:03:39PM +0200, Efraim Flashner wrote:
> * gnu/packages/pumpio.scm (python-pypump): New variable.
> ---
> gnu/packages/pumpio.scm | 39 +++
> 1 file changed, 39 insertions(+)
>
Ignore this one, I included it by accident, and I've neve
* gnu/packages/pumpio.scm (python-pypump): New variable.
---
gnu/packages/pumpio.scm | 39 +++
1 file changed, 39 insertions(+)
diff --git a/gnu/packages/pumpio.scm b/gnu/packages/pumpio.scm
index a74d474..f834884 100644
--- a/gnu/packages/pumpio.scm
+++ b/gnu/
On Fri, Aug 19, 2016 at 06:17:47PM -0400, Leo Famulari wrote:
> On Mon, Aug 15, 2016 at 03:17:57PM -0700, Dylan Jeffers wrote:
> > On Mon, 15 Aug 2016 14:41:28 -0400
> > Leo Famulari wrote:
> >
> > > On Sun, Aug 14, 2016 at 04:07:11PM -0700, Dylan Jeffers wrote:
> > > > > The latest upstream vers
On Mon, Aug 15, 2016 at 03:17:57PM -0700, Dylan Jeffers wrote:
> On Mon, 15 Aug 2016 14:41:28 -0400
> Leo Famulari wrote:
>
> > 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 c
On Tue, Aug 16, 2016 at 12:29:27AM +0200, Danny Milosavljevic wrote:
> > 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
On Tue, Aug 16, 2016 at 12:29:27AM +0200, Danny Milosavljevic wrote:
> > 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
> 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.
It depends on whether py
On Mon, 15 Aug 2016 14:41:28 -0400
Leo Famulari wrote:
> 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 t
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 differ
Hi Leo,
Yeah, following your advice, i used git format-patch -n master, but
then added --stdout > filename.patch to get a single file.
> How about putting this in gnu/packages/pumpio.scm? Seems appropriate
> to me :)
Was not aware of pumpio.scm, seems quite appropriate!
> The latest upstream ve
On Sat, Aug 13, 2016 at 12:32:42PM -0700, Dylan Jeffers wrote:
> Thanks for getting back. Here is the series!
Cool, you showed me something new. I didn't know you could put the whole
series in a single attachment, apply it with `git am`, and have the
patch ordering handled automatically. Very nice
On Sat, 13 Aug 2016 08:57:00 -0400
Leo Famulari wrote:
> On Fri, Aug 12, 2016 at 06:31:29PM -0700, Dylan Jeffers wrote:
> > When submitting patches that require other patches I've submitted,
> > should I put them together in a single patch, or keep them separate
> > like this?
>
> For patches
On Fri, Aug 12, 2016 at 06:31:29PM -0700, Dylan Jeffers wrote:
> When submitting patches that require other patches I've submitted,
> should I put them together in a single patch, or keep them separate
> like this?
For patches that depend on each other, sending them as a "patch series"
will commun
PATCH] gnu: Add python-pypump
* gnu/packages/python.scm (python-pypump, python2-pypump): New
* variables.
---
gnu/packages/python.scm | 32
1 file changed, 32 insertions(+)
diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm
index 6ff1c5c..2f67ab7 1
14 matches
Mail list logo
