Re: [Pharo-dev] Probably Metacello sucks…

Hi, As i said earlier in the conversation, you have to unload the oswindow configuration first... Just execute this before loading the package: MCPackageLoader unloadPackage: (MCPackage named: 'ConfigurationOfOSWindow') Merwan On mar., 2015-07-07 at 17:13 +0200, Natalia Tymchuk wrote: >

Re: [Pharo-dev] Probably Metacello sucks…

Hi. I tried to load Woden into pharo 4 and 5 images using script: Gofer new smalltalkhubUser: 'ronsaldo’ project: 'Woden’; package: 'ConfigurationOfWoden’; load. (#ConfigurationOfWoden asClass project version: #jenkins) load And in both

Re: [Pharo-dev] Probably Metacello sucks…

But we need a working configuration for a Thales project so it has to work. Stef Le 25/6/15 20:59, Yuriy Tymchuk a écrit : Hi Stef. Yes, there is “jenkins” baseline, but after some time it stopped working. The problem is that JB cannot really maintain configuration of the projects developed

Re: [Pharo-dev] Probably Metacello sucks…

Hi Stef. Yes, there is “jenkins” baseline, but after some time it stopped working. The problem is that JB cannot really maintain configuration of the projects developed by other people, because he is not aware what has changed and needs significantly more time than the dev that work with it. U

Re: [Pharo-dev] Probably Metacello sucks…

Yuriy can you check with JB because he told me that he wrote a configuration for Wooden. Stef Le 12/6/15 13:48, Yuriy Tymchuk a écrit :Yuri Just a quick side note: my initial email was kind of a troll. Because when you ask for something about roassal and 3D, you get a reply about R

Re: [Pharo-dev] Probably Metacello sucks…

Esteban, Yeah, it can take time for the culture to change, but the tools do have to be in place and the early adopters have to beat those tools into shape ... we are in this phase at the moment I think... once the tools are in place, then the projects that are feeling the most pain will have

Re: [Pharo-dev] Probably Metacello sucks…

+1 > On Jun 12, 2015, at 9:36 AM, Peter Uhnák wrote: > > As a sidenote (and since Yuriy mentioned Roassal), we would like to address > the versioning (and release management) of roassal at ESUG (Camp Roassal) > since Roassal was being developed really fast and it was hard to keep up. > --

Re: [Pharo-dev] Probably Metacello sucks…

… and of course I agree 100% with you :) the real problem is how do we get there, and I’m thinking not just the tools, but the “cultural change”. Esteban > On 12 Jun 2015, at 19:41, Dale Henrichs > wrote: > > > > On 06/12/2015 01:24 AM, Esteban Lorenzano wrote: >> it was just an example of

Re: [Pharo-dev] Probably Metacello sucks…

On 06/12/2015 01:24 AM, Esteban Lorenzano wrote: it was just an example of why using #stable in project dependences is a bad idea :) you made #releaseN.N to fix precisely my point. but since this is a convention of Seaside and not a regular practice… who knows it? (not saying that is wrong, i

Re: [Pharo-dev] Probably Metacello sucks…

On Fri, Jun 12, 2015 at 1:48 PM, Yuriy Tymchuk wrote: > Just a quick side note: > > my initial email was kind of a troll. Because when you ask for > something about roassal and 3D, you get a reply about Roassal-Woden i.e. > Roassal3D is not supported anymore, you have to use Woden instead

Re: [Pharo-dev] Probably Metacello sucks…

Just a quick side note: my initial email was kind of a troll. Because when you ask for something about roassal and 3D, you get a reply about Roassal-Woden i.e. Roassal3D is not supported anymore, you have to use Woden instead. Now when you have to load Woden, you can’t so you have to u

Re: [Pharo-dev] Probably Metacello sucks…

> On 12 Jun 2015, at 10:40, Stephan Eggermont wrote: > > On 12-06-15 10:24, Esteban Lorenzano wrote: >> it was just an example of why using #stable in project dependences is a bad >> idea :) >> you made #releaseN.N to fix precisely my point. >> there should exist something like I say “3.*” > >

