> partitioning for development and partitioning for deployment. It's good 
> that we make that distinction, particularly at the beginning since we 
> now have lots of stuff that isn't separately deployable, but should be. 

Right.

> There's no need to preserve the class categories as they stand today...

Exactly. Let's get rid of class categories. However, it might be difficult to assure backward compatibility. This is on what I was working with the packages as first-class entities...

> Of course, that kind of partitioning may prove difficult, but it will 
> probably pay off in the end.

Whatever the strategy of partitioning, we should need tools to do it :-)
I am currently working on a new package browser that would perform this step easily...

Alexandre

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.