Well I thought about doing that, and, as I wrote in the DESIGN file (which I was asked to write after others were confused), I wanted to make it portable; and non-Debian systems don't have it. However; if asoundconf is going to change radically, I can easily rewrite it to just invoke that.
On Sun, 2006-12-03 at 19:27 -0500, Daniel T. Chen wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Toby Smithe wrote: > > I have uploaded, and based on advice in #ubuntu-motu, fixed, my package > > asoundconf-gtk. You can find it on REVU here: > > http://revu.tauware.de/details.py?upid=3639 > > A quick perusal of the source makes me wonder why you didn't Depend on > alsa-utils in debian/control and just invoke /usr/bin/asoundconf from > your frontend. Duplicating asoundconf's code in this manner is madness, > as the code base is currently morphing to accommodate the integration of > pulseaudio. Have you inspected how gnome-control-center integrates with > asoundconf? > > Thanks, > - -- > Daniel T. Chen [EMAIL PROTECTED] > GPG key: 0xC88ABDA3 > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.5 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFFc2uMe9GwFciKvaMRAnukAJ9dmkt22kNbKQ/q/LaI6H0/rbqFIgCdFqKd > kDkFVFIBNwrD7F7IeVcscNs= > =Z4HY > -----END PGP SIGNATURE----- -- Ubuntu-motu mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-motu
