"Arnold, Curt" wrote:
>
> Sorry, some more *nix novice questions.
>
> If trying to get Xerces in the distributions is primarily to allow already compiled
>code to run without having to provide the .so's, would an binary/runtime drop that
>did not have header files resolve
> the collision issue?
That would be silly. One of the reasons for a library being already
present is that an application that needs it can then be built easily.
That couldn't happen if the headers weren' installed too. This is all
very standard and there are established ways to package and distribute
software on Unix/Linux.
> People who wanted to rebuild applications could download either a binary/build or
>source drop with the current include strategy.
>
> Could you provide sample full path names of where the files would be installed in a
>distribution or with an RPM install? This will show my *nix ignorance, are you
>saying that the Xerces's include
> files would go into some common include directory with include files from other
>installed packages? This doesn't seem plausible since there would not be a mechanism
>to distinguish headers from
> multiple versions of Xerces if they are all in /local/include/xerces or something
>like that.
Yes, headers are installed in e.g. /usr/include or /usr/local/include.
Yes, there is a general problem on linux of conflicting headers from
different versions. GTK+/GNOME has started to solve this by using
version sub-directories, but that's another issue that I would tackle
after getting this most simple of issues out of the way first.
>
> My current vote would be a -0. The change looks disruptive and my instinct is that
>either the justification isn't strong enough or that something short of renaming src
>could do the job for end-users
> of applications that use Xerces, however I'm not a Linux developer.
Your abstain is appropriate because of your lack of understanding of
Unix libraries.
> Could anyone provide URL's to resources that describe appropriate naming and
>location strategies for *nix include files?
There must be something out there. If not then there should be. However,
it's something that you soon learn when building and installing
libraries from source.
>
> P.s. Only committer votes are binding (and I'm not one), other votes are advisory,
>so you might mention your status when you vote.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
--
Murray Cumming
www.murrayc.com
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
