Tool to export Moose packages list to freeze a version
Locked
Tool to export Moose packages list to freeze a version
 
|
Today we created a tool with stephane:
I'm a kind of loader that know how to save and load list of packages. First when you have a configuration of packages that you want to version use: (Pay attention version and save first your packages, we are talking here about saving a list of packages not the packages themselves) publishNewVersion it will create a new method scriptXXX on the MooseConfigurationRepository You can then version this class in the package containing the Reloader class. In another image once you load this new version you can reload the configuration you save using the method reload: aNumber and it will load all the packages you previously specified. Under the cover, we need a way to know which packages to save and where to load them. Here is how this information is specified right now, it can be modified using accessors. defaultSavedPackagesPatternNames ^ #(#('Moose-Tests-Algos-InformationRetrieval*' 'http://www.squeaksource.com/MooseAlgos') #('Moose-Settings*' 'http://www.squeaksource.com/Moose') #('ConfigurationOfNewECompletion*' 'http://ss3.gemstone.com/ss/NEC') #('Fame-Example*' 'http://www.squeaksource.com/Fame') #('Moose-Tests-Algos-FormalConceptAnalysis*' 'http://www.squeaksource.com/MooseAlgos') #('CollectionExtensions*' 'http://www.squeaksource.com/CollectionExtensions') #('Grease-Core*' 'http://www.squeaksource.com/Seaside30') #('PetitSmalltalk*' 'http://source.lukas-renggli.ch/petit') #('Mondrian-Visitor*' 'http://www.squeaksource ......) Currently, it kills squeaksource but we will retry with a wait between each package and it should works. This tool is available at: http://www.smalltalkhub.com/mc/StephaneDucasse/MooseReloader/main -- Guillaume Larcheveque _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Tool to export Moose packages list to freeze a version
|
|
Hi guys
the idea is that while waiting to get better tools (christophe demarey started to work on a better versionner) to manage Moose configurations we did a simple system that should save a list of versioned packages so that people can perform snapshot when they want. We should probably iterate again on the code but we faced and fixed most of the problem. have a look and let us know Stef _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
|
|
In reply to this post by Guillaume Larcheveque
Is it something intented to be used with Metacello? When would I want to have this list of package and not a metacello version?
Just wondering. Alexandre On Aug 2, 2012, at 10:47 AM, Guillaume Larcheveque <[hidden email]> wrote: > Today we created a tool with stephane: > > I'm a kind of loader that know how to save and load list of packages. > > First when you have a configuration of packages that you want to version use: > (Pay attention version and save first your packages, we are talking here about saving a list of packages not the packages themselves) > > publishNewVersion > it will create a new method scriptXXX on the MooseConfigurationRepository > > You can then version this class in the package containing the Reloader class. > > In another image once you load this new version you can reload the configuration you save using the method > > reload: aNumber > and it will load all the packages you previously specified. > > Under the cover, we need a way to know which packages to save and where to load them. > Here is how this information is specified right now, it can be modified using accessors. > > defaultSavedPackagesPatternNames > ^ #(#('Moose-Tests-Algos-InformationRetrieval*' 'http://www.squeaksource.com/MooseAlgos') #('Moose-Settings*' 'http://www.squeaksource.com/Moose') #('ConfigurationOfNewECompletion*' 'http://ss3.gemstone.com/ss/NEC') #('Fame-Example*' 'http://www.squeaksource.com/Fame') #('Moose-Tests-Algos-FormalConceptAnalysis*' 'http://www.squeaksource.com/MooseAlgos') #('CollectionExtensions*' 'http://www.squeaksource.com/CollectionExtensions') #('Grease-Core*' 'http://www.squeaksource.com/Seaside30') #('PetitSmalltalk*' 'http://source.lukas-renggli.ch/petit') #('Mondrian-Visitor*' 'http://www.squeaksource ......) > > Currently, it kills squeaksource but we will retry with a wait between each package and it should works. > This tool is available at: http://www.smalltalkhub.com/mc/StephaneDucasse/MooseReloader/main > -- > Guillaume Larcheveque > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Tool to export Moose packages list to freeze a version
|
|
Added a delay to wait for squeaksource (2s between each package).
works now!! 2012/8/3 Alexandre Bergel <[hidden email]> Is it something intented to be used with Metacello? When would I want to have this list of package and not a metacello version? -- Guillaume Larcheveque _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Tool to export Moose packages list to freeze a version
|
|
In reply to this post by abergel
On Aug 3, 2012, at 12:15 AM, Alexandre Bergel wrote: > Is it something intented to be used with Metacello? Not at all. It is intended to be the safe belt to make sure that at least you can load the same packages than the image you used. Normally we should kill that once the Metacello of Moose is fixed and once we have the tools to manage Metacello configurations. Stef > When would I want to have this list of package and not a metacello version? > Just wondering. > > Alexandre > > > On Aug 2, 2012, at 10:47 AM, Guillaume Larcheveque <[hidden email]> wrote: > >> Today we created a tool with stephane: >> >> I'm a kind of loader that know how to save and load list of packages. >> >> First when you have a configuration of packages that you want to version use: >> (Pay attention version and save first your packages, we are talking here about saving a list of packages not the packages themselves) >> >> publishNewVersion >> it will create a new method scriptXXX on the MooseConfigurationRepository >> >> You can then version this class in the package containing the Reloader class. >> >> In another image once you load this new version you can reload the configuration you save using the method >> >> reload: aNumber >> and it will load all the packages you previously specified. >> >> Under the cover, we need a way to know which packages to save and where to load them. >> Here is how this information is specified right now, it can be modified using accessors. >> >> defaultSavedPackagesPatternNames >> ^ #(#('Moose-Tests-Algos-InformationRetrieval*' 'http://www.squeaksource.com/MooseAlgos') #('Moose-Settings*' 'http://www.squeaksource.com/Moose') #('ConfigurationOfNewECompletion*' 'http://ss3.gemstone.com/ss/NEC') #('Fame-Example*' 'http://www.squeaksource.com/Fame') #('Moose-Tests-Algos-FormalConceptAnalysis*' 'http://www.squeaksource.com/MooseAlgos') #('CollectionExtensions*' 'http://www.squeaksource.com/CollectionExtensions') #('Grease-Core*' 'http://www.squeaksource.com/Seaside30') #('PetitSmalltalk*' 'http://source.lukas-renggli.ch/petit') #('Mondrian-Visitor*' 'http://www.squeaksource ......) >> >> Currently, it kills squeaksource but we will retry with a wait between each package and it should works. >> This tool is available at: http://www.smalltalkhub.com/mc/StephaneDucasse/MooseReloader/main >> -- >> Guillaume Larcheveque >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Tool to export Moose packages list to freeze a version
|
|
In reply to this post by Guillaume Larcheveque
excellent! Thanks guillaume
We should also move the spec to the repository class and move the synectique class to another package. On Aug 3, 2012, at 11:59 AM, Guillaume Larcheveque wrote: > Added a delay to wait for squeaksource (2s between each package). > > works now!! > > 2012/8/3 Alexandre Bergel <[hidden email]> > Is it something intented to be used with Metacello? When would I want to have this list of package and not a metacello version? > Just wondering. > > Alexandre > > > On Aug 2, 2012, at 10:47 AM, Guillaume Larcheveque <[hidden email]> wrote: > > > Today we created a tool with stephane: > > > > I'm a kind of loader that know how to save and load list of packages. > > > > First when you have a configuration of packages that you want to version use: > > (Pay attention version and save first your packages, we are talking here about saving a list of packages not the packages themselves) > > > > publishNewVersion > > it will create a new method scriptXXX on the MooseConfigurationRepository > > > > You can then version this class in the package containing the Reloader class. > > > > In another image once you load this new version you can reload the configuration you save using the method > > > > reload: aNumber > > and it will load all the packages you previously specified. > > > > Under the cover, we need a way to know which packages to save and where to load them. > > Here is how this information is specified right now, it can be modified using accessors. > > > > defaultSavedPackagesPatternNames > > ^ #(#('Moose-Tests-Algos-InformationRetrieval*' 'http://www.squeaksource.com/MooseAlgos') #('Moose-Settings*' 'http://www.squeaksource.com/Moose') #('ConfigurationOfNewECompletion*' 'http://ss3.gemstone.com/ss/NEC') #('Fame-Example*' 'http://www.squeaksource.com/Fame') #('Moose-Tests-Algos-FormalConceptAnalysis*' 'http://www.squeaksource.com/MooseAlgos') #('CollectionExtensions*' 'http://www.squeaksource.com/CollectionExtensions') #('Grease-Core*' 'http://www.squeaksource.com/Seaside30') #('PetitSmalltalk*' 'http://source.lukas-renggli.ch/petit') #('Mondrian-Visitor*' 'http://www.squeaksource ......) > > > > Currently, it kills squeaksource but we will retry with a wait between each package and it should works. > > This tool is available at: http://www.smalltalkhub.com/mc/StephaneDucasse/MooseReloader/main > > -- > > Guillaume Larcheveque > > > > > > _______________________________________________ > > Moose-dev mailing list > > [hidden email] > > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > Guillaume Larcheveque > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Tool to export Moose packages list to freeze a version
|
|
In reply to this post by Guillaume Larcheveque
doru
did you get a look? because I thought that this is what you wanted to snapshot moose versions? Stef On Aug 2, 2012, at 4:47 PM, Guillaume Larcheveque wrote: > Today we created a tool with stephane: > > I'm a kind of loader that know how to save and load list of packages. > > First when you have a configuration of packages that you want to version use: > (Pay attention version and save first your packages, we are talking here about saving a list of packages not the packages themselves) > > publishNewVersion > it will create a new method scriptXXX on the MooseConfigurationRepository > > You can then version this class in the package containing the Reloader class. > > In another image once you load this new version you can reload the configuration you save using the method > > reload: aNumber > and it will load all the packages you previously specified. > > Under the cover, we need a way to know which packages to save and where to load them. > Here is how this information is specified right now, it can be modified using accessors. > > defaultSavedPackagesPatternNames > ^ #(#('Moose-Tests-Algos-InformationRetrieval*' 'http://www.squeaksource.com/MooseAlgos') #('Moose-Settings*' 'http://www.squeaksource.com/Moose') #('ConfigurationOfNewECompletion*' 'http://ss3.gemstone.com/ss/NEC') #('Fame-Example*' 'http://www.squeaksource.com/Fame') #('Moose-Tests-Algos-FormalConceptAnalysis*' 'http://www.squeaksource.com/MooseAlgos') #('CollectionExtensions*' 'http://www.squeaksource.com/CollectionExtensions') #('Grease-Core*' 'http://www.squeaksource.com/Seaside30') #('PetitSmalltalk*' 'http://source.lukas-renggli.ch/petit') #('Mondrian-Visitor*' 'http://www.squeaksource ......) > > Currently, it kills squeaksource but we will retry with a wait between each package and it should works. > This tool is available at: http://www.smalltalkhub.com/mc/StephaneDucasse/MooseReloader/main > -- > Guillaume Larcheveque > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Tool to export Moose packages list to freeze a version
|
|
Hi Stef,
Not yet. I was away :) Doru On Sat, Aug 11, 2012 at 11:19 AM, Stéphane Ducasse <[hidden email]> wrote: > doru > > did you get a look? > because I thought that this is what you wanted to snapshot moose versions? > > Stef > > On Aug 2, 2012, at 4:47 PM, Guillaume Larcheveque wrote: > >> Today we created a tool with stephane: >> >> I'm a kind of loader that know how to save and load list of packages. >> >> First when you have a configuration of packages that you want to version use: >> (Pay attention version and save first your packages, we are talking here about saving a list of packages not the packages themselves) >> >> publishNewVersion >> it will create a new method scriptXXX on the MooseConfigurationRepository >> >> You can then version this class in the package containing the Reloader class. >> >> In another image once you load this new version you can reload the configuration you save using the method >> >> reload: aNumber >> and it will load all the packages you previously specified. >> >> Under the cover, we need a way to know which packages to save and where to load them. >> Here is how this information is specified right now, it can be modified using accessors. >> >> defaultSavedPackagesPatternNames >> ^ #(#('Moose-Tests-Algos-InformationRetrieval*' 'http://www.squeaksource.com/MooseAlgos') #('Moose-Settings*' 'http://www.squeaksource.com/Moose') #('ConfigurationOfNewECompletion*' 'http://ss3.gemstone.com/ss/NEC') #('Fame-Example*' 'http://www.squeaksource.com/Fame') #('Moose-Tests-Algos-FormalConceptAnalysis*' 'http://www.squeaksource.com/MooseAlgos') #('CollectionExtensions*' 'http://www.squeaksource.com/CollectionExtensions') #('Grease-Core*' 'http://www.squeaksource.com/Seaside30') #('PetitSmalltalk*' 'http://source.lukas-renggli.ch/petit') #('Mondrian-Visitor*' 'http://www.squeaksource ......) >> >> Currently, it kills squeaksource but we will retry with a wait between each package and it should works. >> This tool is available at: http://www.smalltalkhub.com/mc/StephaneDucasse/MooseReloader/main >> -- >> Guillaume Larcheveque >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- www.tudorgirba.com "Every thing has its own flow" _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
Re: Tool to export Moose packages list to freeze a version
|
|
On Aug 13, 2012, at 9:49 AM, Tudor Girba wrote: > Hi Stef, > > Not yet. I was away :) I hope your holidays where as good as mine because mine were excellent. I should do a pass on the code and soon start to work on a configuration for moose but I'm waiting that Christophe makes progress on the new versionner. Stef > > Doru > > > On Sat, Aug 11, 2012 at 11:19 AM, Stéphane Ducasse > <[hidden email]> wrote: >> doru >> >> did you get a look? >> because I thought that this is what you wanted to snapshot moose versions? >> >> Stef >> >> On Aug 2, 2012, at 4:47 PM, Guillaume Larcheveque wrote: >> >>> Today we created a tool with stephane: >>> >>> I'm a kind of loader that know how to save and load list of packages. >>> >>> First when you have a configuration of packages that you want to version use: >>> (Pay attention version and save first your packages, we are talking here about saving a list of packages not the packages themselves) >>> >>> publishNewVersion >>> it will create a new method scriptXXX on the MooseConfigurationRepository >>> >>> You can then version this class in the package containing the Reloader class. >>> >>> In another image once you load this new version you can reload the configuration you save using the method >>> >>> reload: aNumber >>> and it will load all the packages you previously specified. >>> >>> Under the cover, we need a way to know which packages to save and where to load them. >>> Here is how this information is specified right now, it can be modified using accessors. >>> >>> defaultSavedPackagesPatternNames >>> ^ #(#('Moose-Tests-Algos-InformationRetrieval*' 'http://www.squeaksource.com/MooseAlgos') #('Moose-Settings*' 'http://www.squeaksource.com/Moose') #('ConfigurationOfNewECompletion*' 'http://ss3.gemstone.com/ss/NEC') #('Fame-Example*' 'http://www.squeaksource.com/Fame') #('Moose-Tests-Algos-FormalConceptAnalysis*' 'http://www.squeaksource.com/MooseAlgos') #('CollectionExtensions*' 'http://www.squeaksource.com/CollectionExtensions') #('Grease-Core*' 'http://www.squeaksource.com/Seaside30') #('PetitSmalltalk*' 'http://source.lukas-renggli.ch/petit') #('Mondrian-Visitor*' 'http://www.squeaksource ......) >>> >>> Currently, it kills squeaksource but we will retry with a wait between each package and it should works. >>> This tool is available at: http://www.smalltalkhub.com/mc/StephaneDucasse/MooseReloader/main >>> -- >>> Guillaume Larcheveque >>> >>> >>> _______________________________________________ >>> Moose-dev mailing list >>> [hidden email] >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> >> _______________________________________________ >> Moose-dev mailing list >> [hidden email] >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > > _______________________________________________ > Moose-dev mailing list > [hidden email] > https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list [hidden email] https://www.iam.unibe.ch/mailman/listinfo/moose-dev |
«
Return to Moose
|
1 view|%1 views
| Free forum by Nabble | Edit this page |