Subject: Re: [ecasound] development release: 2.2.0-rc1
From: Kai Vehmanen (k_AT_eca.cx)
Date: Sun Dec 01 2002 - 23:48:21 EET
On Sun, 1 Dec 2002, Junichi Uekawa wrote:
> I would like to have shared libraries back, if it is possible,
> because it would be benefitial in terms of disk space and
> version control.
But as there are only three apps that use libecasound left: ecasound,
ecamegapedal and ecawave, not much disk space would be saved. In the long
term, ecawave will be surpassed by new editors such as Sweep and Audacity
[1]. Ecamegapedal will probably continue to be developed as it's something
I use often myself :), but I'd like to either a) convert it to an ECI app,
or b) copy&paste enough code from libecasound to ecamegapedal so I can get
rid of the dependence between the two projects.
So in a away, libecasound is just a way to internally organize ecasound
source code, not a public interface.
And based on the stats at:
http://freshmeat.net/search/?q=ecasound§ion=projects
... ecasound is the only app of the three that is widely used. So I see
very little point in maintaining libecasound as a public library. If
nothing else, making libecasound separately available might encourage
developers to use it directly, which is specifically something I want to
discourage.
But I might have missed some important aspect, so feedback is welcome (and
especially now when 2.2.0 is just around the corner).
Btw; does this new arrangement somehow conflict with the debian
packaging guidelines?
[1] And, of course, there's always snd!
-- http://www.eca.cx Audio software for Linux!
This archive was generated by hypermail 2b28 : Sun Dec 01 2002 - 23:44:32 EET