On Sun, May 02, 2010 at 08:55:33AM -0700, Michael Rueger wrote:
On 5/1/10 11:31 AM, Bert Freudenberg wrote:
On 01.05.2010, at 18:31, David T. Lewis wrote:
Do you know if the rest of the stuff in http://source.impara.de/freetype/ still has value (or has it been superceded by Freetype Plus)?
I would think so, that's why there wasn't any further development on the freetype plugin. The current repositories are of somewhat historical value for e.g. the Sophie builds.
I have opened a new SqueakSource project for the Freetype plugin (FT2Plugin).
MCHttpRepository location: 'http://www.squeaksource.com/FreetypePlugin' user: '' password: ''
This contains copies of all the Freetype-Plugin entries from the archival repository at http://source.impara.de/freetype, as well as one additional update from Mantis 7521.
Project administrators are Andy Tween, Bert Freudenberg and me. Developers are everyone whose author initials appear in the original archive.
VMMaker class>>updateFromServer should now load FT2Plugin from the new FreetypePlugin repository. A similar update will be needed for ConfigurationOfVMMaker for Pharo.
For now the original package name Freetype-Plugin has been retained, although I note that this conflicts with the current packaging of Freetype in SqS/Freetype Plus, so a change to the package name may be in order.
FT2Plugin contains dependencies on Freetype. This is the reason that I moved it to a separate SqueakSource project rather than include it in the SqS/VMMaker repository.
Dave
On 09.05.2010, at 10:26, David T. Lewis wrote:
On Sun, May 02, 2010 at 08:55:33AM -0700, Michael Rueger wrote:
On 5/1/10 11:31 AM, Bert Freudenberg wrote:
On 01.05.2010, at 18:31, David T. Lewis wrote:
Do you know if the rest of the stuff in http://source.impara.de/freetype/ still has value (or has it been superceded by Freetype Plus)?
I would think so, that's why there wasn't any further development on the freetype plugin. The current repositories are of somewhat historical value for e.g. the Sophie builds.
I have opened a new SqueakSource project for the Freetype plugin (FT2Plugin).
MCHttpRepository location: 'http://www.squeaksource.com/FreetypePlugin' user: '' password: ''
This contains copies of all the Freetype-Plugin entries from the archival repository at http://source.impara.de/freetype, as well as one additional update from Mantis 7521.
Project administrators are Andy Tween, Bert Freudenberg and me. Developers are everyone whose author initials appear in the original archive.
VMMaker class>>updateFromServer should now load FT2Plugin from the new FreetypePlugin repository. A similar update will be needed for ConfigurationOfVMMaker for Pharo.
For now the original package name Freetype-Plugin has been retained, although I note that this conflicts with the current packaging of Freetype in SqS/Freetype Plus, so a change to the package name may be in order.
FT2Plugin contains dependencies on Freetype. This is the reason that I moved it to a separate SqueakSource project rather than include it in the SqS/VMMaker repository.
Dave
Thanks!
- Bert -
VMMaker class>>updateFromServer should now load FT2Plugin from the new FreetypePlugin repository. A similar update will be needed for ConfigurationOfVMMaker for Pharo.
Done (version 1.4). All Pharo-1.0 tests green with last squeakvm revision.
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/
On Mon, May 10, 2010 at 9:53 PM, laurent laffont laurent.laffont@gmail.comwrote:
VMMaker class>>updateFromServer should now load FT2Plugin from the new FreetypePlugin repository. A similar update will be needed for ConfigurationOfVMMaker for Pharo.
Done (version 1.4). All Pharo-1.0 tests green with last squeakvm revision.
Hi Laurent. Thank you very much for tacking care. Now I was thinking: the ONLY way to correclty be able to reproduce a VM version we need not only the VMMaker side but also SVN. If 6 months from today, I try to load version 1.4 with trunk, it won't work. I need to downloa an spceific SVN revision, as you write it in the commit comment. However, I was thinking that it would be great to put such information in the description: of Metacello. Not even the version (as the repo can change) but also the whole command. Not necesary while a verison is in #development but yes when it is realed. So, suppose I release 1.4 I can write:
version14: spec <version: '1.4' imports: #('1.4-baseline') >
spec for: #common do: [ spec blessing: #development. spec description: '- Changed repository of TrueType - etc..... Works with svn co http://squeakvm.org/svn/squeak/trunk/platforms/ -r 2203'. spec package: 'FFI-Pools' with: 'FFI-Pools-ar.1'; package: 'SharedPool-Speech' with: 'SharedPool-Speech-dtl.2'; package: 'VMMaker' with: 'VMMaker-dtl.170'; package: 'MemoryAccess' with: 'MemoryAccess-dtl.3'; package: 'SlangBrowser' with: 'SlangBrowser-dtl.3'; package: 'VMConstruction-Plugins-OSProcessPlugin' with: 'VMConstruction-Plugins-OSProcessPlugin-mtf.21'; package: 'VMConstruction-Plugins-AioPlugin' with: 'VMConstruction-Plugins-AioPlugin-dtl.9'; package: 'VMConstruction-Plugins-XDisplayControlPlugin' with: 'VMConstruction-Plugins-XDisplayControlPlugin-dtl.7'; package: 'Balloon3D-Constants' with: 'Balloon3D-Constants-ar.5'; package: 'Balloon3D-Plugins' with: 'Balloon3D-Plugins-bf.5';
package: 'Freetype-Plugin' with: 'Freetype-Plugin-dtl.56'; package: 'FreeType' with: 'FreeType-tween.435'. ].
spec for: #pharo do: [ spec blessing: #development. spec package: 'Alien-VMMaker-Support' with: 'Alien-VMMaker-Support-John M McIntosh.8'; package: 'Alien-VMMaker-Plugins' with: 'Alien-VMMaker-Plugins-John M McIntosh.8'; package: 'Sound' with: 'Sound-StephaneDucasse.47'. ]
Of course, this is just an example...
what do you think ? I hope this will increase traceability between Smalltalk code and svn.
Cheers
Mariano
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/
On Tue, May 11, 2010 at 1:06 AM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
On Mon, May 10, 2010 at 9:53 PM, laurent laffont < laurent.laffont@gmail.com> wrote:
VMMaker class>>updateFromServer should now load FT2Plugin from the new FreetypePlugin repository. A similar update will be needed for ConfigurationOfVMMaker for Pharo.
Done (version 1.4). All Pharo-1.0 tests green with last squeakvm revision.
Hi Laurent. Thank you very much for tacking care. Now I was thinking: the ONLY way to correclty be able to reproduce a VM version we need not only the VMMaker side but also SVN. If 6 months from today, I try to load version 1.4 with trunk, it won't work. I need to downloa an spceific SVN revision, as you write it in the commit comment. However, I was thinking that it would be great to put such information in the description: of Metacello. Not even the version (as the repo can change) but also the whole command. Not necesary while a verison is in #development but yes when it is realed. So, suppose I release 1.4 I can write:
version14: spec <version: '1.4' imports: #('1.4-baseline') >
spec for: #common do: [ spec blessing: #development. spec description: '- Changed repository of TrueType - etc..... Works with svn cohttp://squeakvm.org/svn/squeak/trunk/platforms/ -r 2203'. spec package: 'FFI-Pools' with: 'FFI-Pools-ar.1'; package: 'SharedPool-Speech' with: 'SharedPool-Speech-dtl.2'; package: 'VMMaker' with: 'VMMaker-dtl.170'; package: 'MemoryAccess' with: 'MemoryAccess-dtl.3'; package: 'SlangBrowser' with: 'SlangBrowser-dtl.3'; package: 'VMConstruction-Plugins-OSProcessPlugin' with: 'VMConstruction-Plugins-OSProcessPlugin-mtf.21'; package: 'VMConstruction-Plugins-AioPlugin' with: 'VMConstruction-Plugins-AioPlugin-dtl.9'; package: 'VMConstruction-Plugins-XDisplayControlPlugin' with: 'VMConstruction-Plugins-XDisplayControlPlugin-dtl.7'; package: 'Balloon3D-Constants' with: 'Balloon3D-Constants-ar.5'; package: 'Balloon3D-Plugins' with: 'Balloon3D-Plugins-bf.5';
package: 'Freetype-Plugin' with: 'Freetype-Plugin-dtl.56'; package: 'FreeType' with: 'FreeType-tween.435'. ]. spec for: #pharo do: [ spec blessing: #development. spec package: 'Alien-VMMaker-Support' with:'Alien-VMMaker-Support-John M McIntosh.8'; package: 'Alien-VMMaker-Plugins' with: 'Alien-VMMaker-Plugins-John M McIntosh.8'; package: 'Sound' with: 'Sound-StephaneDucasse.47'. ]
Of course, this is just an example...
what do you think ? I hope this will increase traceability between Smalltalk code and svn.
I think you're right. I will add this description.
Indeed, with easy_squeakvm script you have reproducibility (all is automated, explicit svn rev. and ConfigurationOfVMMaker).
May be we can "translate" easy_squeakvm to Smalltalk so we can have an EasySqueakVM package (or better name) which is cross platform.
Cheers,
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/
Cheers
Mariano
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/
I think you're right. I will add this description.
Indeed, with easy_squeakvm script you have reproducibility (all is automated, explicit svn rev. and ConfigurationOfVMMaker).
Yes, it is reproduceable. But it is the same, in the Conf version, I need the version of easy_squeakvm script as you will commit after.
easy_squeakvm is linux specific...so I would put the svn version, not easy_squeakvm script ;)
May be we can "translate" easy_squeakvm to Smalltalk so we can have an EasySqueakVM package (or better name) which is cross platform.
hahahah maybe ;)
Cheers,
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/
Cheers
Mariano
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/
On Tue, May 11, 2010 at 9:56 AM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
I think you're right. I will add this description.
Indeed, with easy_squeakvm script you have reproducibility (all is automated, explicit svn rev. and ConfigurationOfVMMaker).
Yes, it is reproduceable. But it is the same, in the Conf version, I need the version of easy_squeakvm script as you will commit after.
? 1 version of easy_squeakvm uses automatically the right squeakvm revision and the right version of ConfigurationOfVMMaker. So the reference is not ConfigurationOfVMMaker nor squeakvm sources, but easy_squeakvm itself.
easy_squeakvm is linux specific...so I would put the svn version, not easy_squeakvm script ;)
Yes it's true. But I think it's easily portable to MacOSX as it's a Unix system.
As there's some work on the Windows VM build to use CMake if I understand, with cygwin we can have it too.
And then we can automatically generate the One-Click archive from scratch ;p
I can tag easy_squeakvm 1.0 for Pharo 1.0, easy_squeakvm 1.1 for Pharo 1.1 and so on.
Laurent Laffont.
May be we can "translate" easy_squeakvm to Smalltalk so we can have an EasySqueakVM package (or better name) which is cross platform.
hahahah maybe ;)
Cheers,
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/
Cheers
Mariano
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/
On Tue, May 11, 2010 at 10:57 AM, laurent laffont <laurent.laffont@gmail.com
wrote:
On Tue, May 11, 2010 at 9:56 AM, Mariano Martinez Peck < marianopeck@gmail.com> wrote:
I think you're right. I will add this description.
Indeed, with easy_squeakvm script you have reproducibility (all is automated, explicit svn rev. and ConfigurationOfVMMaker).
Yes, it is reproduceable. But it is the same, in the Conf version, I need the version of easy_squeakvm script as you will commit after.
? 1 version of easy_squeakvm uses automatically the right squeakvm revision and the right version of ConfigurationOfVMMaker. So the reference is not ConfigurationOfVMMaker nor squeakvm sources, but easy_squeakvm itself.
There as a misunderstood. I know easy_squeakvm is completly reproducible. What I was saying is that someone that DOES NOT use easy_squeakvm should be reproducible too ;) Putting the SVN revision in the Metacello version helps with this.
easy_squeakvm is linux specific...so I would put the svn version, not easy_squeakvm script ;)
Yes it's true. But I think it's easily portable to MacOSX as it's a Unix system.
As there's some work on the Windows VM build to use CMake if I understand, with cygwin we can have it too.
And then we can automatically generate the One-Click archive from scratch ;p
sounds cool. If I have time I will try easy_squeakvm in my Mac...
I can tag easy_squeakvm 1.0 for Pharo 1.0, easy_squeakvm 1.1 for Pharo 1.1 and so on.
Laurent Laffont.
May be we can "translate" easy_squeakvm to Smalltalk so we can have an EasySqueakVM package (or better name) which is cross platform.
hahahah maybe ;)
Cheers,
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/
Cheers
Mariano
Laurent Laffont
http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/
On Tue, May 11, 2010 at 01:58:22PM +0200, Mariano Martinez Peck wrote:
There as a misunderstood. I know easy_squeakvm is completly reproducible. What I was saying is that someone that DOES NOT use easy_squeakvm should be reproducible too ;) Putting the SVN revision in the Metacello version helps with this.
Yes, I think this is a very good idea.
Dave
On Tue, May 11, 2010 at 2:03 PM, David T. Lewis lewis@mail.msen.com wrote:
On Tue, May 11, 2010 at 01:58:22PM +0200, Mariano Martinez Peck wrote:
There as a misunderstood. I know easy_squeakvm is completly reproducible. What I was saying is that someone that DOES NOT use easy_squeakvm should
be
reproducible too ;) Putting the SVN revision in the Metacello version helps with this.
Yes, I think this is a very good idea.
Dave
I've added descriptions in ConfigurationOfVMMaker versions 1.3 and 1.4. Tell me if it's what you expect.
version13: spec <version: '1.3' imports: #('1.3-baseline') >
spec for: #common do: [ spec blessing: #release.
spec description: 'Version needed to build 4.0.3.2202 Unix VM. - SqueakVM svn revision 2202. - Support FT2Plugin. - Tested with all plugins external except UUIDPlugin as internal'.
.....
version14: spec <version: '1.4' imports: #('1.4-baseline') >
spec for: #common do: [ spec blessing: #development.
spec description: '- Use SqueakVM svn revision 2203 at least. - Added Alien plugin (NewsqueakIA32ABIPlugin) - FT2Plugin now on SqueakSource. - do not fixFreeTypePluginForPharo anymore'.
...
Laurent
On Tue, May 11, 2010 at 10:12:38PM +0200, laurent laffont wrote:
On Tue, May 11, 2010 at 2:03 PM, David T. Lewis lewis@mail.msen.com wrote:
On Tue, May 11, 2010 at 01:58:22PM +0200, Mariano Martinez Peck wrote:
There as a misunderstood. I know easy_squeakvm is completly reproducible. What I was saying is that someone that DOES NOT use easy_squeakvm should
be
reproducible too ;) Putting the SVN revision in the Metacello version helps with this.
Yes, I think this is a very good idea.
Dave
I've added descriptions in ConfigurationOfVMMaker versions 1.3 and 1.4. Tell me if it's what you expect.
version13: spec <version: '1.3' imports: #('1.3-baseline') >
spec for: #common do: [ spec blessing: #release.
spec description: 'Version needed to build 4.0.3.2202 Unix VM.
- SqueakVM svn revision 2202.
- Support FT2Plugin.
- Tested with all plugins external except UUIDPlugin as internal'.
.....
version14: spec <version: '1.4' imports: #('1.4-baseline') >
spec for: #common do: [ spec blessing: #development.
spec description: '- Use SqueakVM svn revision 2203 at least.
- Added Alien plugin (NewsqueakIA32ABIPlugin)
- FT2Plugin now on SqueakSource.
- do not fixFreeTypePluginForPharo anymore'.
...
Hi Laurent,
These seem to be good descriptions. I'm not actually testing these, but I think that it is good to document the SVN version associated with a configuration of VMMaker, so thanks for doing this.
Dave
Thanks Laurent. For me is perfect ;)
On Tue, May 11, 2010 at 10:12 PM, laurent laffont <laurent.laffont@gmail.com
wrote:
On Tue, May 11, 2010 at 2:03 PM, David T. Lewis lewis@mail.msen.comwrote:
On Tue, May 11, 2010 at 01:58:22PM +0200, Mariano Martinez Peck wrote:
There as a misunderstood. I know easy_squeakvm is completly
reproducible.
What I was saying is that someone that DOES NOT use easy_squeakvm should
be
reproducible too ;) Putting the SVN revision in the Metacello version helps with this.
Yes, I think this is a very good idea.
Dave
I've added descriptions in ConfigurationOfVMMaker versions 1.3 and 1.4. Tell me if it's what you expect.
version13: spec <version: '1.3' imports: #('1.3-baseline') >
spec for: #common do: [ spec blessing: #release.
spec description: 'Version needed to build 4.0.3.2202 Unix VM.
- SqueakVM svn revision 2202.
- Support FT2Plugin.
- Tested with all plugins external except UUIDPlugin as internal'.
.....
version14: spec <version: '1.4' imports: #('1.4-baseline') >
spec for: #common do: [ spec blessing: #development.
spec description: '- Use SqueakVM svn revision 2203 at least.
- Added Alien plugin (NewsqueakIA32ABIPlugin)
- FT2Plugin now on SqueakSource.
- do not fixFreeTypePluginForPharo anymore'.
...
Laurent
On Mon, May 10, 2010 at 09:53:47PM +0200, laurent laffont wrote:
VMMaker class>>updateFromServer should now load FT2Plugin from the new FreetypePlugin repository. A similar update will be needed for ConfigurationOfVMMaker for Pharo.
Done (version 1.4). All Pharo-1.0 tests green with last squeakvm revision.
Laurent,
Thanks for doing the update!
Dave
vm-dev@lists.squeakfoundation.org
-
Bert Freudenberg -
David T. Lewis -
laurent laffont -
Mariano Martinez Peck