Re: Automake and directories
Piotras <pp-VVDi8QVAvoBWk0Htik3J/[email protected]> Fri, 17 Feb 2006 18:06:23 +0100
| Newsgroups | gmane.comp.web.midgard.devel |
|---|---|
| Message-ID | <[email protected]> |
Jukka Zitting <[email protected]> wrote: > The default ./configure would put these in: > > MIDGARD_CONF_DIR=/usr/local/etc/midgard/conf.d > MIDGARD_BLOB_DIR=/usr/local/var/midgard/blobs > MIDGARD_SHARE_DIR=/usr/local/share/midgard > > The current custom paths could be recreated with: > > ./configure --prefix=/usr --sysconfdir=/etc --sharedstatedir=/var/lib The less configure options we have the better. But I think I need some use case, as I think about apache and php modules now. And I find this very difficult for them. At least it makes core's data handling much more difficult as you need to pass this variables to core somehow. Couldn't we just define these paths in configuration file? You can get midgard config property value then and forget about setting it somehow. So paths calculation may be defined statically when core is configured and compiled and later defined by user ( admin , developer ) in configuration file. Then : * you write application once * configure and build without need to define additional parameters * share among different environments even the same binaries So for exmple I build debian packages which by default follow debian policy and fsh while torben is able to use them ( without any need to rebuild ) in chrooted environments. Piotras