[Pharo-project] Version 1.39 of Versionner
Gofer new squeaksource3: 'Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) >project lastVersion load.
I get: Could not resolve: Metacello-ToolBox [Metacello-ToolBox-dkh.130] in C:\Pharo\Pharo2.0-one-click.app\Contents\Resources\package-cache http://ss3.gemstone.com/ss/Versionner Is it just me? Thx T.
No idea why happened. I copied the a missing file in the repository Try again, it should work now Alexandre On Apr 18, 2013, at 4:00 PM, Torsten Bergmann <astares@gmx.de> wrote:
Gofer new squeaksource3: 'Versionner'; package: 'ConfigurationOfVersionner'; load. (Smalltalk at: #ConfigurationOfVersionner) >project lastVersion load.
I get:
Could not resolve: Metacello-ToolBox [Metacello-ToolBox-dkh.130] in C:\Pharo\Pharo2.0-one-click.app\Contents\Resources\package-cache http://ss3.gemstone.com/ss/Versionner
Is it just me?
Thx T.
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
No idea why happened. I copied the a missing file in the repository Try again, it should work now
Alexandre
Works now - thanks. I've put a copy of the config into ss3/MetaRepoForPharo20 so one can easily load via Configuration browser from within the 2.0 image. Bye T.
No idea why happened. I copied the a missing file in the repository Try again, it should work now
Alexandre
Works now - thanks. I've put a copy of the config into ss3/MetaRepoForPharo20 so one can easily load via Configuration browser from within the 2.0 image.
Excellent! Something that would be amazing, is to have a small text panel that appears when you select a configuration, with a short description (or at least some keywords) of what the software about to install is all about. For example, there are only a few projects that I can imagine what they are about. For example, no idea what VistaCursors, VoyageMongo, ScriptManager are about. I know I can easily find the info on the different forges. But my point is that the visibility of these projects is really small. Maybe we can use as a convention a method #readme on each ConfigurationOf ? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Works now - thanks. I've put a copy of the config into ss3/MetaRepoForPharo20 so one can easily load via Configuration browser from within the 2.0 image.
Excellent! Something that would be amazing, is to have a small text panel that appears when you select a configuration, with a short description (or at least some keywords) of what the software about to install is all about.
For example, there are only a few projects that I can imagine what they are about. For example, no idea what VistaCursors, VoyageMongo, ScriptManager are about. I know I can easily find the info on the different forges. But my point is that the visibility of these projects is really small.
Maybe we can use as a convention a method #readme on each ConfigurationOf ?
Alexandre
I completely agree that more work is needed. I started a new config browser for 3.0 (based on Spec) as a changeset - currently I cant find the issue on this horrible new issue tracker ;) Yes - the config itself would be a good place. One problem: if you want to have a slick UI (fast moving in the list) you would have to load all the configs into the image. Or one needs an updating server job that collects all #readmes and provides a txt/xml file for the config browser client Bye T.
On Apr 19, 2013, at 5:25 PM, Torsten Bergmann <astares@gmx.de> wrote:
Works now - thanks. I've put a copy of the config into ss3/MetaRepoForPharo20 so one can easily load via Configuration browser from within the 2.0 image.
Excellent! Something that would be amazing, is to have a small text panel that appears when you select a configuration, with a short description (or at least some keywords) of what the software about to install is all about.
For example, there are only a few projects that I can imagine what they are about. For example, no idea what VistaCursors, VoyageMongo, ScriptManager are about. I know I can easily find the info on the different forges. But my point is that the visibility of these projects is really small.
Maybe we can use as a convention a method #readme on each ConfigurationOf ?
Alexandre
I completely agree that more work is needed. I started a new config browser for 3.0 (based on Spec) as a changeset - currently I cant find the issue on this horrible new issue tracker ;)
:) Yes me too :)
Yes - the config itself would be a good place.
One problem: if you want to have a slick UI (fast moving in the list) you would have to load all the configs into the image. Or one needs an updating server job that collects all #readmes and provides a txt/xml file for the config browser client
Yes :) Probably the job that will validate the projects that are accepted in a distribution should build this cache. In fact we want to have a job that loads the ConfigurationOf and parse their Pier description and generate a catalog on the web. Right now I'm continuing to write chapters for a future book in pier https://ci.inria.fr/pharo-contribution/job/PharoForTheEnterprise/ but this will be with the same techno Like that we will not have to maintain the catalog in the collaborative book. Stef
Bye T.
We should add more information in the configurationOf Stef
No idea why happened. I copied the a missing file in the repository Try again, it should work now
Alexandre
Works now - thanks. I've put a copy of the config into ss3/MetaRepoForPharo20 so one can easily load via Configuration browser from within the 2.0 image.
Excellent! Something that would be amazing, is to have a small text panel that appears when you select a configuration, with a short description (or at least some keywords) of what the software about to install is all about.
For example, there are only a few projects that I can imagine what they are about. For example, no idea what VistaCursors, VoyageMongo, ScriptManager are about. I know I can easily find the info on the different forges. But my point is that the visibility of these projects is really small.
Maybe we can use as a convention a method #readme on each ConfigurationOf ?
Alexandre
-- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
participants (3)
-
Alexandre Bergel -
stephane ducasse -
Torsten Bergmann