[Pharo-project] Versionner in 2.0 again
Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner. Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever): I loaded Versionner from Metacello (taken from [1]) Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) perform: #load monticello issues ============= While updating the rest of the packages to the newest I saw that Versionner-Core-Model-ChristopheDemarey.19 has an older ancestor for fixing something for pharo 1.4. The package Versionner-Core-Model-ChristopheDemarey.20 merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier. So I'm using Versionner-Core-Model-ChristopheDemarey.18 and Versionner-Core-Commands-ChristopheDemarey.17 as older packages. Any other package is the newest in the repository. metacello toolbox issues ================== I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion. There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do. versionner issues ============= At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement. Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any) I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong. thanks, Norbert [1] http://users.dcc.uchile.cl/~jsandova/versionner/
Huh, I find it strange that nobody cares. Does anybody use Versionner? Norbert Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert@hartl.name>:
Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner.
Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever):
I loaded Versionner from Metacello (taken from [1])
Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) perform: #load
monticello issues =============
While updating the rest of the packages to the newest I saw that
Versionner-Core-Model-ChristopheDemarey.19
has an older ancestor for fixing something for pharo 1.4. The package
Versionner-Core-Model-ChristopheDemarey.20
merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier. So I'm using
Versionner-Core-Model-ChristopheDemarey.18 and Versionner-Core-Commands-ChristopheDemarey.17
as older packages. Any other package is the newest in the repository.
metacello toolbox issues ==================
I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion. There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do.
versionner issues =============
At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement. Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any)
I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong.
thanks,
Norbert
[1] http://users.dcc.uchile.cl/~jsandova/versionner/
<Metacello-ToolBox-NorbertHartl.136.mcz> <Versionner-Core-Commands-NorbertHartl.18.mcz> <Versionner-Core-Model-NorbertHartl.19.mcz>
Well, it for sure looks interesting. Once one has the understanding about configurations. Which will lead to look for something like that tool. Not sure I am mastering configuration basics at the moment... So, that's why I guess. Phil 2013/4/11 Norbert Hartl <norbert@hartl.name>
Huh, I find it strange that nobody cares. Does anybody use Versionner?
Norbert
Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert@hartl.name>:
Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner.
Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever):
I loaded Versionner from Metacello (taken from [1])
Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) perform: #load
monticello issues =============
While updating the rest of the packages to the newest I saw that
Versionner-Core-Model-ChristopheDemarey.19
has an older ancestor for fixing something for pharo 1.4. The package
Versionner-Core-Model-ChristopheDemarey.20
merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier. So I'm using
Versionner-Core-Model-ChristopheDemarey.18 and Versionner-Core-Commands-ChristopheDemarey.17
as older packages. Any other package is the newest in the repository.
metacello toolbox issues ==================
I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion. There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do.
versionner issues =============
At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement. Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any)
I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong.
thanks,
Norbert
[1] http://users.dcc.uchile.cl/~jsandova/versionner/
<Metacello-ToolBox-NorbertHartl.136.mcz> <Versionner-Core-Commands-NorbertHartl.18.mcz> <Versionner-Core-Model-NorbertHartl.19.mcz>
Yes, I use Versionner everyday. I do not commit without it actually. So far, I use Pharo 1.4 to do all my commit, sadly... Alexandre On Apr 11, 2013, at 7:32 AM, phil@highoctane.be wrote:
Well, it for sure looks interesting. Once one has the understanding about configurations. Which will lead to look for something like that tool.
Not sure I am mastering configuration basics at the moment... So, that's why I guess.
Phil
2013/4/11 Norbert Hartl <norbert@hartl.name> Huh, I find it strange that nobody cares. Does anybody use Versionner?
Norbert
Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert@hartl.name>:
Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner.
Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever):
I loaded Versionner from Metacello (taken from [1])
Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) perform: #load
monticello issues =============
While updating the rest of the packages to the newest I saw that
Versionner-Core-Model-ChristopheDemarey.19
has an older ancestor for fixing something for pharo 1.4. The package
Versionner-Core-Model-ChristopheDemarey.20
merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier. So I'm using
Versionner-Core-Model-ChristopheDemarey.18 and Versionner-Core-Commands-ChristopheDemarey.17
as older packages. Any other package is the newest in the repository.
metacello toolbox issues ==================
I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion. There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do.
versionner issues =============
At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement. Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any)
I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong.
thanks,
Norbert
[1] http://users.dcc.uchile.cl/~jsandova/versionner/
<Metacello-ToolBox-NorbertHartl.136.mcz> <Versionner-Core-Commands-NorbertHartl.18.mcz> <Versionner-Core-Model-NorbertHartl.19.mcz>
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I care... and a LOT :) But I was waiting for Christophe to say something :P Esteban On Apr 11, 2013, at 1:18 PM, Norbert Hartl <norbert@hartl.name> wrote:
Huh, I find it strange that nobody cares. Does anybody use Versionner?
Norbert
Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert@hartl.name>:
Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner.
Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever):
I loaded Versionner from Metacello (taken from [1])
Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) perform: #load
monticello issues =============
While updating the rest of the packages to the newest I saw that
Versionner-Core-Model-ChristopheDemarey.19
has an older ancestor for fixing something for pharo 1.4. The package
Versionner-Core-Model-ChristopheDemarey.20
merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier. So I'm using
Versionner-Core-Model-ChristopheDemarey.18 and Versionner-Core-Commands-ChristopheDemarey.17
as older packages. Any other package is the newest in the repository.
metacello toolbox issues ==================
I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion. There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do.
versionner issues =============
At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement. Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any)
I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong.
thanks,
Norbert
[1] http://users.dcc.uchile.cl/~jsandova/versionner/
<Metacello-ToolBox-NorbertHartl.136.mcz> <Versionner-Core-Commands-NorbertHartl.18.mcz> <Versionner-Core-Model-NorbertHartl.19.mcz>
We care a lot else we would not have christophe to work on it since september. the problem is that he was disrtacted by inria tasks. For us we cannot use versionner if does not handle project. stef On Apr 11, 2013, at 1:18 PM, Norbert Hartl <norbert@hartl.name> wrote:
Huh, I find it strange that nobody cares. Does anybody use Versionner?
Norbert
Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert@hartl.name>:
Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner.
Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever):
I loaded Versionner from Metacello (taken from [1])
Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) perform: #load
monticello issues =============
While updating the rest of the packages to the newest I saw that
Versionner-Core-Model-ChristopheDemarey.19
has an older ancestor for fixing something for pharo 1.4. The package
Versionner-Core-Model-ChristopheDemarey.20
merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier. So I'm using
Versionner-Core-Model-ChristopheDemarey.18 and Versionner-Core-Commands-ChristopheDemarey.17
as older packages. Any other package is the newest in the repository.
metacello toolbox issues ==================
I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion. There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do.
versionner issues =============
At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement. Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any)
I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong.
thanks,
Norbert
[1] http://users.dcc.uchile.cl/~jsandova/versionner/
<Metacello-ToolBox-NorbertHartl.136.mcz> <Versionner-Core-Commands-NorbertHartl.18.mcz> <Versionner-Core-Model-NorbertHartl.19.mcz>
Hi Norbert, Sorry, I don't read Pharo ML every day else I will never have time to work on Versionner... I only have a part time to do that. What I'm doing on Versionner is to add the possibility to update your configurations at a very fine grained (add/remove projects/packages/groups). This version is a WIP and not yet usable. I'm not so far to have one version open for beta-test but I now face issues with Metacello on Pharo2 and some missing API in the toolbox. That's why I'm now working to have Metacello tests green on Pharo2. What I'm doing: update builderCi (used by Dale to test Metacello on Travis) to support Pharo2/3 : almost done be able to load MetacelloPreview on Pharo2/3 have green tests. With a clean and up to date metacello environment for Pharo, I will be able to focus on Versionner and have a result soon. I also did not take time to port the "old" Versionner on Pharo2 since I will face the same issues with Metacello/Pharo2. The problem is not really Versionner itself but the fact that it relies on libraries not tested and not fully working on Pharo2. I will take a look at your work. (some comments below). Thanks for your contribution. Regards, Christophe. Le 11 avr. 2013 à 13:18, Norbert Hartl a écrit :
Huh, I find it strange that nobody cares. Does anybody use Versionner?
Norbert
Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert@hartl.name>:
Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner.
Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever):
I loaded Versionner from Metacello (taken from [1])
Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) perform: #load
monticello issues =============
While updating the rest of the packages to the newest I saw that
Versionner-Core-Model-ChristopheDemarey.19
has an older ancestor for fixing something for pharo 1.4. The package
Versionner-Core-Model-ChristopheDemarey.20
merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier.
I tried to switch at a time to Pharo2 but too many issues. So I switched back to Pharo1.4 to be able to work on Versionner.
So I'm using
Versionner-Core-Model-ChristopheDemarey.18 and Versionner-Core-Commands-ChristopheDemarey.17
as older packages. Any other package is the newest in the repository.
I will check that you don't have useless parts of the new Versionner. As it is difficult to maintain branches with Monticello, I moved new Versionner developments to Smalltalkhub.
metacello toolbox issues ==================
I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion.
ConfigurationOf and Baseline are introduced by newest version of Metacello that the one shipped with Pharo2.
There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do.
What is the version of Metacello and Metacello Toolbox you loaded?
versionner issues =============
At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement.
I also fixed that for the new version.
Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any)
I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong.
thanks,
Norbert
[1] http://users.dcc.uchile.cl/~jsandova/versionner/
<Metacello-ToolBox-NorbertHartl.136.mcz> <Versionner-Core-Commands-NorbertHartl.18.mcz> <Versionner-Core-Model-NorbertHartl.19.mcz>
Hi Norbert, I just add a look at your changes. In my opinion, all stuff related to ConfigurationBaseName shouldn't be changed. The root of the problem is the Metacello ToolBox version. I added a new configuration for Versionner (in ss3) for Pharo2. I tested it a bit and it looks fine. What you need : 1/ Load (don't merge) Metacello-ToolBox-dkh.130 from http://seaside.gemstone.com/ss/metacello in your Pharo2 image. 2/ Load ConfigurationOfVersionner from http://ss3.gemstone.com/ss/Versionner 3/ ConfigurationOfVersionner load Let me know if it solves your issues. Regards, Christophe. Le 11 avr. 2013 à 17:40, Christophe Demarey a écrit :
Hi Norbert,
Sorry, I don't read Pharo ML every day else I will never have time to work on Versionner... I only have a part time to do that. What I'm doing on Versionner is to add the possibility to update your configurations at a very fine grained (add/remove projects/packages/groups). This version is a WIP and not yet usable. I'm not so far to have one version open for beta-test but I now face issues with Metacello on Pharo2 and some missing API in the toolbox.
That's why I'm now working to have Metacello tests green on Pharo2. What I'm doing: update builderCi (used by Dale to test Metacello on Travis) to support Pharo2/3 : almost done be able to load MetacelloPreview on Pharo2/3 have green tests.
With a clean and up to date metacello environment for Pharo, I will be able to focus on Versionner and have a result soon.
I also did not take time to port the "old" Versionner on Pharo2 since I will face the same issues with Metacello/Pharo2. The problem is not really Versionner itself but the fact that it relies on libraries not tested and not fully working on Pharo2.
I will take a look at your work. (some comments below).
Thanks for your contribution.
Regards, Christophe.
Le 11 avr. 2013 à 13:18, Norbert Hartl a écrit :
Huh, I find it strange that nobody cares. Does anybody use Versionner?
Norbert
Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert@hartl.name>:
Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner.
Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever):
I loaded Versionner from Metacello (taken from [1])
Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) perform: #load
monticello issues =============
While updating the rest of the packages to the newest I saw that
Versionner-Core-Model-ChristopheDemarey.19
has an older ancestor for fixing something for pharo 1.4. The package
Versionner-Core-Model-ChristopheDemarey.20
merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier.
I tried to switch at a time to Pharo2 but too many issues. So I switched back to Pharo1.4 to be able to work on Versionner.
So I'm using
Versionner-Core-Model-ChristopheDemarey.18 and Versionner-Core-Commands-ChristopheDemarey.17
as older packages. Any other package is the newest in the repository.
I will check that you don't have useless parts of the new Versionner. As it is difficult to maintain branches with Monticello, I moved new Versionner developments to Smalltalkhub.
metacello toolbox issues ==================
I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion.
ConfigurationOf and Baseline are introduced by newest version of Metacello that the one shipped with Pharo2.
There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do.
What is the version of Metacello and Metacello Toolbox you loaded?
versionner issues =============
At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement.
I also fixed that for the new version.
Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any)
I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong.
thanks,
Norbert
[1] http://users.dcc.uchile.cl/~jsandova/versionner/
<Metacello-ToolBox-NorbertHartl.136.mcz> <Versionner-Core-Commands-NorbertHartl.18.mcz> <Versionner-Core-Model-NorbertHartl.19.mcz>
On Apr 15, 2013, at 4:30 PM, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:
Hi Norbert,
I just add a look at your changes. In my opinion, all stuff related to ConfigurationBaseName shouldn't be changed. The root of the problem is the Metacello ToolBox version. I added a new configuration for Versionner (in ss3) for Pharo2. I tested it a bit and it looks fine.
Thanks for your time. We should produce a bug fix for Pharo 20.
What you need : 1/ Load (don't merge) Metacello-ToolBox-dkh.130 from http://seaside.gemstone.com/ss/metacello in your Pharo2 image. 2/ Load ConfigurationOfVersionner from http://ss3.gemstone.com/ss/Versionner 3/ ConfigurationOfVersionner load
Let me know if it solves your issues.
Regards, Christophe.
Le 11 avr. 2013 à 17:40, Christophe Demarey a écrit :
Hi Norbert,
Sorry, I don't read Pharo ML every day else I will never have time to work on Versionner... I only have a part time to do that. What I'm doing on Versionner is to add the possibility to update your configurations at a very fine grained (add/remove projects/packages/groups). This version is a WIP and not yet usable. I'm not so far to have one version open for beta-test but I now face issues with Metacello on Pharo2 and some missing API in the toolbox.
That's why I'm now working to have Metacello tests green on Pharo2. What I'm doing: update builderCi (used by Dale to test Metacello on Travis) to support Pharo2/3 : almost done be able to load MetacelloPreview on Pharo2/3 have green tests.
With a clean and up to date metacello environment for Pharo, I will be able to focus on Versionner and have a result soon.
I also did not take time to port the "old" Versionner on Pharo2 since I will face the same issues with Metacello/Pharo2. The problem is not really Versionner itself but the fact that it relies on libraries not tested and not fully working on Pharo2.
I will take a look at your work. (some comments below).
Thanks for your contribution.
Regards, Christophe.
Le 11 avr. 2013 à 13:18, Norbert Hartl a écrit :
Huh, I find it strange that nobody cares. Does anybody use Versionner?
Norbert
Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert@hartl.name>:
Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner.
Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever):
I loaded Versionner from Metacello (taken from [1])
Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) perform: #load
monticello issues =============
While updating the rest of the packages to the newest I saw that
Versionner-Core-Model-ChristopheDemarey.19
has an older ancestor for fixing something for pharo 1.4. The package
Versionner-Core-Model-ChristopheDemarey.20
merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier.
I tried to switch at a time to Pharo2 but too many issues. So I switched back to Pharo1.4 to be able to work on Versionner.
So I'm using
Versionner-Core-Model-ChristopheDemarey.18 and Versionner-Core-Commands-ChristopheDemarey.17
as older packages. Any other package is the newest in the repository.
I will check that you don't have useless parts of the new Versionner. As it is difficult to maintain branches with Monticello, I moved new Versionner developments to Smalltalkhub.
metacello toolbox issues ==================
I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion.
ConfigurationOf and Baseline are introduced by newest version of Metacello that the one shipped with Pharo2.
There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do.
What is the version of Metacello and Metacello Toolbox you loaded?
versionner issues =============
At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement.
I also fixed that for the new version.
Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any)
I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong.
thanks,
Norbert
[1] http://users.dcc.uchile.cl/~jsandova/versionner/
<Metacello-ToolBox-NorbertHartl.136.mcz> <Versionner-Core-Commands-NorbertHartl.18.mcz> <Versionner-Core-Model-NorbertHartl.19.mcz>
stephane ducasse wrote
What you need : 1/ Load (don't merge) Metacello-ToolBox-dkh.130 from http://seaside.gemstone.com/ss/metacello in your Pharo2 image. 2/ Load ConfigurationOfVersionner from http://ss3.gemstone.com/ss/Versionner 3/ ConfigurationOfVersionner load
So is this the best way to load Versionner in 2.0? Can we streamline that i.e. put the preload in the config? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Versionner-in-2-0-again-tp4680376p4681681.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
Hi Sean, Le 15 avr. 2013 à 20:39, Sean P. DeNigris a écrit :
stephane ducasse wrote
What you need : 1/ Load (don't merge) Metacello-ToolBox-dkh.130 from http://seaside.gemstone.com/ss/metacello in your Pharo2 image. 2/ Load ConfigurationOfVersionner from http://ss3.gemstone.com/ss/Versionner 3/ ConfigurationOfVersionner load
So is this the best way to load Versionner in 2.0?
Yes. There might be some remaining issues but it is difficult to track without having metacello tests running on Pharo2.
Can we streamline that i.e. put the preload in the config?
I was wondering if it is possible to downgrade an already installed package in a configuration. Is it possible with a preload directive? Thanks, Christophe.
Christophe Demarey wrote
I was wondering if it is possible to downgrade an already installed package in a configuration.
For now, why don't we just declare a dependency to the correct version of the toolbox? I'm uploading a config to Nabble which does this and seems to work... ConfigurationOfVersionner-SeanDeNigris.101.mcz <http://forum.world.st/file/n4682230/ConfigurationOfVersionner-SeanDeNigris.1...> ----- Cheers, Sean -- View this message in context: http://forum.world.st/Versionner-in-2-0-again-tp4680376p4682230.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On Apr 18, 2013, at 5:16 AM, "Sean P. DeNigris" <sean@clipperadams.com> wrote:
Christophe Demarey wrote
I was wondering if it is possible to downgrade an already installed package in a configuration.
For now, why don't we just declare a dependency to the correct version of the toolbox? I'm uploading a config to Nabble which does this and seems to work... ConfigurationOfVersionner-SeanDeNigris.101.mcz <http://forum.world.st/file/n4682230/ConfigurationOfVersionner-SeanDeNigris.1...>
Lets just load it in 2.0 and 3.0, no need to have wrong version in the image. Marcus
Le 18 avr. 2013 à 05:16, Sean P. DeNigris a écrit :
Christophe Demarey wrote
I was wondering if it is possible to downgrade an already installed package in a configuration.
For now, why don't we just declare a dependency to the correct version of the toolbox? I'm uploading a config to Nabble which does this and seems to work... ConfigurationOfVersionner-SeanDeNigris.101.mcz <http://forum.world.st/file/n4682230/ConfigurationOfVersionner-SeanDeNigris.1...>
I tried with a baseline but it doesn't work (metacello keep the most up to date toolbox). I didn't think to declare the toolbox as package. Your version works fine. Thanks. I pushed it to the Versionner repo. :) So, now Versionner is loadable as any other lib. @Marcus: Yes, if possible, it should be nice to update the toolbox version in the image. Best regards, Christophe.
On Apr 18, 2013, at 2:34 PM, Christophe Demarey <Christophe.Demarey@inria.fr> wrote:
Le 18 avr. 2013 à 05:16, Sean P. DeNigris a écrit :
Christophe Demarey wrote
I was wondering if it is possible to downgrade an already installed package in a configuration.
For now, why don't we just declare a dependency to the correct version of the toolbox? I'm uploading a config to Nabble which does this and seems to work... ConfigurationOfVersionner-SeanDeNigris.101.mcz <http://forum.world.st/file/n4682230/ConfigurationOfVersionner-SeanDeNigris.1...>
I tried with a baseline but it doesn't work (metacello keep the most up to date toolbox). I didn't think to declare the toolbox as package. Your version works fine. Thanks. I pushed it to the Versionner repo. :) So, now Versionner is loadable as any other lib.
@Marcus: Yes, if possible, it should be nice to update the toolbox version in the image.
sure open a ticket and explain what we should do.
Best regards, Christophe.
Hi Christophe, looks pretty good to me. I did only quick tests. If I find anything I get back to you. Thanks for your effort. That was one missing piece for me to switch more projects to pharo 2.0 Norbert Am 15.04.2013 um 16:30 schrieb Christophe Demarey <Christophe.Demarey@inria.fr>:
Hi Norbert,
I just add a look at your changes. In my opinion, all stuff related to ConfigurationBaseName shouldn't be changed. The root of the problem is the Metacello ToolBox version. I added a new configuration for Versionner (in ss3) for Pharo2. I tested it a bit and it looks fine.
What you need : 1/ Load (don't merge) Metacello-ToolBox-dkh.130 from http://seaside.gemstone.com/ss/metacello in your Pharo2 image. 2/ Load ConfigurationOfVersionner from http://ss3.gemstone.com/ss/Versionner 3/ ConfigurationOfVersionner load
Let me know if it solves your issues.
Regards, Christophe.
Le 11 avr. 2013 à 17:40, Christophe Demarey a écrit :
Hi Norbert,
Sorry, I don't read Pharo ML every day else I will never have time to work on Versionner... I only have a part time to do that. What I'm doing on Versionner is to add the possibility to update your configurations at a very fine grained (add/remove projects/packages/groups). This version is a WIP and not yet usable. I'm not so far to have one version open for beta-test but I now face issues with Metacello on Pharo2 and some missing API in the toolbox.
That's why I'm now working to have Metacello tests green on Pharo2. What I'm doing: update builderCi (used by Dale to test Metacello on Travis) to support Pharo2/3 : almost done be able to load MetacelloPreview on Pharo2/3 have green tests.
With a clean and up to date metacello environment for Pharo, I will be able to focus on Versionner and have a result soon.
I also did not take time to port the "old" Versionner on Pharo2 since I will face the same issues with Metacello/Pharo2. The problem is not really Versionner itself but the fact that it relies on libraries not tested and not fully working on Pharo2.
I will take a look at your work. (some comments below).
Thanks for your contribution.
Regards, Christophe.
Le 11 avr. 2013 à 13:18, Norbert Hartl a écrit :
Huh, I find it strange that nobody cares. Does anybody use Versionner?
Norbert
Am 09.04.2013 um 11:31 schrieb Norbert Hartl <norbert@hartl.name>:
Yesterday I tried again to use Versionner in 2.0 but did have much success. So I tried myself (because I think Versionner is important) and could final generate a new version of my project using versionner.
Following things I noticed (I'm writing this because I'm not sure which issue to open for what package. I'm just want opinions and after that I can open/upload whatever):
I loaded Versionner from Metacello (taken from [1])
Gofer new url: 'http://ss3.gemstone.com/ss/Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) perform: #load
monticello issues =============
While updating the rest of the packages to the newest I saw that
Versionner-Core-Model-ChristopheDemarey.19
has an older ancestor for fixing something for pharo 1.4. The package
Versionner-Core-Model-ChristopheDemarey.20
merged the packages back to HEAD but reverted some things like SystemAnnouncer back to SystemChangeNotifier.
I tried to switch at a time to Pharo2 but too many issues. So I switched back to Pharo1.4 to be able to work on Versionner.
So I'm using
Versionner-Core-Model-ChristopheDemarey.18 and Versionner-Core-Commands-ChristopheDemarey.17
as older packages. Any other package is the newest in the repository.
I will check that you don't have useless parts of the new Versionner. As it is difficult to maintain branches with Monticello, I moved new Versionner developments to Smalltalkhub.
metacello toolbox issues ==================
I don't know much about metacello toolbox but the separation of files into ConfigurationOf and Baseline seems to have potential for confusion.
ConfigurationOf and Baseline are introduced by newest version of Metacello that the one shipped with Pharo2.
There is a notion of a basename so it can build ConfigurationOfMyProject as well as BaselineOfMyProject (MyProject being the basename). But in the MetacelloToolbox in the pharo2.0 repository it does not seem right. I had to change the code to use (MBToolbox baseNameOf: â¦) at a few places. I took orientation from the message signature. If a method expects a configurationBaseName and the sender used the configuration class I changed it. I'll attach the mcz for now to this mail until it is clear what to do.
What is the version of Metacello and Metacello Toolbox you loaded?
versionner issues =============
At one place I added a metacello toolbox name conversion because it made sense to make it there. The other thing I had to fix is a method notification that takes the wrong entity from an announcement.
I also fixed that for the new version.
Both packages attached as I don't have commit rights and don't know where the issue tracker for versionner is if there is any)
I would be glad if any of you guys that know about that stuff could drop me a note if this is ok or where I've gone wrong.
thanks,
Norbert
[1] http://users.dcc.uchile.cl/~jsandova/versionner/
<Metacello-ToolBox-NorbertHartl.136.mcz> <Versionner-Core-Commands-NorbertHartl.18.mcz> <Versionner-Core-Model-NorbertHartl.19.mcz>
participants (8)
-
Alexandre Bergel -
Christophe Demarey -
Esteban Lorenzano -
Marcus Denker -
Norbert Hartl -
phil＠highoctane.be -
Sean P. DeNigris -
stephane ducasse