Up until now many projects end up defining their own specialised package
types by defining their own subclass of PackageInfo.
The latest PackageInfo introduces the idea of Package types.
We have three new package types defined.
PackageInfoKernel
"MyPackage.kernel" will package only the methods and their classes that
have the
method pragma
<kernel>
PackageInfoTest
"MyPackage.test"
Packages categories within the main package that have the subcategory
'Tests'.
PackageInfoImpl
"MyPackage.impl"
Packages categories within the main package that do not have the
subcategory 'Tests'.
========
I am quite pleased with the way this scheme is working out.
1. It is simple.
2. It leaves current behaviour exactly as it is.
3. It enables code and tests to be categorized together in the browser
but packaged separately.
4. When applied to the kernel the category system is much tidier all
round. I think that it is beginning to look refined rather than kludgy.
Finally I would like to see if those who are routinely packaging code
for Gemstone VW or Dolphin would have a preferred scheme for their own
generic PackageInfo types...
i.e. PackageInfoVW, PackageInfoDolphin, PackageInfoGS
Keith
