[csw-pkgsubmissions] newpkgs mpg321, (...)

[Philip Brown]

On Tue, Mar 9, 2010 at 5:10 AM, Maciej (Matchek) Blizinski
<maciej at opencsw.org> wrote:
> On Mon, Mar 8, 2010 at 7:13 PM, Philip Brown <phil at bolthole.com> wrote:
>
>> btw, I wonder if there is an option in mpg123 itself, for the "fast
>> fixed point implementation" option?
>> If so, offering an "alternatives"  alt shared lib in that package,
>> from the proper mpg123 source (rather than mpg321) would be better
>> yet.
>
> Having two versions of mpg123 wouldn't hurt, it's an orthogonal issue.
>
> Why I built mpg321?  It was written because mpg123 wasn't Free.
> mpg321 is still useful to keep up the competition and make sure that
> mpg123 doesn't become closed again; you can think of it as a
> redundancy that removes a single point of failure.
>
> I've added alternatives support for the $(bindir)/mpg123 path.  The
> alternatives system won't overwrite the existing mpg123 binary, but
> when mpg123 starts using alternatives too, mpg321 will be able to
> place the $(bindir)/mpg123 symlink.
>

Thanks for that.
Please also update the description to denote the
performance/implementation difference, though?