A common plugin repository (WAS:Re: [LAD] ladspa qa?)
juuso.alasuutari at gmail.com
Wed Sep 5 11:31:55 UTC 2007
On Wednesday 05 September 2007 13:51:53 Steve Harris wrote:
> On 5 Sep 2007, at 10:52, Juuso Alasuutari wrote:
> > On Wednesday 05 September 2007 11:16:42 Georg Holzmann wrote:
> >> Hallo Juuso!
> >> I also was just thinking about something like this - at least for
> >> users
> >> this would be a great help (then its maybe also easier to categorize
> >> plugins into different sections).
> >> However, then one or a few maintainers for this codebase would be
> >> needed
> >> ...
> > In my optimistic vision, the authors of some respected existing plugin
> > collections would decide to join forces and set up a common
> > playground. But
> > things may not always work according to one's wishes -- especially
> > if he
> > isn't a plugin author himself...
> > Are there any such authors listening who could share their thoughts?
> I don't think it's a particularly great idea myself, it makes it
> harder for package maintainers to track plugins if they move from one
> package to another. If they stay in both then that's also tricky.
I assume you're imagining that the plugins would be copied to the common
repositories as-is; please correct me if I'm wrong.
In my mind this new codebase, although built upon existing code, would be like
any other new plugin collection with new, individual names and everything
else that goes with it. Many of the existing plugin collections would become
abandoned by necessity, as work would be focused towards a common project,
but none of the new plugins would conflict with the old ones. So package
managers (myself included) wouldn't really have to worry.
Some older plugin sets would of course become redundant as the new common
collection would initially introduce much of the same stuff in new clothes.
But I want to stress the word _initially_ here, because from there on the
efforts would be much better concentrated than before.
More information about the Linux-audio-dev