On 12/10/13 14:00 +0100, john ffitch wrote:
> If you do not use Linux ignore this message!
> 
> In a discussion yesterday I wondered if we are supporting Linux
> systems adequately.   Our general view has been to release sources and
> assume Linux users have the build-tools and expertise to install.  I
> would like to know if this is correct.  I know I build it regularly
> but people frequently tell me I am non-normal for using the command
> line without Gnome or KDE....
> 
> We have often created SuSE .rpm files and Debian create .deb files
> suitable for them and Ubuntu.  I wonder what happens to Fedora and all
> the other distros.
> 
> So, possibly off-list, could you tell me which distro you use, do you
> self-compile or use a package (and which one).
> 
> It may be that this is not an issue, but I would like to know.

I build from source and install to a network location, unpackaged.  I 
don't use any of the GUI frontends either, so maybe this workflow will 
be of interest to others who are similarly (dis)inclined.

	git clone git://git.code.sf.net/p/csound/csound6-git csound6-git
	cd csound6-git
	mkdir build
	cd build
	(Use the output of `git describe --tags` to get a version string)
	cmake -DCMAKE_INSTALL_PREFIX:PATH=/nfs/sw/csounds.com/csound-6.0.1-179-gf26d37a ..
	make
	make install

I use the Modules system (http://modules.sourceforge.net/) to bring the
desired version in to the environment.

	module load csound/6.0.1-179-gf26d37a

The Modules setup looks like...

	ash$ ls -la /nfs/modules/csound/
	total 10
	drwxr-xr-x  2 jlucas root   11 Sep 29 02:56 .
	drwxrwxr-x 36 root   staff  36 Aug 29 00:25 ..
	lrwxrwxrwx  1 jlucas root    8 Jun 18 02:41 5.14.2-265-g48b7a27 -> .csound5
	lrwxrwxrwx  1 jlucas root    8 Jun 18 02:41 5.18.03-181-g17a05cd -> .csound5
	lrwxrwxrwx  1 jlucas root    8 Jun 18 02:41 5.18.03-212-g66fd830 -> .csound5
	lrwxrwxrwx  1 jlucas root    8 Jun 18 02:41 5.18.03-212-g66fd830-midiclock-dev -> .csound5
	lrwxrwxrwx  1 jlucas root    8 Sep  4 20:34 6.0.1-128-g423d52a -> .csound6
	lrwxrwxrwx  1 jlucas root    8 Sep 29 02:52 6.0.1-179-gf26d37a -> .csound6
	lrwxrwxrwx  1 jlucas root    8 Sep  4 20:34 6.0.1-2-ge93e876-envvarpath-dev -> .csound6
	-rw-r--r--  1 jlucas root  602 Jun 18 02:26 .csound5
	-rw-r--r--  1 jlucas root  453 Sep  4 01:45 .csound6
	[last: 0s] [12:07:31] [/nfs/modules]
	ash$ 

The Csound 6 modulefile...

	ash$ cat /nfs/modules/csound/.csound6
	#%Module

	module-whatis "Csound audio synthesis tool"

	conflict csound

	set version [file tail $ModulesCurrentModulefile]
	set appdir /nfs/sw/csounds.com/csound-$version
	set bindir $appdir/bin
	set libdir $appdir/lib

	setenv OPCODE6DIR64 $appdir/lib/csound/plugins64-6.0
	setenv OPCODE6DIR $appdir/lib/csound/plugins64-6.0

	setenv CSOUNDVER $version
	setenv CSSTRNGS $appdir/share/locale

	prepend-path PATH $bindir
	prepend-path LD_LIBRARY_PATH $libdir

Further, I load a "project" modulefile to define paths for each project, e.g.

	ash$ module show project/default
	-------------------------------------------------------------------
	/nfs/modules/project/default:

	module-whatis    General project settings. 
	setenv           SAMPLERATE 44100 
	setenv           KRATE 44100 
	setenv           BITDEPTH 16 
	setenv           TMPDIR /nfs/work/taiga/tmp 
	setenv           QTRACTORVER 0.5.7.6-r3140 
	setenv           CSOUNDVER 5.18.03-212-g66fd830 
	setenv           CSOUNDRC /nfs/work/taiga/.csoundrc 
	setenv           SFOUTYP WAV 
	setenv           SSDIR /nfs/work/taiga/asset/pcm 
	setenv           MFDIR /nfs/work/taiga/asset/mid 
	setenv           SFDIR /nfs/work/taiga/render 
	setenv           SADIR /nfs/work/taiga/asset/pvo 
	setenv           INCDIR /nfs/work/taiga/include 
	module           load qtractor/0.5.7.6-r3140 
	module           load csound/5.18.03-212-g66fd830 
	module           load aliases 
	prepend-path     PATH /nfs/work/taiga/bin 
	-------------------------------------------------------------------

You can see I use environment varibles quite extensively, which is why 
I was so interested in seeing the environment variables correctly 
support the Unix standard colon (:) delimiter.  Now that it does, 
INCDIR will probably look more like...

	setenv INCDIR /nfs/work/taiga/include/orc:/nfs/work/taiga/include/sco

I highly recommend the Modules system as a way to manage different 
versions of software on Unix.