Subject: [ecasound] about ecasound version numbers (fwd)
From: Kai Vehmanen (firstname.lastname@example.org)
Date: Wed Oct 04 2000 - 19:00:08 EEST
This might be useful info for some of you:
---------- Forwarded message ----------
OK, I guess I can be of help here. :) I maintain three ecasound packages
1) ecasound (includes libkvutils, libecasound, the console mode ecasound
user-interface and collection of tools in the ecatools
2) qtecasound (includes libqtecasound and qtecasound;
depends on libecasound and libkvutils)
3) ecawave (no libraries, only ecawave; depends on libqtecasound,
libecasound and libkvutils)
These packages have distinct version numbers (all releases are
marked either with 'd' (development) or 'r' (stable release).
In addition to these, libtool versioning is used for all libraries.
Library interfaces (if changed) are frozen when a stable version is
released. For instance, when I release a new ecasound stable release,
libecasound and libkvutils libtool interface numbers are frozen. I try to
be careful with source and binary level issues. In top-level directories
of all libraries, there is a library-specific "ChangeLog" file, which
documents all changes (to the public interfaces).
-- . http://www.eca.cx ... [ audio software for linux ] /\ . . http://www.eca.cx/aivastus ... [ aivastus net radio ] /\ . . http://www.eca.cx/sculpscape [ my armchair-tunes mp3/ra/wav ]
-- To unsubscribe send message 'unsubscribe' in the body of the message to <email@example.com>.
This archive was generated by hypermail 2b28 : Wed Oct 04 2000 - 20:11:48 EEST