Yesterday, Klaus Knopper schrieb:
[snip]
> > agreed. But there is a problem with that: csounders use a variety of
> > systems (libc5, glibc2, X, no X etc.) so it is quite hard to fit
> > binary distributions for everybody... You are more than welcome
> > to try, however.
>
> There are two solutions for this:
>
> a) The Source RPM should be easy to build on any linux system, old or new, with
> the bugfixes included in the Spec file (rpm --rebuild csound.src.rpm gives you
> a binary RPM optimized for your specific system).
>
> b) I could provide an additional statically linked binary RPM that should
> run independently from what kind of libs you use. This increases the size
> of the binaries, of course, but at least would work for all systems.
I think *both* solutions are appropriate...
[snip]
> Hmm.. Is there a link to this distribution on the csound main site? I must have
> missed it, otherwise I would probably have started with your version.
unfortunately this 'unofficial' distribution never went very far
in the canonical circles: it was criticized and I was attacked on
personal grounds, so I lost interest in trying to push the point that,
as there are specialized Mac and Windows versions, there could be a
linux one taking advantage of the specific instruments of the platform.
I did my own and that was that - never pushed anyone to use it, but
still had quite a following at least for some time (I don't know now -
perhaps everybody is happy with it so nobody complains... :))
>From what I know, Maurizio Umberto Puxeddu builds sources and binaries
tar files which should be available from http://www.tiscalinet.it/~umbpux
(I'm not 100% sure about the URL), and Dave Phillips in his excellent
page about linux audio applications reports it. The only thing *I*
currently maintain is the CVS repository (I add the blurb about using
it at the end of this message - it's pretty old but still valid) - it
is probably time to move it to sourceforge but I need some time which
I don't have right now.
> How do you make sure you don't get out of sync with the "official" csound
> distribution?
Ah well (*long story made short*). I have built a semi-automated procedure
which is based on two CVS repositories: csound-linux and csound-canon
(yes, I keep a CVS repository of the canonical distribution too...).
I diff the canonical repository at each new version, purge the diffs
by hand and apply them to the linux version. It does'nt work *all* the
time, but most of the time I get done with 20 min. work - and it works...
There are several issues still left open - but I use csound very intensively
(for production and teaching) and it is essential for me to have
a pretty solid distribution under linux - this way I can count on one...
As always, I'm not pushing the envelope here: you may want to use whatever
distribution you think fit for your purpose. And if you want to add a
fixed procedure to build RPMs out of the unofficial distributions, you
are certainly more than welcome and I will add it.
ciao
nicb
+----------------------+
|Nicola Bernardini |
|E-mail: [EMAIL PROTECTED] |
+----------------------+
------------------------------------------------------------------------------
Some of us csound users/hackers, (mostly) working on Linux platforms, have
decided to use some of the source control tools (cvs) in maintaining the
linux sources for csound. In this development tree, we intend to track
fixes and addition to the canonical sources, and add bug fixes, new opcodes
and functionalities. Likewise, we intend to submit appropriate bugfixes
and enhancements back to the maintainer of the canonical source.
The development tree, known as the csound CVS repository,
can also be accessed anonymously for reading (instructions below).
This way, all interested parties can have access to the latest snapshot
sources and also any intermediate linux release. We will continue to
maintain binary and source distributions in the usual places,
but we plan to be able to closely share the development process with
anybody interested.
Instructions to access the cvs repository (access has been tested
successefully with cvs client/server version 1.9.28, which can be found at
www.cyclic.com):
$ cvs -d ':pserver:[EMAIL PROTECTED]:/home/nicb/projects/repositories' login
<you get requested a password: 'guest' is the password)
$ cvs co csound # using cvs -z6 co csound will compress communication
$ cvs logout
This will create a csound directory in your current directory, with
all the most up-to-date sources in it. You may run all the other read-only
cvs commands in it, comparing releases, reading logging history etc.
Since the repository holds the bare source (including the configuration
process), you will need autoconf to build the 'configure' script (autoconf
is a GNU-maintained package and can be found in any GNU mirror - 2.12 runs
fine with the provided scripts).
There is also a specific mailing list ([EMAIL PROTECTED])
dealing with the discussions of this branch of development and which
receives the automatic mailings from cvs when some new additions/changes
are performed to the repository. Instructions to subscribe to the mailing
list can be found at http://www.ilogic.com.au/csound.
Thanks are due to Vito Asta at Ax Digital Systems in Rome, Italy for giving
us the resources to run the cvs server.
The mailing list is a courtesy of Damien Miller ([EMAIL PROTECTED])
The usual binary and source packaging distributions continue to be available
from the Dave Phillips repository at ftp://mustec.bgsu.edu/pub/linux and
from the AIMI repository at ftp://musart.dist.unige.it/CSOUND. They will
sport a third release number/letter which will refer to the linux revision
addition to the canonical version.
If you are looking for a debian packaging for csound, you can find one
made by Guenter Geiger at ftp://iem.mhsg.ac.at/debian/source/csound_3.482...
------------------------------------------------------------------------------
