[hipl-dev] [Bug 693834] Re: maintain configuration files as separate files
- From: Stefan Götz <693834@xxxxxxxxxxxxxxxxxx>
- To: hipl-dev@xxxxxxxxxxxxx
- Date: Wed, 05 Jan 2011 13:59:28 -0000
I'm skeptical of this 'running from source' business. From my
experience, many tools built with the GNU tool chain do require a 'make
install' invocation for precisely the reasons discussed here.
Personally, I would, in this case, rather go with what other projects do
and people are used to anyway instead of having a custom solution with
the only convenience of saving one the trouble of calling 'make install'
(and maybe giving a custom --prefix option to configure). Just my two
pence.
--
You received this bug notification because you are a member of HIPL core
team, which is subscribed to HIPL.
https://bugs.launchpad.net/bugs/693834
Title:
maintain configuration files as separate files
Status in Host Identity Protocol for Linux:
Confirmed
Bug description:
The configuration files of hipd, hipfw and related HIPL programs are
currently maintained in-source at hipd/init.c.
Examples are:
- HIPL_CONFIG_FILE_EX
- HIPL_HOSTS_FILE_EX
- HIPL_NSUPDATE_CONF_FILE_EX
- hip_init_certs()
This is ugly and leads to the side-effect that hipd needs to be run for the
first time before hipfw can be started, as it needs to generate
firewall_config. Furthermore, as the configuration files are not explicitly
shipped in the distribution packages, they will not be removed on purge.
We need to maintain configuration in separate files, add them to configure.ac
and ensure that the configuration files can also be found in case of running
hipd from source without prior make install.
Other related posts:
