Temüjin
November 18th, 2009, 11:48 PM
Sorry if this seems n00bish. I've made some simple .deb's before, but never tried to reconfigure existing Ubuntu packages.
libcanberra can use different backends: null, ALSA, PulseAudio, OSS,
GStreamer.
Since the PulseAudio backend requires PulseAudio >= 0.9.11, this package uses ALSA for testing purposes. It is planned to use PulseAudio as soon as it is released. It is also planned to have different inter-conflicting packages for configurable backend installation.
I want to build a libcanberra source package configured to use the gstreamer backend and distribute it in a PPA. Unfortunately, libcanberra is not easily configurable. It checks for outputs in the order - ALSA, PulseAudio, OSS, gstreamer. The first one found is used.
So I have all the dependencies and I download the source package:
apt-get source libcanberra
Then I edit the debian rules to configure the way I want it. Now what else do I need to do besides cleanup the control file? Then what do I do?
libcanberra can use different backends: null, ALSA, PulseAudio, OSS,
GStreamer.
Since the PulseAudio backend requires PulseAudio >= 0.9.11, this package uses ALSA for testing purposes. It is planned to use PulseAudio as soon as it is released. It is also planned to have different inter-conflicting packages for configurable backend installation.
I want to build a libcanberra source package configured to use the gstreamer backend and distribute it in a PPA. Unfortunately, libcanberra is not easily configurable. It checks for outputs in the order - ALSA, PulseAudio, OSS, gstreamer. The first one found is used.
So I have all the dependencies and I download the source package:
apt-get source libcanberra
Then I edit the debian rules to configure the way I want it. Now what else do I need to do besides cleanup the control file? Then what do I do?