On Mon, 2010-05-03 at 09:05 +0200, Thomas Anders wrote: > Robert Story wrote: > > I'd like to move the configure prompts for values earlier in the configure > > process. Currently they are at the end, which means if you fat-finger a > > response (or the configure option that provides the value so that you don't > > need a response), you have to re-run configure and go through the long > > process > > of module configuration again. I don't think this should have any real > > impact, > > but want to run it by everyone (particularly Wes and Dave) to see if > > there's a > > good reason to keep it at the end. > > The obvious downside is that if there's a configure error somewhere > else in the long series of tests, your manual responses may be > (repeatedly) wasted (which may become annoying until you learn how to > avoid them).
This is in fact why I never use the manual configuration. For throwaway configurations I use --with-defaults and for repeatable configurations I use the various --with-<options>. This also has the added benefit of putting the response in the command line history and thus saving me some typing when I mess it up. >From my point of view we could just remove the prompt stuff and make the command line options mandatory. /MF ------------------------------------------------------------------------------ _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
