On 10/22/16 7:03 AM, Dimitris Chloupis wrote:
Configurations in MetaRepo are supposed to be maintained and uploaded
by developers anyway. Its a public repo with no requirement for access
to write and read.
http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo60
<http://smalltalkhub.com/#%21/%7EPharo/MetaRepoForPharo60>
Unless your solution offers an advantage I cant see.
ConfigurationOfs are "obsolete" ... github projects use BaselineOf and
the BaselineOf is not portable. The BaselineOf is meant to be loaded
from the repository that it manages ...
The catalog browser uses the ConfigurationOf to get meta-data about the
project and then uses the ConfigurationOf to load the project and at the
moment for a github project to be listed in the catalog one must create
a ConfigurationOf whose sole purpose is to provide meta data to the catalog.
A MetacelloProjectLoadSpec would provide the portability that a
BaselineOf lacks, while providing the necessary meta data and
maintaining the loadability of a ConfigurationOf.
Finally, a MetacellProjectLoadSpec is useful for more than just the
Pharo catalog. The same object could be used to load projects in Squeak
and GemStone and as I have mentioned in the previous email could be a
component of local build scripts as well ..
So yes I think that there are additional advantages:)
Dale
On Sat, Oct 22, 2016 at 4:51 PM Dale Henrichs
<dale.henri...@gemtalksystems.com
<mailto:dale.henri...@gemtalksystems.com>> wrote:
On 10/22/16 3:09 AM, Esteban Lorenzano wrote:
On 22 Oct 2016, at 10:56, Dimitris Chloupis
<kilon.al...@gmail.com <mailto:kilon.al...@gmail.com>> wrote:
We need some easy to use gem-style installer on the command line.
we have it:
./pharo Pharo.image get Seaside3
will load seaside into your Pharo.image
this is catalog based, of course (there is no magic there, if you
want an easy way to install things, you need a centralised
repository).
Esteban
ps: there are a lot of perks like that people ignores… what we
actually need is a better documentation system :)
Esteban,
I really think that the catalog could benefit by a first class
objects like the TDProjectEntry and MetacelloProjectLoadSpec ...
these would be objects directly created and maintained by the
project developers themselves. The objects would be used for
custom build scripts, smalltalkCI builds, catalog loads, etc. ...
oh and if it was a Metacello class, it would be usable cross
platform (Squeak, Pharo, GemStone, etc.)
As a coincidence, I have been planning on talking on this subject
at the upcoming Smalltalks conference ... The working title for
the talk is "Dangerous Liaisons: Smalltalk, Files and Git" ...
Dale
