hi,
On Wed, Jun 06, 2007 at 09:26:13PM +1000, Erik de Castro Lopo wrote:
> Michael Ablassmeier wrote:
>
> > indeed, shipping your own flac source and linking against it is more error
> > prone and might lead to further bugs .. (and means also more work ..)
>
> Firstly, the main reason I am shipping a subset of the FLAC sources
> as part of libsndfile is to make building a FLAC enabled libsndfile
> easier on MacOSX and windows.
>
> Secondly, I intend to sync the FLAC sources in libsndfile against
> FLAC CVS and test it thoroughly before each release.
>
> Finally, the current bug in libsndfile (ie not building) was caused
> by changes to the FLAC API, a problem which can never occur again
> if I ship a verify subset of the FLAC sources with libsndfile.
as long as libsndfile can still be dynamically linked against the version in
debian this is no problem. But having a debian package which does need to
ship/build its own libflac and link against it, is IMHO opinion useless and
duplicates work (might also waste mirror space).
Ive been in the same situation with streamripper. Its author ships both libtre
and libmad with his source archive, but still allows me to remove it from the
tarball and link against the versions in debian - that doesnt waste mirror
space and saves build time + i dont have to mess with bugs in the libtre /
libmad versions from his tarball.
bye,
- michael
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
