2015-09-11 16:05 GMT+02:00 stephan <stephan@stack.nl>:

On 11-09-15 15:52, Thierry Goubier wrote:

Hi Usman,

as far as I know, I see two things:

- Metacello and Monticello have no true concept of branch names in their
code; there is code where when you decode a package version name, you throw
away some of the name to keep only the package name, the version and the
author.

and:

- In your example, branch names are not written correctly: from filetree on
ss3 (http://ss3.gemstone.com/ss/FileTree/), what you see is that it should
be: PackageName.branch-author.version.mcz

So that means that they should preferably not be in a separate repository?

Due to the naming bug in MC and package cache, yes, they should be kept in the same repository (so that you can notice you are overwritting a stable good version with a newer one of the same name and crash everything for all users... otherwise the bug will appear under certain conditions in a user package cache ;) ).

Oh, yes, for fun. MC uses the branch when loading the package, to throw the branch name away inside Pharo; to makes it almost impossible to you to keep using the correct branch name when saving your developments on that branch :(

Thierry

Stephan

_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev