So if someone wants to use rubric in Pharo4, what version should he use?

Stephan

On 04-09-15 16:12, Usman Bhatti wrote:
On Fri, Sep 4, 2015 at 3:10 PM, Tudor Girba <tudor@tudorgirba.com> wrote:

Hi,

Just a note: please still prefix the versions with a Moose51 suffix
because we should not confuse them with the ones from the regular
repository.

I created the two versions:

ConfigurationOfGlamourCore>>version313Moose51: (new #stable)
ConfigurationOfRubric>>version1214Moose51:

they are loading correctly in the latest build and the bug is fixed.

regards.

Cheers,
Doru



On Fri, Sep 4, 2015 at 3:02 PM, Usman Bhatti <usman.bhatti@gmail.com>
wrote:


On Fri, Sep 4, 2015 at 2:41 PM, Andrei Chis <chisvasileandrei@gmail.com>
wrote:


On Fri, Sep 4, 2015 at 2:21 PM, Usman Bhatti <usman.bhatti@gmail.com>
wrote:


On Fri, Sep 4, 2015 at 12:41 PM, Tudor Girba <tudor@tudorgirba.com>
wrote:

As I mentioned when we released 5.1, we should create a separate repo
for committing code packages with fixes for 5.1. The configuration remains
in the same place and we will create a new version that will point to the
new packages.

@Usman: could you create the moose/moose51 repo?

MCHttpRepository
location: 'http://smalltalkhub.com/mc/Moose/Moose51/main'
user: ''
password: ''

@Andrei, can you commit the fix(es) in the repo? I see how to correct
the problem in Glamour renderer but I do not understand what checks you
would wish to introduce in Rubric for default theme colors.


I committed the two fixes.
Can you update the configurations?

Yes. I'm doing it now.


Cheers,
Andrei




              
Doru

--
www.tudorgirba.com

"Every thing has its own flow"

On 04 Sep 2015, at 12:34, Usman Bhatti <usman.bhatti@gmail.com> wrote:



On Fri, Sep 4, 2015 at 11:49 AM, stephan <stephan@stack.nl> wrote:


On 04-09-15 11:42, Usman Bhatti wrote:

A new version only will not solve the problem. The fix also needs to
be committed somewhere and if I commit the fix it in the main branch (see
screenshot below), I need to merge all the the changes done for Moose 6.0
(and update other packages that these packages depend on) and hence break
my tools in Moose 5.1.

Why? The only thing you are depending on is that #bleedingEdge
returns a version for Moose 6, isn't it?

No. We are using the stable version of Moose (release Moose 5.1) for
Pharo 4.0 and not the bleeding edge.


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

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


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


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


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


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



--
www.tudorgirba.com

"Every thing has its own flow"

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



      

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