Creating parcels with version string - how?

Hi all,

I would like to create parcels from bundles which are already versioned
in Store. And I would like to do this in a way which includes the
version string in the parcel, but without having to publish the
(unchanged) bundle again. I don't want to assign a new version string
just because I am generating a parcel file. "Publish as parcel" creates
parcels without version information.

Is there a way to do this? Or do I have to publish the bundle in Store
and use the "Parcel options" of the publishing dialog at the same time
(and as a side-effect create new versions in Store which are exactly the
same as their parent version)?

Best regards,
Joachim Geidel

You can create a parcel from any pundle and save it to an arbitrary
location,

pundle
 saveAsParcel: (dir construct: label)
 saveStructure: false
 saveLinks: false
 parcelOptions: ((Dictionary new)
                   at: #parcelSaveSource put: false;
                   yourself)

Is this something you're looking for?

-Boris

--
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

[hidden email]

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: Joachim Geidel [mailto:[hidden email]]
> Sent: Thursday, March 15, 2007 2:06 PM
> To: vwnc-list
> Subject: Creating parcels with version string - how?
>
> Hi all,
>
> I would like to create parcels from bundles which are already
versioned
> in Store. And I would like to do this in a way which includes the
> version string in the parcel, but without having to publish the
> (unchanged) bundle again. I don't want to assign a new version string
> just because I am generating a parcel file. "Publish as parcel"
creates
> parcels without version information.
>
> Is there a way to do this? Or do I have to publish the bundle in Store
> and use the "Parcel options" of the publishing dialog at the same time
> (and as a side-effect create new versions in Store which are exactly
the
> same as their parent version)?
>
> Best regards,
> Joachim Geidel

I just found a way to add the version string:

- Load the parcel.
- Open a browser, switch to the parcel view, select the parcel.
- Select the "Properties" tool, go to "Other properties".
- Add a new field named "version" to the "Other properties" dictionary,
  and set the value to the version string.
- Save the parcel again.

But now, the parcel has a property "packageName" in addition to the
"bundleName". When I load it, the bundle structure is not restored, and
everything is loaded in a package with the same name as the original
bundle. That's of course not what I wanted.

Boris Popov schrieb am 15.03.2007 22:23:
Thanks for pointing to this method. It does not add the version string
of the pundle to the properties of the parcel, but I found a method
which can be overridden to add it. CodeComponent>>propertiesForSave
creates the Dictionary which is used as the properties for the parcel.
If it contains the key #version, the corresponding value will be written
to the header of the parcel file (CodeWriter>>storeHeader).

After adding the following method to PundleModel, the parcel had a
version string, and also recreated the bundle structure after load.

propertiesForSave
        | forSave |
        forSave := super propertiesForSave.
        forSave at: #version put: self traceVersionString.
        ^forSave

traceVersionString is not exactly what I wanted, as it has the form
        (version,username)
It's too late now on this side of the Atlantic, I'll look into
retrieving the version string tomorrow.

Best regards,
Joachim Geidel

Travis Griggs schrieb am 16.03.2007 02:19:
> You may take a look at StoreExtensions. It may not do exactly what you
> want, but is likely a good starting place, and maybe a good place to
> provide some increased functionality.
>
> It adds (amongst other things) a menu option called "Deploy (w/
> prerequisites)". This option will publish your package as a parcel. It
> does some things that may be nice for you:

...and I had this loaded all the time without ever using it. Sigh...

It's almost what I wanted in the first place (and more). I think I'll
just deploy the parcelized packages, and add an empty "Install" package
with lots of prerequisites as a replacement for the bundles. This won't
recreate the bundles, but if somebody wants the bundles, there is still
the Store repository to load from.

Thanks a lot!

Joachim

Hi Joachim,

I do it by adding an extension to PundleModel

        setVersionSilentlyTo: aString
                "set silently - dont notify anybody"
                properties at: #version put: aString

since the properties are not accessible directly otherwise.

My publishing code then looks like:

        publishAsParcelTo: aDirectory
                | basename options |
                basename := (aDirectory construct: self parcelOutName)
asString.
                options := Dictionary new.
                options at: #parcelSave put: true.
                options at: #databaseLinks put: false.
                options at: #bundleStructure put: false.
                options at: #parcelDirectory put: basename.
                options at: #parcelOverwrite put: true.
                options at: #parcelSaveSource put: self
publishWithSource.
                options at: #parcelPadded put: true.
                self codeComponent setVersionSilentlyTo: self
versionString.
                self codeComponent
                        saveAsParcel: basename asFilename
                        saveStructure: false
                        saveLinks: false
                        parcelOptions: options

(self is my class for Code, and self codeComponent is the PundleModel in
this case).

HTH,
        Christian