2014-03-23 8:14 GMT+01:00 Johan Brichau jo...@inceptive.be:
I reflected a bit more on your requirements. How about the following?
Put a separate reference for the project in each platform-specific
section. I combine this with a #file: declaration because otherwise your
package cache will
Perhaps I was not really clear.
My argument was against different _versions_ of a ConfigurationOfXXX in
different (metacello-|catalog-)repositories. This will create a real mess
because you _will_ get identical package versions of the ConfigurationOfXXX
package in your package cache, leading
I reflected a bit more on your requirements. How about the following?
Put a separate reference for the project in each platform-specific section. I
combine this with a #file: declaration because otherwise your package cache
will play dirty tricks on you if it has a newer version of the
On 22 Mar 2014, at 23:06, Pharo4Stef pharo4s...@free.fr wrote:
Now others told me that in other community this is the inverse. People only
refer to the catalog.
Yes, that is perfect if there is one catalog for the community. Not a different
catalog per version of the platform (pharo2.x,
I have some packages A that depend on another package B.
In Metacello, I can easily declare the dependency
spec
className: 'ConfigurationOfB';
versionString: #'stable';
repository: 'http://www.squeaksource.com/MetacelloRepository' ].
But the repository
Why can you not reference the main repository? The meta repository is just a
place where the configuration loader tool fetches them.
Platform-specific elements go in the separate 'sections' of a baseline or
version method.
Don't make separate branches of the same ConfigurationOf class. You
OK, if the MetacelloRepository on squeaksource can still serve as
reference, I'm perfectly OK with it, I don't know why I had this impression
that anything beginning with those 6 letters was going to be seen as a
problem ;)
2014-03-22 18:53 GMT+01:00 Johan Brichau jo...@inceptive.be:
Why can
I don't understand what squeaksource has to do with that.
With main repository, I mean the repository of the project itself.
Almost all ConfigurationOfXXX are hosted together with the project itself. They
are also referenced in that repo. The MetacelloRepo or MetaRepos are almost
always
2014-03-22 21:27 GMT+01:00 Johan Brichau jo...@inceptive.be:
I don't understand what squeaksource has to do with that.
With main repository, I mean the repository of the project itself.
Almost all ConfigurationOfXXX are hosted together with the project itself.
They are also referenced in
I'm currently browsing the various ConfigurationOf in MetaRepoForPharo30
catalog hoping to find a pattern to serve as guidelines, but what I see is
a messy variety of solutions:
- direct reference to specific source repositories of package B as Johan
suggested (and the successive baselines are
We were discussing about that.
My point is that the system should work if the catalog fall apart.
Now others told me that in other community this is the inverse. People only
refer to the catalog.
Since we did not get last year and this year the engineer I requested to work
on the validation of
11 matches
Mail list logo
