Boris Kolpackov <[EMAIL PROTECTED]> wrote:

> My understanding (please correct me if I am wrong) is that there
> are two parts in the swig/ subdirectory. The language-independent
> part (let's call it swig) that can be used to create binding for
> other scripting languages (e.g., Python, Ruby, etc.) as well as
> the language binding for Perl itself (after looking at the source
> code, I release it might not be as clear cut as I've described).
> So the question is whether the whole swig sub-directory is moving
> or just the Perl part of it? Both alternatives seem to make sense:
> . . .

To this discussion, I'd like to add one small point: in order to be
able to build libxml-xerces-perl on debian, I had to modify the debian
xerces packages to install config.status.  Without config.status from
the xerces-c build, it was not possible to configure xerces-p.  The
xerces-c install does not install this by default.  I then had to set
the XERCES_CONFIG variable before building xerces-p.

Now I haven't really verified that this is still necessary for a long
time (maybe 2.5.0), and I don't know whether this issue would
disappear entirely with the new build system, but if you decide pull
xerces-p out and leave swig in (or pull both out, for that matter),
please make sure that the installation of the development files
includes everything that is needed to build the language bindings from
an installed xerces-c.  It's impractical from a packager's perspective
to have a build of one package depend on the availability of the
source distribution of another package.  The usual semantics of a
dependency is that the build of one package depends on the
installation of another package.  This is the way both rpm and
debian's packaging system work.

In other words, if xerces-p is pulled out, then to test this, we need
to make sure we can build xerces-p without a xerces-c source directory
available to the xerces-p build.  Thanks!

--Jay

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to