Re: multiple crashes in lame

Am Fri, 30 Jun 2017 00:52:22 +0200
schrieb Elio Blanca via Lame-dev <[email protected]>: 

> It probably would be a mess (I have no experience in package
> maintenance), but put it simple: libsndfile has a single part to
> build (the library itself), lame has two (the library and the
> frontend). So, the order would be the lame library (no depencencies),
> then the libsndfile library (which needs libmp3lame) and then the
> lame frontend (which needs the full libsndfile).

Yes, there are ways to achieve this, but it is a pain especially if you
want to support on-the-fly builds of the things (source-based distros
like Gentoo or Source Mage, what I am dealing with, or also BSD ports).
You need to artificially split up upstream packages into these pieces.
This happens anyway for binary distros like Debian, because you gain
some flexibility/optimisation of disk usage in the end. Source-based
usually coincides with small user base and rather small developer count
… getting a wild mix of compilers and libs working with rolling release
from sources is tricky enough.

Anyone trying to just even build the software by hand to get some
proper versions on some special system that does not package them will
curse you for inflicting circular dependencies. While consumption of
binary packages from a distro is the norm nowadays, Open Source
software should always offer the option to just grab the source and
play with it, with a clear order of what depends on what.

That being said … one could separate lame frontend from lame library
and serve them as two independent upstream packages. But it's still
more work taking care of two lame packages (with diverging versions)
than one. 

</packager_maintainer_rant>

And, to get back on topic: Does libmp3lame feature the option of
transcoding from MP3 to MP3 or is that only in the frontend? I guess at
least the transcoding of arbitrary libsndfile formats to MP3 would be
left to the frontend only. But then … a generic libsndfile frontend
might be a more proper solution. People who actually use lame on the
command line might just be crafty enough to decode other formats to WAV
first with other tools … the Unix way and all that …


Alrighty then,

Thomas
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Lame-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lame-dev