Re: Questions about packaging

2019-10-23 Thread Marius Bakke
Tanguy Le Carrour writes: > Le 10/18, Marius Bakke a écrit : >> On the next 'core-updates' cycle, Pytest 5 will then become the default, >> and we will have to fix all packages that does not work with that >> version :-) > > I guess those broken packages will show up as "red" in Cuirass!? >

Re: Questions about packaging

2019-10-21 Thread Gábor Boskovits
Hello, Tanguy Le Carrour ezt írta (időpont: 2019. okt. 21., Hét 11:24): > Hi Marius, > > > Le 10/18, Marius Bakke a écrit : > > Tanguy Le Carrour writes: > > > In Guix, we have Pytest 4.4.2, but the latest release is 5.2.1. > > > In that case, would it make sense to define a new "versionned"

Re: Questions about packaging

2019-10-21 Thread Tanguy Le Carrour
Hi Marius, Le 10/18, Marius Bakke a écrit : > Tanguy Le Carrour writes: > > In Guix, we have Pytest 4.4.2, but the latest release is 5.2.1. > > In that case, would it make sense to define a new "versionned" public > > variable for python-pytest? Would I create python-pytest5? Or would I > >

Re: Questions about packaging

2019-10-18 Thread Marius Bakke
Hello Tanguy, Tanguy Le Carrour writes: > In Guix, we have Pytest 4.4.2, but the latest release is 5.2.1. > In that case, would it make sense to define a new "versionned" public > variable for python-pytest? Would I create python-pytest5? Or would I > rename python-pytest to python-pytest4 and

Re: Questions about packaging

2019-10-14 Thread Tanguy Le Carrour
Le 10/12, Danny Milosavljevic a écrit : > Also, in > > (define-public icedtea-6 > (package > [...] > )) > > "icedtea-6" is a variable name (in the programming language Guile). > > The package name is there: > > [...] > (package > (name "icedtea") <- > ) > > We don't have version

Re: Questions about packaging

2019-10-14 Thread Tanguy Le Carrour
Hi Danny Le 10/12, Danny Milosavljevic a écrit : > On Fri, 11 Oct 2019 09:42:00 +0200 > Tanguy Le Carrour wrote: > > > Le 10/10, Danny Milosavljevic a écrit : > > > > 1) Updating a package > > > > So I would have to update python-cachecontrol from 0.11.6 to 0.12.5. > > > > Should I create a

Re: Questions about packaging

2019-10-12 Thread Danny Milosavljevic
Also, in (define-public icedtea-6 (package [...] )) "icedtea-6" is a variable name (in the programming language Guile). The package name is there: [...] (package (name "icedtea") <- ) We don't have version numbers in package names--but you can request a specific version by $ guix

Re: Questions about packaging

2019-10-12 Thread Danny Milosavljevic
Hi, On Fri, 11 Oct 2019 09:42:00 +0200 Tanguy Le Carrour wrote: > Le 10/10, Danny Milosavljevic a écrit : > > > 1) Updating a package > > > So I would have to update python-cachecontrol from 0.11.6 to 0.12.5. > > > Should I create a python-cachecontrol-0.11.6 and fix all the packages > > > that

Re: Questions about packaging

2019-10-11 Thread Tanguy Le Carrour
Hi Danny ! Thanks for your answer. Le 10/10, Danny Milosavljevic a écrit : > > 1) Updating a package > > So I would have to update python-cachecontrol from 0.11.6 to 0.12.5. > > Should I create a python-cachecontrol-0.11.6 and fix all the packages > > that depend on it? Only the one that would

Re: Questions about packaging

2019-10-09 Thread Danny Milosavljevic
Hi, On Wed, 9 Oct 2019 11:56:33 +0200 Tanguy Le Carrour wrote: > 1) Updating a package > So I would have to update python-cachecontrol from 0.11.6 to 0.12.5. > Should I create a python-cachecontrol-0.11.6 and fix all the packages > that depend on it? Only the one that would break? The latter.

Questions about packaging

2019-10-09 Thread Tanguy Le Carrour
Hi Guix I'm currently working on packaging python-poetry and, unsurprisingly, I have questions! :-) I guess some of them have already been answered somewhere, so don't hesitate to point me to a previous thread or post… 1) Updating a package What am I suppose to do when updating a package to a