[arch-releng] February release

[Dan McGee]

On Wed, Jan 30, 2013 at 1:51 PM, Dave Reisner <d at falconindy.com> wrote:
> On Wed, Jan 30, 2013 at 08:41:31PM +0100, Pierre Schmitz wrote:
>> Am 30.01.2013 20:11, schrieb Dave Reisner:
>> > On Wed, Jan 30, 2013 at 03:57:08PM -0300, Gerardo Exequiel Pozzi wrote:
>> >> On 01/30/2013 03:35 PM, Tom Gundersen wrote:
>> >>
>> >> >
>> >> > For the next release I suggest we seriously consider using Network Manager
>> >> > on the instal medium. nmcli seems to cover most relevant use cases now.
>> >>
>> >> I was thinking about this when systemd replaced initscripts.
>> >>
>> >> +1 for me.
>> > Can we talk about pruning out some of the weight from the ISO before we
>> > add another 20MB via NM and dependencies? We'd need to add, roughly:
>> >
>> > dbus-glib
>> > glib-networking
>> > gsettings-desktop-schemas
>> > libsoup
>> > nspr
>> > nss
>> > polkit
>> > sqlite
>> > networkmanager
>> >
>> > Not really a fan of network manager, but I don't really deal with the
>> > headaches that come with wifi so often. Is nmcli more than just a config
>> > file parser these days?
>>
>> NetworkManager would work quite well for us. The deps look a little
>> insane though. I don't know why it would need libsoup and Gnome stuff.
>
> If adding NM is the deemed The Right Thing To Do™ then fine, but I'd
> like to make sure that it's actually valuable. Last I looked, using
> nmcli meant handwriting config files which had no documented syntax.
>
>> I would say we keep things as-is for at least the February ISO image.
>
> Very much agreed.

If/when we do a cleanup of the ISO, we should really prune things like
nmap. We're not a pen-testing LiveCD, and people can always install
stuff in the live environment anyways.

-Dan