Bart Smaalders wrote: > > So you would find the Marvell Yukon ethernet interface SVR4 driver package > that prompts for IP address, netmask, etc, during installation to be a > model to emulate? > > The packaging system must be able to install the software w/o running > any of it. You are conflating configuration and installation. What > happens if I > wish to make a change in configuration post-installation? >
An ideal packaging/configuration "system", should allow for any/all 3 combinations, and more, of: 1. Just install the "bits",but do configuration later 2. Install the "bits", and go right into configuration, ideally as automated as possible 3. Allow for REconfiguration, post install. Some people like behaviour like #1. However, some people prefer behaviour like #2. Ideally, the example you gave, should be allowable, *IF* the end-user likes his software to behave that way. As someone else observed; it would be nice if sun provide some kind of general configuration interface/api/whatever. Then, the user/admin could globally declare his preference of #1, or #2, and it would no longer be up to the whims of the package creator which path to follow. (and as a side effect, #3 would fall out naturally) The choice would then be up to the end user, which is where it belongs. Not in the hands of the package creator, NOR the hands of the packaging SYSTEM creators. You do a disservice to end users, if you set things up so that it *cannot* behave in the manner of #2, above. _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
