Hello
I'd like to know: what is the autobuild server actually building every
night? What does pd-extended 0.42.5 actually consist of in terms of
SVN directories? I see /branches/pd-extended/0.42 in svn, but this
only contains pd source. Are the externals pulled from trunk?
I guess I can get every
> pd-extended could be assembled from parts as a
> meta package, there's no issue there.
I guess my point is that, if I download the pd-extended tarball, it is
not easy at all to assemble it as a series of parts, not as easy and
efficient as it could be. At the very least, I think there needs to b
So with a couple of perhaps narrow-minded rants out of the way, I
would like now to respond to dmotd.
>
> i guess i understand where you're coming from and
> in some ways i think you are right, however
> packaging debs is not as simple as it seems and
> with the sheer size of the externals repo wh
Sorry I lurk too much and forget I have to reply-to-all to mailing
lists on gmail. Looks like my message has been completely in
Anderson's response earlier.
>> I understand the motivation for pd-extended is to just fork to a
>> stable version. Is this the only reason? Why not just release stable,
As the Gentoo pd-overlay is a little moldy, I was planning on fixing some up
some of the ebuilds. I was a little bit confused by all the overlap in svn,
though. What's the difference between the trunk and the pd-devel branch?
pd-overlay also seemingly offers two choices: build pd-extended (with all
