[Chicken-hackers] call for repository/chicken-setup organization plans

[felix winkelmann]

Hi!

I'm looking for proposals about how to find the ultimate repository/packaging
combination, or better: what could we do to keep a central, revision controlled
repository of chicken extensions, manage chicken+extension interdependencies,
keep users of historical chickens safe from featurecreep, etc. This influences
usage, development, installation, backups, maintenance and many other things,
so is really critical and should be well thought out.

It would be cool if, instead of "hey, this would be nice:..." or, "but
is must support
signing of packages!", we could gather somewhat more elaborate proposals
that try to specify details instead of just handwaving particular issues away.

I don't think any existing packaging system addresses our needs - we should find
something chicken-specific, to have maximal freedom to adapt it to the
particulars
of this implementation and community development style (-> chaos ;-).

Please help!


cheers,
felix