The issue tracker has been moved https://gitlab.archlinux.org/archlinux/archiso/-/issues
FS#16567 - Add installation profiles/templates and some postinstall tasks
Attached to Project:
Release Engineering
Opened by Ismael Carnales (void) - Sunday, 11 October 2009, 03:42 GMT
Last edited by Dieter Plaetinck (Dieter_be) - Sunday, 05 December 2010, 15:15 GMT
Opened by Ismael Carnales (void) - Sunday, 11 October 2009, 03:42 GMT
Last edited by Dieter Plaetinck (Dieter_be) - Sunday, 05 December 2010, 15:15 GMT
|
DetailsI posted this in Arch Bounty by mistake sice that is a sepparate project from Arch.
It would be good to add some profiles to the installation process. After installing the base system, you're offered with a list of profiles, o packages templates based on use cases, some examples: * Desktop * Notebook (apps, tweaks and optimizations for running on notebooks) * Model * Environment * Console * X.org * DE * Gnome * Apps * KDE * Apps * Xfce * Apps * Window manager * Fluxbox * Apps / Utils * Xmonad * Apps / Utils * Awesome * Apps / Utils * Apps * Gtk * QT * Lightweight apps * Home Server * File Server * Media Center * Server * web server * platform * firewall Every profile will have information of required and recommended packages, I think they could be official and community suplied profiles.. Every profile could suppply some optional groups, to allow more customization. If we can have the "metapackages" really suited for one thing the customization possibilities will be endless. This metapackages could also supply example sets of config files for some programs provided by the community and the suggestions from the wiki. We should supply the possibility to make custom profile install discs with the required sofware to make multiple installs. Obviously that this won't force any package selection, only suggest what others think is good for the task and provide you with different options to go or to use your own: like when you select that will have a DE or X.org you must install a video driver, etc, etc. This can also be used to provide Arch backends to other platforms such as Sugar, Moblin, Media Centers, etc. As a final comment this idea could be implemented at a more basic level for ex, having a Xorg package that will show you a list of drivers, fonts, and add hal to rc.conf on install, this should make newcomers fall less in some really common pitfalls like no having input on X. All the base information is ready on the wiki, my proposal is giving that a machine readable structure and allow users to see the critical info when selecting/browsing this metapackages. This could be a post-install tasks after install is complete |
This task depends upon
Closed by Dieter Plaetinck (Dieter_be)
Sunday, 05 December 2010, 15:15 GMT
Reason for closing: Won't implement
Additional comments about closing: not in the scope of the official tools. feel free to do this
Sunday, 05 December 2010, 15:15 GMT
Reason for closing: Won't implement
Additional comments about closing: not in the scope of the official tools. feel free to do this
- for the interactive procedure, enable the user to pick a profile which is nothing more then a "set of default selected packages". note that someone will need to maintain those lists and that's tricky because it would be tightly coupled to the procedure.
- for the automatic procedure: just have some more profiles available, which can easily be 3rd party profiles.
option 2 seems the most usefull to me. you could also write a customized procedure which is similar to interactive but is more integrated with things you want. you could also easily maintain this as a 3rd party procedure.