Ned Konz wrote:
On Sunday 21 September 2003 11:50 pm, Mark A. Schwenk wrote:
Ned Konz wrote:
On Thursday 18 September 2003 06:10 pm, Mark A. Schwenk wrote:
In addition to these items, I'm wondering how to handle grouping of packages into larger entities, such as "all the packages I need for this application I'm building." I'm not sure if Monticello yet has this concept for a set of packages or set of versions of packages.
It's in some ways related to the loadscripts talked about in the SqueakMap context but loading from Monticello repositories.
I'm wondering, what is the Monticello equivalent for something like Envy Configuration Maps or Store Bundles?
It's a SAR with all the .mcv packages inside.
It appears that SARinstaller wants to laod MonticelloCVS to deal with the .mcz members, even though that package should not be required now.
Which SARInstaller version do you have? I recently posted a fix CS.
I was using the SqueakMap version for 3.6:
SARInstaller for 3.6 (18)
I thought that version would be the most up-to-date. I didn't have the fixes loaded. Is it because the package is part of the 3.6 image that you can't update the SqueakMap package to include the latest fixes?
If I let SARInstaller load MonticelloCVS, it eventually blows up because it does not seem to understand that the .mcz files are zip files.
What do you mean?
What blows up?
What .mcz files? I was referring to a SAR with .mcv files (SAR files can't currently handle .mcz files).
The current version of Monticello seems to write .mcz files, not .mcv files. What I meant was that SARInstaller, as you stated, doesn't properly handle .mcz files.
Thanks for your help! -Mark