I ran into a false dependency on the Development System when stripping
for deployment in 5.1.2 pro. The two packages that I was using that show
Development System as a prerequisite are 'Month View' and 'ActiveX
Control Hosting'.
In getting to the bottom of it, I found that the two indicated methods
in ActiveX Control Hosting are in the 'must strip' method category, and
so weren't actually causing any problems. However MonthView class >>
#publishedAspectsOfInstances is not in 'must strip'. It's in the
'development' method category, and so it itself does eventually get
stripped. But it's not stripped early enough in the process, and so
Development System gets left in as a result.
My workaround was to put it into 'must strip' (along with a few others
that I happened to notice):
(MethodCategory name: 'must strip') addMethod: MonthView class >>
#publishedAspectsOfInstances.
(MethodCategory name: 'must strip') addMethod: MaskedEdit class >>
#publishedAspectsOfInstances.
(MethodCategory name: 'must strip') addMethod: DBResultSet class >>
#publishedAspectsOfInstances.
(MethodCategory name: 'must strip') addMethod: DBAbstractRow >>
#publishedAspects.
At a minimum, I believe that these should be that way in the base image.
Even nicer might be if these were loose methods in separate packages the
way 'ActiveX Automation' and 'ActiveX Automation Development' are
handled. That way the dependency of the deployed package would never
appear in the Package Browser in the first place.
thanks,
-Bill
-------------------------------------------
Bill Dargel
[hidden email]
Shoshana Technologies
100 West Joy Road, Ann Arbor, MI 48105 USA
Locked
