Re: [linux-audio-dev] "pro" soundfile editors for linux

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [linux-audio-dev] "pro" soundfile editors for linux
From: Benno Senoner (sbenno_AT_gardena.net)
Date: ke helmi  09 2000 - 06:28:53 EST


On Tue, 08 Feb 2000, Paul Barton-Davis wrote:
> >Another problem is compile-time and inter-library compatibility
> >problems. Most problem-reports I receive are either g++ or
> >libstc++ related. And taking your Quasimodo as an example, I've
> >never been able to compile it. Same goes with aRts. And believe me,
>
> There is this general issue that we in the open source community face
> a lot these days: there are libraries out there that do things we
> want. They come in nice neat packages. They work. But if we use them,
> we have to tell both compile-oriented users *AND* people using
> non-statically linked binaries "you need this library". And that
> library. And the other library. And that one over there. Worse, when
> the libraries alter, we face the problem of either keeping up with
> them in our apps, or telling people "use an older version". In some
> cases, we have to tell them "use the new version". Its an ugly, ugly
> mess.
>

Paul, I think as application developers we should try to make things as easy as
possible for the people who what to try out an app.

Therefore my advice would be not only to supply a list of download links of
the libs needed for a program for working properly, but putting emphasis
on installing a packaged version of the lib (RPM, DEB etc).

Since the user/developer is only interested in the main app,
just let him install the rest of the components ie. ibsigc etc, as a rpm (or
deb) without being forced to manually compile and "make install" the lib,
 which sooner or later will make you box unmanageable, becuase of dozen (maybe
duplicate too) libraries and includes lying around in various directiories.

It's not easy I know, but since I switched from Slackware to Redhat,
I try to use rpm as much as possible,
with rpmfind you find almost all stuff in rpm form, when you want to get rid of
some lib or app you do not longer need,
a simple rpm -e name.rpm does the trick.
:-)

For work-in-progress software this is much more difficult to implement,
but at least we should try to ship the needed libs (which do not change that
often) in some packages format.

Benno.


New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:23:27 EST