Charles Plessy wrote: > Le Tue, Apr 24, 2007 at 09:17:38AM -0400, Matthew McGuire a écrit : > >> a single tasksel system does sound nice, but it makes building the >> iso images for the installers impossible. If the user can select an >> essentially infinite number of tasks from the one interface then >> the installer would require a disk image too large for CD media. > > Hi, > > I think that a solution was already previously proposed by me and > others: If the pacakges necessary for the installation of the CDDs were > not available, the tasks would be greyed, and when the network is > available, it does not matter that the packages pulled by the CDD are > not present on the physical installaiton medium. > > Have a nice day, >
That is an interesting idea, and I am sorry I didn't see your suggestion in the thread. Although if you are going to display the tasks based on condition of available packages, it might be reasonable to not display the task at all if it's dependencies are not met. However, if you choose to display them in a disabled state it might be good to provide a note on how to enable them in the task selection dialog. Such that disabled tasks can be enabled if you choose a network mirror or add the appropriate CD media during the install. This might be a bit obtuse and could be confusing to new users. IIRC, the tasksel dialog appears well after apt configuration so it might not be a suitable solution. The biggest concern I have with my own idea, is that existing tasks would not be maintained by the tasksel maintainers and therefore would need more collective QA work. The trade-off is that you get people from the CDD team to help maintain their specific task. This promotes the internal team leadership model, but is this a good time or place to test that model? I think so, but I am sure others would disagree. Thanks, Matthew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
