Hi,
On Mon, 04 Dec 2017, Thomas Goirand wrote:
> On 12/03/2017 05:30 PM, Raphael Hertzog wrote:
> > In the last years, Petter Rheinholdtsen worked on isenkram[2] with a
> > similar but a bit broader goal. I noticed it has better support
> > of clouds and that it will install some
Hi,
On Sun, 03 Dec 2017, Cyril Brulebois wrote:
> > I see mainly benefits to such a move. The only downside is that it
> > would pull python by default. This entirely depends on whether we want
> > to keep it installed or not. We could install it just to do a single
> > scan and install pass
[Elena ``of Valhalla'']
> Did I see it right and this would be python 2?
Probably. I just used /usr/bin/python and did not care much about
python 2 or 3 when writing it. As far as I know, there is not much
stopping it from working with python 3, but I have not done the porting.
I agree that it
On 2017-12-03 at 17:30:49 +0100, Raphael Hertzog wrote:
> I see mainly benefits to such a move. The only downside is that it would
> pull python by default.
Did I see it right and this would be python 2?
I'd think that at the very least it would have to be ported to python 3, since
py2 is going
Le 04/12/2017 à 02:22, Thomas Goirand a écrit :
> On 12/03/2017 05:30 PM, Raphael Hertzog wrote:
>> In the last years, Petter Rheinholdtsen worked on isenkram[2] with a
>> similar but a bit broader goal. I noticed it has better support
>> of clouds and that it will install some
On 12/03/2017 05:30 PM, Raphael Hertzog wrote:
> In the last years, Petter Rheinholdtsen worked on isenkram[2] with a
> similar but a bit broader goal. I noticed it has better support
> of clouds and that it will install some virtualization/cloud-related
> packages automatically whereas discover
Hi,
Raphael Hertzog (2017-12-03):
> debian-installer is using discover[1] to install some packages based
> on the hardware it discovers. Unfortunately, discover is dead upstream
> (Debian is the upstream really) and the hardware->package database is
> not maintained at all.
7 matches
Mail list logo