Adding Ubuntu 12.04 instructions.

[jc00ke]

Closes #278

[PromyLOPh]

Thanks for the pull request. Although I rejected a similar pull request
in the past (#249) I feel there’s demand for this kind of information.
So, I see a few options how to proceed now:

1. Apply as is. Con: Document is going to get very
   long/confusing as we add more distributions
2. Every distribution into a single file (INSTALL.debian,
   INSTALL.ubuntu, …). Con: A lot of files in the root directory
3. Reject the pull request.
4. Enable the github wiki and put it there. Con: Fragmentation of
   information, pro: everyone can edit
5. Actually solve the problem by providing up-to-date packages for every
   Linux distribution, so noone has to build the latest pianobar from
   source. Con: A lot of work, pro: Package manager/packager handles all
   the ugly bits (dependencies, updates, …)

At the moment 2) is my favorite. What do you think? :)

[jc00ke]

I would vote for option 1. As long as we keep the INSTALL file in alphabetical order for operating systems, it shouldn't get too bad.

If option 2 were to be taken, I would suggest creating a install/ directory so the root directory isn't muddied. INSTALL could just say Find OS-specific instructions in the install/ directory

But yeah, +1 for option 1 ;)

[PromyLOPh]

Applied with minor modifications (tabs not spaces, removed git clone –
we assume you already have a checkout/tarball/whatever if you’re reading
INSTALL). We’ll see how well this works – thanks :)

[PabloTwo]

There seems to be no requirement for libfaac-dev to build pianobar in Ubuntu >=12.04, or any other Linux distribution. libfaac is an encoder, libfaad is the decoder. I am a Fedora user and not an Ubuntu user. Of course, installing libfaac-dev does no harm, but, in my opinion, should not be listed as a build requirement when it is not.

[jc00ke]

I can confirm that libfaac-dev isn't needed on Ubuntu. Sorry for not checking first!

[PromyLOPh]

What about gcrypt? It isn’t listed in the apt-get command.

[jc00ke]

@PromyLOPh I don't have gcrypt installed & I'm listening to pianobar as I type ;)

[PromyLOPh]

I merged your fixes.

[PabloTwo]

@jc00ke - Clearly, libgcrypt-dev (assuming that's the correct file name in Ubuntu) should be in the build requirements list. Although pianobar may compile without complaining without libgcrypt-dev installed, doing so disables the ability to use that function. I build pianobar into rpm packages (32 and 64 bit) for Fedora users, including libgcrypt-devel (Fedoras name). Using the rpm command to query the built pianobar rpm package what its "requirements" are when the gcrypt header files are present during the build, included among the list are, for 64 bit::

libgcrypt.so.11()(64bit)
libgcrypt.so.11(GCRYPT_1.2)(64bit)

A user installing my rpm package would have the libgcrypt rpm package pulled in as a dependency if it were not already installed on his system. Maybe too late to add this comment after being "Closed" ?

[jc00ke]

@PabloTwo libgcrypt11-dev must have already been installed on my system. Oops.

[PromyLOPh]

So we have to add libgcrypt11-dev to the apt-get too?

[PabloTwo]

Yes, libgcrypt11-dev should be included in the list of packages to install in the Ubuntu specific instructions.

And thanks for a great program (pianobar) and all your efforts at keeping up with the API changes.

[PromyLOPh]

Fixed.