From: Philip Prindeville <philipp_subx@redfish-solutions.com>
To: alsa-devel@lists.sourceforge.net
Subject: Redhat packaging...
Date: Fri, 19 Aug 2005 19:58:47 -0600 [thread overview]
Message-ID: <43068E57.8090900@redfish-solutions.com> (raw)
Well, this is the packaging that Redhat uses, but not where
the CVS build goes as it stands:
[root@mail share]# rpm --query --filesbypkg alsa-utils-1.0.6-3
alsa-lib-1.0.6-8.FC3
alsa-utils /etc/dev.d/sound
alsa-utils /etc/dev.d/sound/alsa.dev
alsa-utils /sbin/alsactl
alsa-utils /usr/bin/aconnect
alsa-utils /usr/bin/alsamixer
alsa-utils /usr/bin/amidi
alsa-utils /usr/bin/amixer
alsa-utils /usr/bin/aplay
alsa-utils /usr/bin/aplaymidi
alsa-utils /usr/bin/arecord
alsa-utils /usr/bin/arecordmidi
alsa-utils /usr/bin/aseqnet
alsa-utils /usr/bin/iecset
alsa-utils /usr/bin/speaker-test
alsa-utils /usr/sbin/alsactl
alsa-utils /usr/share/doc/alsa-utils-1.0.6
alsa-utils /usr/share/doc/alsa-utils-1.0.6/COPYING
alsa-utils /usr/share/doc/alsa-utils-1.0.6/ChangeLog
alsa-utils /usr/share/doc/alsa-utils-1.0.6/README
alsa-utils /usr/share/doc/alsa-utils-1.0.6/TODO
alsa-utils /usr/share/man/man1/aconnect.1.gz
alsa-utils /usr/share/man/man1/alsactl.1.gz
alsa-utils /usr/share/man/man1/alsamixer.1.gz
alsa-utils /usr/share/man/man1/amidi.1.gz
alsa-utils /usr/share/man/man1/amixer.1.gz
alsa-utils /usr/share/man/man1/aplay.1.gz
alsa-utils /usr/share/man/man1/aplaymidi.1.gz
alsa-utils /usr/share/man/man1/arecord.1.gz
alsa-utils /usr/share/man/man1/arecordmidi.1.gz
alsa-utils /usr/share/man/man1/aseqnet.1.gz
alsa-utils /usr/share/man/man1/iecset.1.gz
alsa-lib /etc/alsa
alsa-lib /etc/alsa/alsa.conf
alsa-lib /etc/alsa/cards
alsa-lib /etc/alsa/cards/ATIIXP-MODEM.conf
alsa-lib /etc/alsa/cards/ATIIXP-SPDMA.conf
alsa-lib /etc/alsa/cards/ATIIXP.conf
alsa-lib /etc/alsa/cards/AU8810.conf
alsa-lib /etc/alsa/cards/AU8820.conf
alsa-lib /etc/alsa/cards/AU8830.conf
alsa-lib /etc/alsa/cards/Audigy.conf
alsa-lib /etc/alsa/cards/Audigy2.conf
alsa-lib /etc/alsa/cards/AudigyLS.conf
alsa-lib /etc/alsa/cards/CMI8338-SWIEC.conf
alsa-lib /etc/alsa/cards/CMI8338.conf
alsa-lib /etc/alsa/cards/CMI8738-MC6.conf
alsa-lib /etc/alsa/cards/CS46xx.conf
alsa-lib /etc/alsa/cards/EMU10K1.conf
alsa-lib /etc/alsa/cards/EMU10K1X.conf
alsa-lib /etc/alsa/cards/ENS1370.conf
alsa-lib /etc/alsa/cards/ENS1371.conf
alsa-lib /etc/alsa/cards/FM801.conf
alsa-lib /etc/alsa/cards/GUS.conf
alsa-lib /etc/alsa/cards/ICE1712.conf
alsa-lib /etc/alsa/cards/ICE1724.conf
alsa-lib /etc/alsa/cards/ICH-MODEM.conf
alsa-lib /etc/alsa/cards/ICH.conf
alsa-lib /etc/alsa/cards/NFORCE.conf
alsa-lib /etc/alsa/cards/RME9636.conf
alsa-lib /etc/alsa/cards/RME9652.conf
alsa-lib /etc/alsa/cards/SI7018
alsa-lib /etc/alsa/cards/SI7018.conf
alsa-lib /etc/alsa/cards/SI7018/sndoc-mixer.alisp
alsa-lib /etc/alsa/cards/SI7018/sndop-mixer.alisp
alsa-lib /etc/alsa/cards/TRID4DWAVENX.conf
alsa-lib /etc/alsa/cards/VIA686A.conf
alsa-lib /etc/alsa/cards/VIA8233.conf
alsa-lib /etc/alsa/cards/VIA8233A.conf
alsa-lib /etc/alsa/cards/VX222.conf
alsa-lib /etc/alsa/cards/VXPocket.conf
alsa-lib /etc/alsa/cards/VXPocket440.conf
alsa-lib /etc/alsa/cards/YMF744.conf
alsa-lib /etc/alsa/cards/aliases.alisp
alsa-lib /etc/alsa/cards/aliases.conf
alsa-lib /etc/alsa/pcm
alsa-lib /etc/alsa/pcm/center_lfe.conf
alsa-lib /etc/alsa/pcm/front.conf
alsa-lib /etc/alsa/pcm/iec958.conf
alsa-lib /etc/alsa/pcm/modem.conf
alsa-lib /etc/alsa/pcm/rear.conf
alsa-lib /etc/alsa/pcm/side.conf
alsa-lib /etc/alsa/pcm/surround40.conf
alsa-lib /etc/alsa/pcm/surround41.conf
alsa-lib /etc/alsa/pcm/surround50.conf
alsa-lib /etc/alsa/pcm/surround51.conf
alsa-lib /etc/alsa/pcm/surround71.conf
alsa-lib /etc/alsa/sndo-mixer.alisp
alsa-lib /lib64/libasound.so.2
alsa-lib /lib64/libasound.so.2.0.0
alsa-lib /usr/bin/alsalisp
alsa-lib /usr/bin/aserver
alsa-lib /usr/share/doc/alsa-lib-1.0.6
alsa-lib /usr/share/doc/alsa-lib-1.0.6/COPYING
alsa-lib /usr/share/doc/alsa-lib-1.0.6/ChangeLog
alsa-lib /usr/share/doc/alsa-lib-1.0.6/TODO
alsa-lib /usr/share/doc/alsa-lib-1.0.6/asoundrc.txt
[root@mail share]#
what do I need to tweak to have things go into the right places
(i.e. with a command-line build, "make install LIBDIR=..." etc).
-Philip
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
next reply other threads:[~2005-08-20 1:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 1:58 Philip Prindeville [this message]
2005-08-20 2:20 ` Redhat packaging Lee Revell
2005-08-20 17:16 ` Philip Prindeville
2005-08-20 18:27 ` Lee Revell
2005-08-20 3:09 ` Lee Revell
2005-08-22 12:17 ` Takashi Iwai
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=43068E57.8090900@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=alsa-devel@lists.sourceforge.net \
/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