Release Engineering

This project is intented for all release related issues (isos, installer, etc), under the umbrella of the ArchLinux Release Engineers
Tasklist

FS#18495 - Installer should always install needed packages

Attached to Project: Release Engineering
Opened by Allan McRae (Allan) - Sunday, 28 February 2010, 12:39 GMT
Last edited by Gerardo Exequiel Pozzi (djgera) - Monday, 26 November 2012, 04:45 GMT
Task Type Bug Report
Category AIF
Status Closed
Assigned To Dieter Plaetinck (Dieter_be)
Architecture All
Severity Low
Priority Low
Reported Version 2009.08
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

It would good if the installer always installed packages needed for the filesystem types and encryption/raid options that are selected. Then the relevant packages could be removed from the base group.

At least these packages:
cryptsetup
device-mapper
jfsutils
lvm2
mdadm
reiserfsprogs
xfsprogs

and maybe some network related packages?
This task depends upon

Closed by  Gerardo Exequiel Pozzi (djgera)
Monday, 26 November 2012, 04:45 GMT
Reason for closing:  Deferred
Comment by Dieter Plaetinck (Dieter_be) - Sunday, 28 February 2010, 20:59 GMT
s/always install/select by default/
good point. pretty easy to implement. it's in interactive_select_packages() if anyone wants to have a go at it.
Comment by Dieter Plaetinck (Dieter_be) - Friday, 16 April 2010, 11:05 GMT
wpa_supplicant, ppp and rp-pppoe also imho.
Comment by Dieter Plaetinck (Dieter_be) - Sunday, 05 December 2010, 17:22 GMT
I have implemented this.
http://projects.archlinux.org/aif.git/commit/?id=839ade1073032d841a3823e0a25d0ded19cc8b71
It was a bit hard to test (aif now preselects the relevant FS packages but they are currently preselected because they're in base anyway), but in my testing I changed the needed packages to non-base packages (like openssh) and that seems to work. later on i'll doublecheck with automatic installs, because we're dealing with sensitive stuff here.

So, as far as aif-git is concerned, all filesystems (including ext) can go out of base. Of course, you'll probably only want to do this after we've released new images with the new aif.
I currently haven't done anything for network packages. The fanciest networking tool aif uses is dhcpcd, which you'll probably want to keep in base. (even if the user doesn't use dhcp at installation time, this program is too useful to remove from base). Aif currently has no support for wireless networking, ppp, etc. So we could schedule deletion from base for those, as long as i put a clear message during package selection "make sure to select the appropriate networking packages if you need them" or something. Although now i think about it, I'ld keep wireless stuff. It's silly that when a user would install with physical network install, and then leave the house with only wifi available, needs to discover he doesn't have wireless support.

Loading...