puredyne-team team mailing list archive

[danstowell <danstowell+launch@xxxxxxxxx>]

(Correction to my above comment - the redf0 ugens are separate from
sc3-plugins, which is why they're packaged separately.)

I've written some deb packaging for the sc3-plugins (can't upload for a
few days yet). Trying to decide what granularity to go for. In the old
version, Karsten started with one simple package for the whole lot and
then later broke them out into many separate units. I am tempted to try
something imbetween, e.g. only divide into separate packages when the
dependencies are different (so the AY pack gets its own package cos of
the dependency on libayemu). It'd be nice to get a good clean
arrangement, cos then I'll send the packaging scripts upstream so
they're readily available for other debians - so, comments welcome.

** Changed in: broth
       Status: New => In Progress

-- 
Add supercollider-plugins (sc3-plugins)
https://bugs.launchpad.net/bugs/500751
You received this bug notification because you are a member of puredyne
team, which is the registrant for broth.

Status in broth - the mother of all soups: Invalid

Bug description:
The "sc3-plugins" plugin collection for SuperCollider is very widely used and contains lots of very useful plugins. I think Karsten may have some packaging scripts already for these, though it looks like he's only packaged the redf0 subset (any reason K?).

I made a half-working bundle in my own ppa based on old scripts by K, but they definitely need work before use.

So the question is, does K have packaging nearly usable for these or should I try and start on them?