Hi Jason,

Jason Stewart <[EMAIL PROTECTED]> writes:

> > What about the swig/interfaces/Perl/ directory? swig/scripts/?
>
> I don't know about these two...

You mean you don't know what they are for (in which case I will
just move them to attic) or you don't know whether we should keep
them in Xerces-C++? Are they used in Xerces-P at all?


> I'd like to keep them with the swig directory, but it would be
> possible to move them elsewhere.

If we are to keep them in swig then the whole idea of having only
language-independent part in Xerces-C++ becomes moot since these
two directories (especially interfaces/Perl) appear to be very
language-dependent and I would imagine similar directories would
need to be added for other languages.

So I think we should either make swig truly minimal and language-
independent (and move these two directories to Xerces-P) or we
should move the whole swig out of Xerces-C++.


> >  Also, do we need to install anything from swig (and if so, where)
> >  so that dependant packages (e.g., Xerces-P) don't require source
> >  distribution of Xerces-C++.
>
> Ah.... Good point.... I have been assuming all along that I would
> *need* the source distribution, but maybe not. If people want a binary
> distro of Xerces-P, they can do that via debian or ubuntu. Otherwise,
> if people want to build Xerces-P, I will package the Xerces-C source
> *with* the Xerces-P source - to ensure proper version.

Package maintainers are exactly the people who complain about this
arrangement (see email from Jay in this thread who is maintaining
Debian packages).


> I'm open to changing this plan - but it is complicated - and I am in
> the mood to be simple.

I don't care either way. It is just making maintainer's life complicated
may result in your package being left out of major repositories.

Boris

-- 
Boris Kolpackov, Code Synthesis Tools
Open source XML data binding for C++:   http://codesynthesis.com/products/xsd
Mobile/embedded validating XML parsing: http://codesynthesis.com/products/xsde

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

Reply via email to