pd packages [was: [PD] PD usability - .debs]

[Fernando Pablo Lopez-Lezcano]

> > The pd-externals package still exists, it is a demudi only thing
> > (maybe planet ccrma has it too, I don know ..)
> 
> CCRMA only has zexy, Gem and ggee. 

+iemlib (curently pd and gem come from cvs)

> I had a discussion with Fernando
> regarding joining forces with the CVS. I'd like to see rpm-packages with
> similar names and contents as the Debs, and Fernando agreed with that. This
> is necessary for Demudi/Rehmudi anyway, isn't it?
> 
> Maybe we should try to convince Fernando to put his rpm-scripts into the
> souceforge CVS? Then one could build rpms from the CVS contents as
> easy as the Debs. 

I'm looking at the repository now. As far as I can tell there are debian
packaging instructions for pd-linux(ogg stuff? should be called ogg?),
pd-zexy, pd-flext and pd-osc (but I don't know much about the debian
build process). What about the others? I was starting to do a spec file
for the whole thing (spliting them to separate packages) and there are
several issues. One is versioning. I think it would be better to split
the collection into the component "subcollections" and maybe some of
them (I have not checked all) do not have versioning information...

> Btw regarding my externals and other externals depending on flext in
> general.  I've come to the conclusion, that they should build-depend on
> pd-flext, and not, as it is currently the case, look for flext in a
> repository's path.  So we could maybe package all flext-externals together
> into a package called pd-flexternals, but build them after pd-flext is
> installed? This could include Thomas single externals like idelay and
> xsample as well.

Is there a way for each external to state its dependencies? Or do
dependencies have to be compiled "by hand"? (sorry if this has an
obvious answer to pd gurus)

I would imagine it would be hard to create a version for a composite
package like the one suggested if all the externals are coming from
different sources. I guess all packages could have the cvs date as the
version, but that would make it impossible to track the evolution of
individual packages. I think I would prefer individual packages (with
proper dependencies, of course) so that you can mix and match stuff as
you need it. 

-- Fernando