To try to bring this forward, and gauge the interest, I created
https://salsa.debian.org/installer-team/hw-detect/-/merge_requests/10 >
enabling isenkram in the installer. It replaces the discover support
that was removed yesterday in 961c536c29f01c47da202034b371caab697d85ac.
--
Happy hacking
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 virtualization/cl
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 durin
[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 a
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 virtualization/cloud
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 do
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.
The fact it's been ma
[ Please respect reply-to, let's have this discussion on debian-boot ]
Hello everybody,
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
9 matches
Mail list logo
