Hi, Thanks. But, I meant to say that the packages should have a suffix. For example: Glamour-Morphic-Renderer-AndreiChis.324 should ideally be Glamour-Morphic-Renderer-Moose51-AndreiChis.324 Otherwise, we can also create a conflicting package with the one from the main repo of Glamour. For example, right now, we have in the Glamour repo: Glamour-Morphic-Renderer-SeanDeNigris.324 Luckily, in this case, the version was committed by Sean, but this could well have been committed by Andrei, and then we would have had a mess when using the local package cache (because we would have had 2 different implementations using the same file name). So, all versions committed in the Moose51 repo, should have a Moose51 suffix. Is that Ok? Could you republish the two packages with the Moose51 suffix? Cheers, Doru Cheers, Doru On Fri, Sep 4, 2015 at 4:12 PM, Usman Bhatti <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Hi, On Fri, Sep 4, 2015 at 5:49 PM, Tudor Girba <[hidden email]> wrote:
I see.
But I do not understand what problem can be caused by two packages having same names coming from two different repos?
Ok. I'll take care of that. regards.
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Hi,
On Mon, Sep 7, 2015 at 2:33 PM, Usman Bhatti <[hidden email]> wrote:
Imagine you have in the same folder a: moose51.image moose60.image package-cache/ In Moose 5.1 you load through Gofer PackageA.XYZ.70, and in Moose 6.0 you load also through Gofer a package with the same name but from a different repo. You will get problems in the Moose 6.0 image because the second time you load, it will be cached in package-cache.
Thanks! Doru
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
I've committed the packages with correct suffixes and updated configurations of Rubric and GlamourCore.
However, the packages are not loading because Roassal2 stable loads a different version of GlamourCore. So, we have: ConfigurationOfGlamour loading ConfigurationOfGlamourCore stable (3.1.3.Moose51) and ConfigurationOfRoassal2 loading ConfigurationOfGlamourCore 3.1.4. The first one should load the correct packages but the second one takes precedence and hence forces to load older versions of the packages. I'll have a look later. On Mon, Sep 7, 2015 at 3:39 PM, Tudor Girba <[hidden email]> wrote:
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
On 08-09-15 18:56, Usman Bhatti wrote: > I've committed the packages with correct suffixes and updated > configurations of Rubric and GlamourCore. > > However, the packages are not loading because Roassal2 stable loads a > different version of GlamourCore. > > So, we have: > > ConfigurationOfGlamour loading ConfigurationOfGlamourCore stable > (3.1.3.Moose51) > and > ConfigurationOfRoassal2 loading ConfigurationOfGlamourCore 3.1.4. > > The first one should load the correct packages but the second one takes > precedence and hence forces to load older versions of the packages. I'll > have a look later. of packages not under your control is wrong. Keeping configurations working becomes easier once we stop doing that. Stephan _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
In reply to this post by Usman Bhatti
On Tue, Sep 8, 2015 at 6:56 PM, Usman Bhatti <[hidden email]> wrote:
A wild guess: The correct packages were loaded before because GlamourCore loaded Rubric-AndreiChis.207 and when another configuration tried to load an older version (Rubric-AlainPlantec.206), it did not happen because that is just old version of the same package. With suffix added (Rubric-Moose51-usmanbhatti.207), Metacello might not consider the package to be the ancestor of Rubric-AlainPlantec.206 and hence it proceeds with loading the package thus overwriting fixes with an old version. In the past, I used loadDirective to debug package resolution mechanism in Metacello thru this command to see the actual list of packages loading: (ConfigurationOfGlamour project version: #stable) record loadDirective But I didn't work now (I do not get any package names actually loaded). Is there something changed recently in Metacello?
_______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Free forum by Nabble | Edit this page |