On 6/2/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
On further consideration I don't see the necessity for this. We don't
say this about lib-ossp-uuid although it too is only used for a contrib
module.
And is it good? For that functionality I would also add comment
describing that this "--with
Nikolay Samokhvalov wrote:
On 6/2/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
On further consideration I don't see the necessity for this. We don't
say this about lib-ossp-uuid although it too is only used for a contrib
module.
And is it good? For that functionality I would also add commen
Andrew Dunstan wrote:
Nikolay Samokhvalov wrote:
The current CVS' configure is really confusing: it has "--with-xslt"
option, while there is no XSLT support in the core. At least let's
change the option's comment to smth like "build with XSLT support (now
it is used for contrib/xml2 only)".
On 5/20/07, Andrew Dunstan <[EMAIL PROTECTED]> wrote:
contrib is a misnomer at best. When 8.3 branches I intend to propose
that we abandon it altogether, in line with some previous discussions.
We can change the configure help text if people think it matters that
much - which seems to me much m
Nikolay Samokhvalov wrote:
The current CVS' configure is really confusing: it has "--with-xslt"
option, while there is no XSLT support in the core. At least let's
change the option's comment to smth like "build with XSLT support (now
it is used for contrib/xml2 only)"...
contrib is a misnom
On 4/15/07, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
Well, if we're going to make libxslt an explicit thing, then it'd be
trivial to add an xslt transformation function into the core, and then
I think we can claim equivalent support. But we'll have to check the
details, of course.
I have bee
