Le 20/04/2018 à 11:44, Esteban Lorenzano a écrit :
On 20 Apr 2018, at 11:01, Thierry Goubier <thierry.goubier@gmail.com <mailto:thierry.goubier@gmail.com>> wrote:
Le 20/04/2018 à 09:09, Stephane Ducasse a écrit :
The underlying questions (sorry for people that need subtitles) are: - how do we have a central place to declare projects     - right now in Smalltalkhub/list is a nice way to find projects with the move to github     we should get a central place
One of the issues I have with the Catalog is that it made a mess of the various MetaRrepo for Pharo... Showing in the end that the single place one should put a ConfigurationOf for Pharo is the squeak meta repo.
not really. if you put your project in the squeak meta repo it will not even be listed (is old stuff and we are not listing those).
the idea was to add a project in its corresponding development repo. But is an uncomfortable way, yes (and it was a patch, not meant to last)
That in addition the Catalog doesn't even use the best package management we have at a given point is just salt rubbed in the wound.
thatâs a one method change. Instead:Â
loadConfiguration Gofer it url: self repositoryUrl; configurationOf: self name; load
loadConfiguration Metacello new repository: self repositoryUrl; configuration: self name; load.
when I made catalog, Metacello usage was not so expanded. Yet⦠gofer will use metacello to load so, yes, it will use the best package management we have at the moment.
Hi, Except if it changed recently, Gofer does not use Metacello behind. At Synectique when I tried to clean all our configurations because it was really hard to update them, I found some problems in the configurations but the projects were loading. The reasons was that we used Gofer and the bugs of gofer compensated the problems in the configurations. After switching to Metacello the projects did not load anymore and I needed to fix the configurations to make them clean. So, if it worked with Gofer but not Metacello, I doubt Gofer use Metacello.
very unlikely. a spec made in STON you just have to modify it each time you do a release (which is exactly what you have to do now with configurations).
A crawler will not handle the need to publish a released version.
one STON file as I imagine would be something like:Â
project { ânameâ : "blah", âurlâ : "http://github.com/someone/blah", âlastVersionâ : âv1.0.0", âdescriptionâ : âSome project description" }
and maybe a couple more. Howâs that cryptic? maybe you are confusing things?
-- Cyril Ferlicot https://ferlicot.fr