[Freeipa-devel] [PATCH] autotoolize ipa-client

[Karl MacMillan]

On Wed, 2007-10-17 at 12:07 -0400, Rob Crittenden wrote:
> William Jon McCann wrote:

[...]

> > I just don't see any compelling reason to package the server and
> > client together.
> 
> I was proposing only the source would be packaged together. Each 
> component would be separate, but it still raises the issue where only 
> one piece needs an update you've gotta build them all.
> 
> So I think I'm ok leaving them separate for now. We still may want/need 
> some top-level Makefile to do something useful. I use make-localdist all 
> the time to build the packages for testing.
> 
> Now, onto some uglier stuff. I poked further at what changes would be 
> required for hardcoded paths and what I found isn't pretty.
> 
> We have a slew of references to /usr/ in there, from the installer to 
> runtime components. I think at least we should centralize this into one 
> or two places (/etc/ipa/ipa.conf or some ipaconfig.py file).
> 
> The files affected are, at a minimum:
> 
> ./ipa-gui/ipa-webgui
> ./ipa-install/ipa-server-install
> ./ipa-install/share/kdc.conf.template
> ./ipa-install/test/Makefile
> ./ipaserver/dsinstance.py
> ./xmlrpc-server/funcs.py
> ./xmlrpc-server/ipa.conf
> ./xmlrpc-server/ipaxmlrpc.py
> ./xmlrpc-server/test/README
> 
> Most of these are: sys.path.append("/usr/share/ipa/")
> 
> The two init files (ipa-webgui and ipa-kpasswd) both refer to /usr/sbin.
> 

Added ticket #47 to track this. Whenever we make the change we need to
be careful to separate out things that we now at ipa build time
(e.g., /usr/share/ipa) and things that are system dependent (like the
location of the DS setup tools). The latter needs to be configurable on
the end system?

Karl