From: Seemant Kulleen <seemant@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] the mpg123 fiasco
Date: Wed, 01 Oct 2003 00:30:22 -0700 [thread overview]
Message-ID: <1064993422.15475.2.camel@localhost> (raw)
Hi All,
So, mpg123 has its share of problems, not least of which is its
licensing. So, the proposed solution is to have a virtual/mpg123 which
mpg321 will provide by default. I understand that there is one package
which will need some patching (and it's being looked into -- the names
of the package and the looker-into escape me right now, because my brain
is made of swiss cheese) to work with mpg321 as a drop-in replacement.
So, if everyone is ok with it -- I will institute this change in about
48 hours. If you agree with this solution, please do NOT respond. Only
respond if you disagree (and please give a logical explanation).
thanks,
--
Seemant Kulleen
Developer and Project Co-ordinator,
Gentoo Linux http://dev.gentoo.org/~seemant
Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x3458780E
Key fingerprint = 23A9 7CB5 9BBB 4F8D 549B 6593 EDA2 65D8 3458 780E
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-10-01 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 7:30 Seemant Kulleen [this message]
2003-10-01 14:37 ` [gentoo-dev] the mpg123 fiasco Ned Ludd
2003-10-01 14:49 ` Sven Blumenstein
2003-10-01 15:51 ` Lisa Seelye
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1064993422.15475.2.camel@localhost \
--to=seemant@gentoo.org \
--cc=gentoo-dev@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox