Subject: Re: [ecasound] embedding interface version numbers in library names
From: Michael Carmack (karmak_AT_karmak.org)
Date: Wed Apr 24 2002 - 19:21:36 EEST
On Wed, Apr 24, 2002 at 10:51:24AM -0400, S. Massy wrote:
> On Wed, 24 Apr 2002, Kai Vehmanen <k_AT_eca.cx> wrote:
> > ... ecawave, ecamegapedal and other apps using ecasound would link to
> > specific interface versions. When building rpms (and other binary
> > packages), separate rpms would be created for the libraries. This would
> > make it _much_ easier to install different versions of ecasound and
> > related tools.
> Not only do I agree with this scheme but I also suggest extending it to
> executables as well, just like with Debian.
> So when installing, say ecasound v2.1dev8, you'd have the libraries
> with their respective major versions appended to their names, but the
> executable installed would be called ecasound-2.1dev8. The
> /usr/local/bin/ecasound file would be a symlink to your favourite
> version of ecasound. That would be a great way to have several versions
> of ecasound live in simple harmony together.
If this is implemented, please make it optional. Appending version
numbers to binaries is a clumsy solution to a distribution-specific
problem. If you read the article I referenced in my other reply, you'll
see that there are much cleaner ways of solving this problem. Appending
version numbers to binaries by default, while at the same time abandoning
the creation of binaries with simple names, is (IMO) a step in the wrong
-- To unsubscribe send message 'unsubscribe' in the body of the message to <ecasound-list-request_AT_wakkanet.fi>.
This archive was generated by hypermail 2b28 : Wed Apr 24 2002 - 19:08:31 EEST