From: Jorge B. G. <yor...@gm...> - 2007-09-27 19:04:39
|
Continuing with the packaging work, I'm looking at the current configuration scripts in the fisterra-distribution packages. The script is useful, but you can run it only when you install the package, and the fisterra applications are complex ones. I can't assume the user has the database and the name-server properly configured when they decide to do "apt-get install fisterra2-distribution-server". Possibly the user doesn't know he needs it yet. In addition, you could change the configuration of your nameserver or database after been working with it. So my proposal is to provide a configartion script independent from the debian package, so the user could run it when it's needed. In the package configuration script could be given the option to configure fisterra at that moment or, if the user doesn't have the database and nameserver ready, give an advise that he can (and should) run the configuration script later. I'm even thinking in just install a default configuration file with the package, and mention the configuration script in the README file. The debian policy recommends this, and I've seen several packages that does it. What do you think? does it seems a good idea? Any other ideas? |