It's on the original Moose job, just another archive called
moose-less.zip
The problem is not in Moose. It's even not in the tools, but
for now Pharo doesn't provide a good configuration mechanics. I
would prefer to be asked when I start the image for the first
time if I want to use the alternative theme or tools. And if I
don't, I'd prefer to stay with my own setup. We don't have this,
and Moose job configures the image for everyone (without asking
of course). That's I archive the image before the script is
being run, so I can download it and set it up for myself.
For example I use dark theme and apple fonts, but I can't
force others to use my configuration.
Uko
Sent from my iPhone
Where is your ci?
Because
Hi yuri
where is your ci?
Because moose is becoming bloated and I think that we should
rethink it.
Stef
The thing is that after loading all packages current
build job runs magical script that sets up theme, tools
and so on. Now moose-less image is archived before this
script is being run. So then I can set up the inspector
and so on by myself, while everything other remains like
in vanilla pharo.
Uko
_______________________________________________
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