[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xine-devel
Subject:    Re: [xine-devel] Re: [xine-cvs] CVS: xine-lib configure.ac,1.186,1.187
From:       Michael Roitzsch <mroi () users ! sourceforge ! net>
Date:       2003-11-03 13:07:56
[Download RAW message or body]

Hi Siggi,

> > CC'ing Siggi and Manfred, the package gurus,
>
> (removing all those CCs as we're all subscribed to xine-devel...)

Maybe not everyone followed this thread. Sorry if I caused 
inconvenience.

> > For our packagers who might not have followed the whole thread:
> > Since Rocky promised to take care of correct versioning, xine-lib
> > currently uses external versions of vcd libraries (libcdio, libvcd
> > and libvcdinfo) by default, if they are available and sufficiently
> > new. It is now your decision, wether to rely on these external
> > versions and have an additional dependency or use internal
> > versions, which can be forced with --with-internal-vcdlibs.
>
> For the Debian package, I'd have to do that, and yes, it would fix
> the issue. But it would do so only for the .deb package.
> I'd strongly recommend to make the same addition to the .spec files
> in case we really default to external versions.
> I hope that makes my original point more clear: If the configure
> script just defaults to internal copies, we'd save those switches at
> many other places, plus we'd safely have all inexperienced users who
> install from source use the included copy, too. IMHO, that's the
> safes thing we can do from the support point of view: this minimizes
> the variations of xine-lib found "in the wild".
> Once libcdio and libvcdinfo become commonly included in
> Distributions, (at which time they'll be sufficiently stable to
> assume that upgrading them won't break anything), I'm all for linking
> them dynamically. It's just that I don't see this is the case right
> now...
>
> Right now, I don't see any advantage in using external
> libcdio/libvcdinfo for the large majority of users who's _not_
> knowing what they're doing. Those who _do_ know that they're doing
> can safely be identified by the ability to specify
> --with-external-vcdlibs (or whatever switch/switches configure is
> finally going to supply).
>
> Guess that's all I can say about the topic.

As I said, my patch was not meant to end any discussions. I just fixed a 
bug in configure. If people do not like the fix and there is a majority 
favoring a different solution, I cannot stop you from changing the cvs 
again.

Michael

-- 
"Hey, it's Unix! I know this!" 
	-Lex, Jurassic park. 



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?   SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
xine-devel mailing list
xine-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xine-devel
[prev in list] [next in list] [prev in thread] [next in thread]