On 5/13/17 6:26 AM, Stephane Ducasse wrote:
Hi dale
christophe developed something like that and this is based on cargo
metadata.
If it can be applied to arbitrary metacello projects, then it would fit
the bill ...
Dale
Stef
On Sat, May 13, 2017 at 3:04 PM, Dale Henrichs
<[email protected]
<mailto:[email protected]>> wrote:
Steph,
As Thierry mentions you should create an umbrella project for
Pharo where you can maintain a list of projects contributed by
users --- something like I've done for GsDevKit_home[1].
I strongly suggest that you use a "project load spec object"[2][3]
as the unit of registration for your projects. In addition to the
Metacello load instructions the "project load spec" can maintain a
bunch of meta data about the project.
The pharo image can scan the projects listed (similar to what you
do with the Category Browser - I think) or better yet, the
developer can make a local clone of the project site in a
well-known location and then all images can look up projects in
this the local clone and avoid having to hit the network to build
the project list ...
Take a look at the video or slides for my "Dangerous Liaisons:
Smalltalk, files, and git"[4] for more details ... and of course
I'm willing to discuss additional details/ideas over skype or email.
Dale
[1] http://gsdevkit.github.io/GsDevKit_home/
<http://gsdevkit.github.io/GsDevKit_home/>
[2]
https://github.com/GsDevKit/GsDevKit_home/blob/gh-pages/Seaside3.ston
<https://github.com/GsDevKit/GsDevKit_home/blob/gh-pages/Seaside3.ston>
[3]
https://github.com/dalehenrich/tode/blob/master/.smalltalk.ston
<https://github.com/dalehenrich/tode/blob/master/.smalltalk.ston>
[4]
http://fast.org.ar/talks/dangerous-liaisons-smalltalk-files-and-git
<http://fast.org.ar/talks/dangerous-liaisons-smalltalk-files-and-git>
On 5/13/17 12:01 AM, Stephane Ducasse wrote:
Hi guys
right now many people publish their software on SmalltalkHUB,
SS3 and Squeaksource
and this is handy to find something.
I hope that we will release soon the package repository that
christophe was developing but
now I'm wondering if we as a community should follow a pattern
to help?
git freaks do you have suggestions
Stef