[Moose-dev] Re: Moose on pharo 2.0 -> moving it STHub

9 Feb 2013

...

 I wanted to say that we should only take the packages that are being used right now, and
not all the cruft that exists in the repositories. We can move the obsolete packages into
an obsolete repository in StHub. 
sure this is what we are doing.

...
  Furthermore, given that some repositories should be
split (like the Moose one), we have to take care how we do it. 
Indeed.

...
    - We double check that what we wanted to move was
actually moved  
 Indeed we have (and will) creating a version with exact version for all the configuration
for 1.4.
 Then we have (and will) created a new baseline to point to smalltalkhub.
 Then we will create a new baseline + version for 2.0.

 Now there are differences between the latest baseline and the default one and this is
annoying.   
 Yes, in the future, we should remove the default: and only rely on the #development
symbolic version. 
Ok we will then change the configuration to do that.

...
    Regarding PetitParser, please do not move it yet. This
is the project of Lukas, and first we have to ask him nicely about the plans he has with
it. Perhaps he does not want to have it somewhere else in which case we have to see how we
deal with having it working on the latest Pharo. In any case, the first step is to ask the
main author.  
 Sure! Ask lukas. 
 Now for projects we use for real we cannot rely on a server that may disappear tomorrow.

 We are building synectique and we will build a lot of parsers and infrastructure using
PetitParser, so we (as a community) 
 should have a way to store extensions and this should be in a logical place. There is not
even an inbox on petitParser source (or we do not find it)  
 If PetitParser, and Moose in general, is so important for you, it would be great to get
some feedback from time to time :). 
I think that you are again thinking that we are hidding changes that we may have done 
but anything that we do on moose is PUBLIC. for petit parser guillaume extended it and
send the code to lukas
but lukas preferred not to add it in the petit parser project.

...
   In addition
redoing and checking all the configurationof will take us a lot of energy 
 so we should control the places where the project are stored or that authors are reactive
because we may have to change some information.   
 Sure. Btw, this effort was performed, it's just that given that not many people
bothered, I ended up doing it. 
Yes I imagine well what it means. 

...
    Regarding Moose, I am not sure what you are
downloading, 
 Glamour  
 What is with Glamour? In the end, I understood that you will not move it, and that I
will. 
I do not know. We downloaded on the machine of usman but he probably thought that it would
be easier if you do it

what we want to do:
	- one versionned configuration for 1.4 on squeaksource
	- one baseline conifguration for 1.4 on squeaksource
	- then baseline/version for 2.0

it would be good that we all do the same.

...
  > but if you
just say Moose-Core and FAMIX, I am a bit skeptical.  
 This is what Usman wrote:
 "Moose (FAMIX + Moose-Core, downloading packages, will be committing next
week)"

 So, from this mail, I do not know what will be moved. 
we are starting by the leaves and we will move up.

...
    Please let's not deal with this hastily.  
 yes well. We should start one day and it was today.   
 I understand the urge.

 Cheers,
 Doru

   I will
start looking into this next week.

 Btw, we still did not release 4.7 :).  
 yes we know. Now if we want to give feedback to pharo 2.0 about problems and get a chance
to see them fixed we should move.  

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

[Moose-dev] Re: Moose on pharo 2.0 -> moving it STHub