> 
 > My only concern is if the headers/libs change between versions. I 
 > don't think this should be a problem with libraries--they have the 
 > version number appended. But what would happen if someone still had 
 > old libraries and we replaced the headers? Should we have 
 > htdig-${VERSION} instead of just htdig?
 > 

 I think the same problem arise for binaries (htdig, htsearch ...) which
are installed in prefix/bin without version number appended anywhere. I assume
every system administrator is aware of that pitfall since it's the same
with most packages. What we could provide is a GCC like installation scheme:
you never destroy an existing installation and can switch back to a previously
installed by changing a few symbolic links. I've never done that myself but
it seems possible.
 I'm afraid such a scheme would be overkill for most people. On my system
I would rather install a new htdig version in a separate directory 
($HOME/local) and try it before replacing the system version in /usr/local.
It's also a bit more complex to do since there is no direct support for that
in automake.
 Let me know if this seems particularly important to you.

 Cheers,

-- 
                Loic Dachary

                24 av Secretan
                75019 Paris
                Tel: 33 1 42 45 09 16
                e-mail: [EMAIL PROTECTED]
                URL: http://www.senga.org/


------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED] 
You will receive a message to confirm this. 

Reply via email to