FFADO-ppa

The first packaging I did with my ppa was FFADO. Just like working with prevu, I needed to build the updated or non-existing dependencies in Hardy to build JACK and Ardour.

Under my ~/build directory I created a /ppa directory and copied my ~/build/libffado directory into it and renamed /libffado to /ffado-ppa

I edited the ~/build/ppa/ffado-ppa/libffado-2.0~rc1/debian/changelong file.

libffado (2.0~rc1-0ubuntu3~ppa2) hardy; urgency=low

* backport to hardy (LP: #469717)

-- Scott Lavender (ubuntustudio-dev) Sun, 01 Nov 2009 15:33:00 -0600

libffado (2.0~rc1-0ubuntu2) jaunty; urgency=low

* Fix linking against libffado (broken symlink) (LP: #332692)
* Rename README.Debian.source to README.source
* Install a .desktop file and icon for ffado-mixer.
* Drop ffado-mixer-qt3 (see README.source).

-- Andrew Hunter Mon, 23 Feb 2009 16:17:25 -0500

Notice I updated the revision number and changed the Ubuntu version to hardy. Both critically important. Also I followed the exact format including spaces and empty lines.

Next I change directories up one level so that I was at ~/build/ppa/ffado-ppa/libffado-2.0~rc1 to start building the package.

cd ..
debuild -S

Once again I moved up one directory and transferred the correct files to my ppa

cd ..
dput hardybackports libffado_2.0~rc1-0ubuntu3~ppa2_source.changes

The quick witted will notice the ppa2 tag at the end of the package version. This was because I originally forgot to change Ubuntu's version from jaunty to hardy. Since I had already transferred a ppa1 version to my ppa I had to build it again with a new version number.

After that I waited a few hours and the package was built for me.
https://launchpad.net/~slavender/+archive/ppa

libffado

I have found that in order to build the packages that I had originally intended, i.e. JACK and Ardour, than I would need to package several others during this process. Notably, I needed to build the FFADO driver (libffado).

To this end, I first created a created under my /home directory called /build. Not very imaginative I admit.

mkdir build

This will be the main directory where other directories will be stored for the various applications and their respective source packages to be stored.

Next, I moved into the build directory and created another directory for libffado. Move into the new directory also.

cd build
mkdir libffado
cd libffado

Then I downloaded the source package.

apt-get source libffado

Under the /libffado directory that I created this created a /libffado-2.0~rc1 directory, a libffado_2.0~rc1.orig.tar.gz archived package, a libffado_2.0~rc1-0ubuntu2.diff.gz archived package and a libffado_2.0~rc1-0ubuntu2.dsc file.

The directory is for the source files, the orig.tar.gz is the original tarball from upstream, the diff.gz is a tarball of the differences between the original and the Ubuntu built pacakge and the .dsc file is a description file.

Okay, now comes the really hard part; running prevu. First we need to change directory to the source code directory and then type:

cd libffado-2.0~rc1
prevu

That's it, watch it work. It might be a while though.

If everything works well you will be told that you have a .deb file located under the /var/cache/prevu/hardy-debs directory. Of course, this is for Hardy 8.04.

Next I will be moving onto libcelt-dev because JACK requires it as a build-depends. This will provide the capability for Hardy users to use netjack if they build the CELT codec, which is a low latency codec for sending audio over the net.

The decision to build libcelt-dev was slightly difficult for me because of my general ignorance of package building. It was either build CELT also or remove it as a build-depends but then I would have jacked with the changelog and then had to change the version number of JACK and I decided that it would be simpler (hopefully) just to build CELT before building JACK. I suppose we shall find out.