1) when selecting a dynamic stage3, it should force "snapshot" for the portage tree, and force the usage of /mnt/cdrom/snapshots/portage-* | head -n 1... there will only ever be one snapshot, so that shouldn't be an issue 2) when selecting snapshot, fill in "ls /mnt/cdrom/snapshots/portage-* | head -n 1" into the input box, but allow it to be edited 3) make sure the user is unable to change make.conf when doing dynamic/GRP... since it will break networkless if they change a USE flag, as portage now is smart enough to check the flags that the package was built with 4) browse buttons... not sure how useful they would be... but something like a mirror list, pulled live from the site (perhaps via a button press) or something... I really don't know how something like that could be done... but the biggest complaint I got was from people having to enter long URIs into the input boxes 5) have "GRP" check for existence of package in /var/db before allowing user to select it on packages page 6) Add Firefox/Mozilla/Thunderbird and OpenOffice to packages page 7) input validation... while the URI fields (for example) make sure that something is entered in them, should they not also check to make sure the URI is valid before continuing, instead of waiting until the end, then bombing out
8) a "Recommended" button on the partitioning screen... 256m/1g/*... only work with unallocated space... if there isn't like 4GB unallocated, have it pop up a box "There is not enough unallocated space on this disk. You will need to resize or delete partitions yourself to free up some space for this installation." so we don't wipe out Windows installs for the dual-booting crowd
1, 2, and 7 done in gtkfe. 5 and 6 are really moot since that screen doesn't work anyway :P
1,2,3,6 added to gli-dialog, 4 is moot, 7 already exists. 5 is questionable.
Re: comment #2 - It might be moot *now* but at some point it will work... ;] Re: comment #3 - I still feel that the GRP target should be the same as the current GRP in meaning, otherwise we are losing functionality by moving to the installer, and I won't be able to switch to having the installer CD as a default release option. This means that it should only work with things it can actually build from CD. The idea is that you do your validations before the actual "Install" button is clicked, so we keep users from starting an invalid GRP build rather than allowing them to start one, then having it fail with an error, that reflects badly on Gentoo's quality. Also, any situation in which the "GRP" build tries to download *anything* from the Internet will also result in bug reports, as people expect GRP to work without an Internet connection of any sort.
9) throw up a warning when user selects their own stage3 tarball with GRP... something like "You have selected to use your own tarball for stage3. Using this method makes it possible to build an invalid configuration. Do you want to continue?" Of course, the wording will need to be changed to let people know that they need to use a proper stage3 tarball, I'm just giving an example...
Remaining to be completed: GTK === 5 (check /var/db/pkg for GRP) 6 (add firefox/thunderbird/OOo to extra packages) 8 (recommended button for partitioning) 9 (warn when doing their own stage3 when using GRP) dialog ====== 5 8 9
Remaining to be completed: GTK === 5 (check grppkgs.txt on Extra Packages) 9 (warn when doing their own stage3 when using GRP) dialog ====== 8 (recommended button for partitioning) 9
As far as I know, the only remaining item is marking packages as GRP'able on the Extra Packages screen of gtkfe. AllanonJL said he'll be working on that today.
It isn't committed yet, but AllanonJL said it's done :)
Moving to Release Media/Installer.
