BTW, I said "repositories", roughly like they are used in Debian, for
convenience of quick braindump, but this conflates several distinct
concepts you might wish to have.
For example, you might want to have "authorities" (like "racket-core",
individual roles of person/organization authors of contrib packages,
one's own organization, etc.) that are the basis for identifying and
authenticating packages, and then "repositories" are simply untrusted
copies of packages in any of a number of places that bits may be
represented. Then, in this particular example, you have to make this
setup, which I think implies some kind of signing, noncumbersome for
programmers wishing to use or share packages.
I do not envy the person who undertakes some of the design problems
involved in extending PLaneT to even greater heights. :)
--
http://www.neilvandyke.org/
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