Re: [Pharo-dev] Probably Metacello sucks…

On 12-06-15 10:24, Esteban Lorenzano wrote: it was just an example of why using #stable in project dependences is a bad idea :) you made #releaseN.N to fix precisely my point. there should exist something like I say “3.*” #'release3' always refers to the latest stable 3.*.*.* I’m sorry for b

Re: [Pharo-dev] Probably Metacello sucks…

it was just an example of why using #stable in project dependences is a bad idea :) you made #releaseN.N to fix precisely my point. but since this is a convention of Seaside and not a regular practice… who knows it? (not saying that is wrong, is in fact very good, but there should exist somethi

Re: [Pharo-dev] Probably Metacello sucks…

On 12-06-15 09:34, Esteban Lorenzano wrote: Project A uses for instance Seaside stable which is, when Project A starts Seaside 3.0 time after owner tries to load Project A… but since then stable from Seaside has move from Seaside 3.0, to 3.1.2 Seaside is the one example where we are using seman

Re: [Pharo-dev] Probably Metacello sucks…

dependency management for projects is *never* an easy task. who think that the complex on loading project X or Y is because of metacello simply does not understand the inherent complexity the task it tries to solve has. things can be improved, yes… but no matter what tools we create, this will

Re: [Pharo-dev] Probably Metacello sucks…

Absence of Metacello won't help you dealing with dependencies and loading stuff by using hand-made scripts by dozens of people written at different points in time and not maintained by anyone. It may be too complicated to use, especially at earlier stages of development, and in situations, when al

Re: [Pharo-dev] Probably Metacello sucks…

On 11/06/15 07:52, Yuriy Tymchuk wrote: Once Stef mentioned that there is some project for dependency checking. What was it? Maybe we can use that? What I've done is get all latest versions out of smalltalkhub and collect the signatures that are used. That can provide upper and lower limits

Re: [Pharo-dev] Probably Metacello sucks…

Le 11 juin 2015 à 07:52, Yuriy Tymchuk a écrit : > Once Stef mentioned that there is some project for dependency checking. What > was it? Maybe we can use that? http://smalltalkhub.com/#!/~PharoExtras/Tool-DependencyAnalyser But take care, it only spots static dependencies (inheritance, refere

Re: [Pharo-dev] Probably Metacello sucks…

Once Stef mentioned that there is some project for dependency checking. What was it? Maybe we can use that? Uko > On 31 May 2015, at 19:42, Stephan Eggermont wrote: > > It is not going to get much easier than Metacello. > Referring to #stable should probably stop, at least for > configurations

Re: [Pharo-dev] Probably Metacello sucks…

It is not going to get much easier than Metacello. Referring to #stable should probably stop, at least for configurations that are being developed or use dependencies that are being developed. And we need better tool support for groups. Configuration Management is never going to be easy. The Wode

Re: [Pharo-dev] Probably Metacello sucks…

On 31/05/2015 13:34, Yuriy Tymchuk wrote: On 31 May 2015, at 13:29, stepharo > wrote: Hi, this is an observation on usage of Metacello. I guess that metacello is too complicated to be used. For example I was using the `jenkins` version of Woden configuration, bu

Re: [Pharo-dev] Probably Metacello sucks…

> On 31 May 2015, at 13:29, stepharo wrote: > > >> Hi, >> >> this is an observation on usage of Metacello. I guess that metacello is too >> complicated to be used. For example I was using the `jenkins` version of >> Woden configuration, but now it’s broken. > > How? >> And when you look at

Re: [Pharo-dev] Probably Metacello sucks…

Hi, this is an observation on usage of Metacello. I guess that metacello is too complicated to be used. For example I was using the `jenkins` version of Woden configuration, but now it’s broken. How? And when you look at the Woden repo[1] it says that the way to load it is: Gofer new smal

[Pharo-dev] Probably Metacello sucks…

Hi, this is an observation on usage of Metacello. I guess that metacello is too complicated to be used. For example I was using the `jenkins` version of Woden configuration, but now it’s broken. And when you look at the Woden repo[1] it says that the way to load it is: Gofer new smalltalkhubUs