[proaudio] libsndfile pre-release versions / ardour svn

[Harald Gutmann <harald.gutmann@xxxxxxx>]

hello,

as for the recent svn versions of ardour 3.0 it is nessacary to have a 
libsndfile version which is just a prerelease version, i'd like to ask to add 
that versions to the proaudio overlay.

This versions can be found here:
http://www.mega-nerd.com/tmp/


kind regards,
Harald

for your interests from the ardour-devel mailinglist:
"[Ardour-Dev] building 3.0 and commit rules
From: Paul Davis
To: ardour-dev@xxxxxxxxxxxxxxxx
 
3.0 now contains both:

    * the merge with 2.0-ongoing
    * Sakari's work on export for his FSoC project

There are several changes to the build as a result:

    * you must now have libogg (>= 1.1.2), libflac (>= 1.2.1)
    * libsndfile has been removed from the ardour source tree
    * you should install a pre-release of libsndfile 1.0.18,
         available from http://www.mega-nerd.com/tmp/

My approach to the above requirements has been to add /usr/local/sndfile
to my system and use it as the --prefix= argument when building both 
a new FLAC and the pre-release libsndfile. I then do this to setup my
environment:

export PKG_CONFIG_PATH=/usr/local/sndfile/lib/pkgconfig:$PKG_CONFIG_PATH
export LD_LIBRARY_PATH=/usr/local/sndfile/lib:$LD_LIBRARY_PATH
export PATH=/usr/local/sndfile/bin:$PATH

These commands are in a file that I source in my shell before starting
work on Ardour. This enables me to continue using the system-supplied
FLAC and libsndfile packages, but to have the new stuff available when
building Ardour. Once I can get new-enough packages for FLAC and
libsndfile from my distro, this will go away (for me).

3.0 is now more unstable than ever, but this is now the focus of my work
on Ardour. This does not mean that work on 2.0-ongoing will stop, but

   **ALL** changes to 2.0-ongoing must be committed to the 3.0 branch
   within 36 hours of the commit to 2.0-ongoing. If you feel that you
   cannot do this, then either ask me to do the commit (if its small
   and easily reviewed), or consider holding off on your 2.X commit 
   until you can do both.

The primary goal for the next few weeks is to get 3.0 into a state where
we can legitimately ask real users to test it.

--p"