It looks like the relevant lame package for MP3 support is available at
http://rpmfusion.org/.
RPMfusion is specifically for packages that Red HAt, and thus Scientific
Linux,, is unable to put in their default operating system due to licensing
issues. Fortunately for you, our friends at Scientific Linux have made it
available if you install the yum-conf-rpmfusion package.
Whether it is *legal* to use those packages, whether you are in the USA
where the MP3 software is patented and software patents are valid, is your
own problem if you download and use the software. Be very careful of these
licensing issues.
Nico Kadel-Garcia
On Tue, Oct 29, 2013 at 1:25 PM, John Pilkington j.p...@tesco.net wrote:
On 29/10/13 16:25, Elio Fabri wrote:
On 10/27/2013 11:41 PM, Nico Kadel-Garcia wrote:
Life don't work that way. Since you're using Scientific Linux, you
have the option to do this:
yum install yum-confi-epel # This enables the EPEL repository
yum install audacity # This will fetch audacity from the upstream EPEL
repository, and resolve the other dependencies as well from EPEL and
the other available repositories.
OK. I installed the EPEL repo.
On 10/27/2013 11:02 PM, John Pilkington wrote:
I just installed the 32-bit version. The 32-bit versions of all the
above packages (including audacity) are in the epel repo and yum should
install them if you have that repo enabled. I uaed yumex, but I think
the command line would be yum --enable-repo=epel install audacity
I couldn't find che 32-bit version.
There is a 64-bit beta version instead.
Maybe because it's beta, it cannot import mp3 files, but is better than
nothing.
Thank you both
Glad you got it.
I installed the 32-bit version because that's what my (old) machine needs.
I just hadn't checked if all the equivalent 64-bit packages existed.
The mp3 limitation will likely be to avoid any potential legal challenges.
The other suggested source in this thread might not have the same
restriction, but I have no idea how reliable it might be.
I notice that you sent your reply to the list-owner as well as the list.
The 'reply' mechanism here seems rather strange but I think you should
only send to
SCIENTIFIC-LINUX-USERS@FNAL.**GOVSCIENTIFIC-LINUX-USERS@FNAL.GOV
Cheers,
John P