Hi, I started working on the addons to the 2.3 setup script; as you already know we're decided to add some sort of group selecting and/or dependency checking, mainly because of the large number of packages of the modular Xorg release. So far I added a simple group implementation, consisting in a selection of the groups and subsequent separate selection of packages from each collection. Easier to see than to explain: http://www.varlock.com/tmp/groupsetup/ Note: The package selection procedure for upgrades is left untouched. Question #1: do you think that there should be the possibility of selecting packages from a previously unselected group? (all items off by default) Regarding dependency ckecking, I plan to write an additional function / dialog that will display the list of unselected needed packages (if any) after the standard selection procedure. This function will retrieve dependency information from a dedicated file, maybe automatically generated by a prt-get call from the ISO Makefile. Question #2: does this approach to dependency handling make sense? Thanks for your attention, Regards, Simone -- Simone Rota Bergamo, Italy - http://www.varlock.com
Hi, On Fri, Jun 09, 2006 at 18:56:17 +0200, Simone Rota wrote:
Hi,
I started working on the addons to the 2.3 setup script; as you already know we're decided to add some sort of group selecting and/or dependency checking, mainly because of the large number of packages of the modular Xorg release.
So far I added a simple group implementation, consisting in a selection of the groups and subsequent separate selection of packages from each collection. Easier to see than to explain: http://www.varlock.com/tmp/groupsetup/ Note: The package selection procedure for upgrades is left untouched.
Question #1: do you think that there should be the possibility of selecting packages from a previously unselected group? (all items off by default) I'd kinda like to have a "select group" and "select ports from group" functionality, where the later lets you enable/disable ports from a group. Not sure if dialog supports that easily, though.
Here a flow diagram to illustrate that: (start setup) -> (group selection) -> (install packages) | | -> optional (detailed selection) So if you want to do a "install everything" type of install, you only have to make three marks on the group dialog, without dealing with individual port selections pages.
Regarding dependency ckecking, I plan to write an additional function / dialog that will display the list of unselected needed packages (if any) after the standard selection procedure. This function will retrieve dependency information from a dedicated file, maybe automatically generated by a prt-get call from the ISO Makefile.
Question #2: does this approach to dependency handling make sense? Sounds good to me, you hardly ever want to install binaries with broken dependencies :-)
I have another suggestion for our future setup: http://jw.tks6.net/files/crux/setup.png Basically one page which allows you to select the level of KISS/bloat :-) Thanks for your work on that, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
On 06/10/06 17:47 Johannes Winkelmann wrote:
I'd kinda like to have a "select group" and "select ports from group" functionality, where the later lets you enable/disable ports from a group. Not sure if dialog supports that easily, though.
Here a flow diagram to illustrate that:
(start setup) -> (group selection) -> (install packages) | | -> optional (detailed selection)
So if you want to do a "install everything" type of install, you only have to make three marks on the group dialog, without dealing with individual port selections pages.
Looks interesting, even if pressing enter 3 times does not look so bad, unless we aim for the "OMG! One click install" :-) An intermediate solution would be a prompt after group selection asking if detailed selection is wanted, so we reduce the thing to one additional click.
I have another suggestion for our future setup: http://jw.tks6.net/files/crux/setup.png Basically one page which allows you to select the level of KISS/bloat :-)
I support this idea only if we put a "Nevermind, just download and install Fedora Core for me" option. Other than that, good call. Regards, Simone -- Simone Rota Bergamo, Italy - http://www.varlock.com
On Sat, Jun 10, 2006 at 05:47:24PM +0200, Johannes Winkelmann wrote:
I have another suggestion for our future setup: http://jw.tks6.net/files/crux/setup.png Basically one page which allows you to select the level of KISS/bloat :-)
Seems nice, it also reminds me of slackware's installer to some extent. It would still be compatible with the KISS philosophy, and hopefully provide another layer of convenience. Simply my 0,02 EUR on the issue. -- "Damnant quod non intellegunt."
On 06/10/06 17:47 Johannes Winkelmann wrote:
Here a flow diagram to illustrate that:
(start setup) -> (group selection) -> (install packages) | | -> optional (detailed selection)
I have another suggestion for our future setup: http://jw.tks6.net/files/crux/setup.png
Here's an implementation: http://www.varlock.com/tmp/setup.tgz Features: - Group selection and optional detailed selection - Option selection dialog (info pages, etc.) - Dependency checking with display of required packages not previously selected Generic Notes: - In order to test the script I think it's enough to place a /crux symlink pointing to the crux dir inside the package - If you happen to regenerate the setup.dependencies with the included gendeps script, be sure to manually remove iproute2 from dependencies since it's in contrib. (maintainers already alerted). - The option selection dialog has no effect atm since we have yet to define the wanted options. - I Included all (fake) packages for core/opt/xorg for testing purposes. Dev notes: - I'm no bash wizard, I feel the dependency checking funcion (get_missing_deps) can be improved, though it seem to work an take an acceptable time: around 3 secs for full dependency checking on all core/opt/xorg ports When it's time to create a crux-2.3 branch on svn I'll move the script at crux.nu; meanwhile patches and ideas are welcome as usual. Regards, Simone -- Simone Rota Bergamo, Italy - http://www.varlock.com
Hi Simone, On Sun, Jun 25, 2006 at 20:22:32 +0200, Simone Rota wrote:
On 06/10/06 17:47 Johannes Winkelmann wrote:
Here a flow diagram to illustrate that:
(start setup) -> (group selection) -> (install packages) | | -> optional (detailed selection)
I have another suggestion for our future setup: http://jw.tks6.net/files/crux/setup.png
Here's an implementation: http://www.varlock.com/tmp/setup.tgz
Thanks for this, I have to admit though it's not what I imagined :-), although it's a good start and definitely what the above diagram shows. Furthermore, I'm not sure if this is even possible with 'dialog'; anyway, here we go: --- group selection screen ----------------- [x] # core ports ################# [ ] opt ports w/o x11 [ ] x11 <Cancel> <Detailed selection> <Continue*> -------------------------------------------- (the hashmarks showing the currently selected item) Hitting 'space' would select the group and choosing "Detailed selection" would allow to select individual packages. This way, you don't have to go through all package lists if you want to select packages from just one. Does anyone know if this works with 'dialog'? Could maybe "lxdialog" (from the kernel) do that? Regards, Johannes P.S. Simone: congratulations to the world championship :-) -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
Johannes Winkelmann wrote:
Hi Simone,
Hi,
Thanks for this, I have to admit though it's not what I imagined :-), although it's a good start and definitely what the above diagram shows. Furthermore, I'm not sure if this is even possible with 'dialog'; anyway, here we go:
--- group selection screen -----------------
[x] # core ports ################# [ ] opt ports w/o x11 [ ] x11
<Cancel> <Detailed selection> <Continue*> --------------------------------------------
(the hashmarks showing the currently selected item)
Hitting 'space' would select the group and choosing "Detailed selection" would allow to select individual packages. This way, you don't have to go through all package lists if you want to select packages from just one.
Well, I see your point; on the other side you'll need to manually select <Detailed selection> n times if you want to customize n collections.
Does anyone know if this works with 'dialog'? Could maybe "lxdialog" (from the kernel) do that?
dialog: The additional button <Detailed selection> is easily added with --extra-button and --extra-label; I think it's not possible to detect the currently selected group (as in your hasmarks). Btw, the additional button could replace the confirmation dialog for detailed selection in the proposed implementation. lxdialog: I'm confident we can use the lxdialog structure for subselection, as in: [ ] Amateur Radio support ---> (submenu with detailed selection). Not sure if it's worth switching to lxdialog just for that.
P.S. Simone: congratulations to the world championship :-)
Pity we played our worst match during the final. I apologize to the ones out there who like football :-)
participants (3)
-
Jesse Kokkarinen
-
Johannes Winkelmann
-
Simone Rota