Hi there, The dust after the 2.2 release has settled a bit, and I'd say it worked out pretty well. Thanks for your efforts in making that a (relatively) painless update. I've started two wiki pages to discuss the future development of CRUX itself and pkgutils, meant to serve as a outline for IRC meetings. Those pages are: http://crux.nu/Main/DevVision http://crux.nu/Main/PkgutilsIdeas I'd appreciate if anyone with write access would add his notes to those pages. Regarding DevVision: This page should serve to define a common vision and future goals of CRUX. Obviously, this is subject to frequent change, but I'd like to nail down some basic tasks and goals to make sure we're on the same page, and we're not wasting time implementing things the majority of devs doesn't want. In addition, this should allow people interested in certain subtasks to start working on it early on, seeing that we i.e. want something for the 2.3 release. Regarding PkgutilsIdeas: It's a rather longish document; if you're not that much interested, please jump directly to the "Summary" section. There's a section for personal comments and goals, and I'd be happy if those of you who have expressed an interest in pkgutils hacking (that would be at least sip, jdolan, tilman and vektori) to add their ideas there as well. Also related to this, I wrote a prototype (read: code not meant to be used in a final product but to demonstrate a concept) for attribute based pkgutils, including meta data in binary packages. There's an extra page for this at http://crux.nu/Main/PkgutilsAttributes, including a section on how to get the code and play with it. I'd suggest to have two separate IRC meetings (pkgutils first, the "vision" second) before the end of May; dates are subject to discussion. Comments both on the wiki pages and the rest of this mail are highly welcome. Kind regards, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch