Ricardo Wurmus writes:
> Bonface Munyoki K. writes:
>
>>> You can use an ‘inferior’[0] Guix if you don't
>>> mind the entire closure of python2-flask* being
>>> frozen in the past -- possibly including
>>> incompatibilities or known security
>>> vulnerabilities.
>>>
>>> I don't know what their
Bonface Munyoki K. writes:
You can use an ‘inferior’[0] Guix if you don't
mind the entire closure of python2-flask* being
frozen in the past -- possibly including
incompatibilities or known security
vulnerabilities.
I don't know what their inclusion & maintenance
criteria are, but another
Hi Tobias!
Tobias Geerinckx-Rice writes:
> Bonface,
>
> Bonface Munyoki K. writes:
>> What do you do when you want to use a package that
>> has already been removed from guix. An example is
>> that I have a legacy project that I help maintain
>> that still uses some old python2 packages. One of
On Tue, Apr 20, 2021 at 10:35:10AM +0200, Tobias Geerinckx-Rice wrote:
> You can use an ‘inferior’[0] Guix if you don't mind the entire closure of
> python2-flask* being frozen in the past -- possibly including
> incompatibilities or known security vulnerabilities.
>
> I don't know what their
Bonface,
Bonface Munyoki K. writes:
What do you do when you want to use a package that
has already been removed from guix. An example is
that I have a legacy project that I help maintain
that still uses some old python2 packages. One of
them is python2-flask*. Right now, as a work
around, I
Hi Guix!
What do you do when you want to use a package that
has already been removed from guix. An example is
that I have a legacy project that I help maintain
that still uses some old python2 packages. One of
them is python2-flask*. Right now, as a work
around, I manually write the package
