On Tue, Nov 01, 2005 at 09:53:25PM +0100, Jonas Smedegaard wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 1 Nov 2005 17:27:42 +0100 > Sven Luther <[EMAIL PROTECTED]> wrote: > > > On Tue, Nov 01, 2005 at 04:11:19PM +0100, Jonas Smedegaard wrote: > > > > On Mon, 31 Oct 2005 09:03:23 +0000 > > > Alastair McKinstry <[EMAIL PROTECTED]> wrote: > > > > > ie. for filesystem, try ext3 first, if this cannot be done, use > > > > ext2. > > > > extend the parser to handle this > > > Also, another idea would be for yaird to not necessarily fail fatally > > like it does now, but ask the user to help him resolv the errors, > > preferably using debconf :) > > Well, using debconf is packaging. It requires one of the following from > the yaird tool itself:
Well, i disagree, you need to modify each case where yaird sends a message to the user to use a debconf note, instead of a text output, and the same for input. This is orthogonal to the current proposal though. > 1) options to allow overriding the default automated resolving Yep, well, in each case where we have fatal, we have it because we failed to file some random variable (or piece of info or whatever) needed by yaird. If instead of failing with fatal, we output some explanatory message (like we couldn't find root), and asked the user about filing in a value for it (please tell us on what partition your root filesystem lives ?), where he can just enter to abort, or give the value for yaird to continue. > 2) more finegrained configuration Yes, and no, as said, my thinking was to do it directly inline, during the parsing and generation phase. Maybe ugly code though. > For the second to work with debconf it also requires writing packaging > script that interacts with the configuration file format (read: > packaging scripts written in perl so that the perl config parser can > be used) or the config format changed to the simpler line-based one > used with most shell-based scripts (the format mandated > for /etc/default/* scripts in Debian). Nope, yaird could use debconf directly to communicate with the user, instead of pure text like right now, ideally all the user interaction would be abstreacted in their own perl module, and there would be a debconf and a text version of it or something, in order to not cause ugly patching for non-debian usage or something. You are makind debconfification much more complicated than it really needs to be :) Friendly, Sven Luther You are makind debconfification much more complicated than it really needs to be :) Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
