On Fri, 20 Jun 2008, Hans-Christoph Steiner wrote:
So what should be the core mission of the pure-data repository? It looks like it is time to have that discussion again. I see it as a gathering of code and docs that are intended to be built using a common build system (aka Pd-extended build system).
The core mission of the repository is to be a repository, so that people can repose their code in it. All of the rest is bonus. Whether there are one or two or forty-twelve different build systems in the repository is not the question at all.
The core mission of the repository is what people do with it. If you want something to be part of the core mission, just do your stuff, but you're already doing that.
As for Pd-extended, I think it is a mistake (almost all my fault) including so many things in the package. It is now clear to me that makes more sense to have a distro that includes only the very stable libraries,
Then handle this at the level of your checkouts and/or branches. You don't need to meddle with mission-statements for that.
I guess this was a bit vague and wandering, but it seems that there is a discussion that needs to be had.
This is several discussions. It's a not a bit vague, it's a lot vague. The association of the repository's mission-statement with distro issues makes one wonder about how you think about it all. Do you want the trunk of the repo to be consisting of only the libraries that you like?
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801, Montréal, Québec