Le 11/09/2015 06:56, Damien Cassou a écrit :
Thierry Goubier <thierry.goub...@gmail.com> writes:
2015-09-09 16:29 GMT+02:00 Damien Cassou <damien.cas...@inria.fr>:
something else I forgot:
- what happens if a Metacello description loads a project hosted in git
but I still want to be able to hack on this dependency. So, this
dependency should not be read-only for me
Can you give an example?
For example, Cocoon is a framework to facilitate handling of user
configuration files. We created Cocoon by extracting code from Pillar
and Pillar is still the only user of Cocoon. This means we evolve Pillar
and Cocoon in parallel. The configuration of Pillar requires Cocoon. As
far as I understand, there are 2-ways to describe this dependency if
Cocoon is hosted on github:
1. Pillar depends on a read-only version of the Cocoon source code and
Metacello will download a zip archive from github. That's nice for all
users of Pillar but not for Pillar developers who would prefer a
read-write solution ;
2. Pillar depends on a read-write clone of the github repository. That's
nice for Pillar developers but not for Pillar users.
Easy:
stable version of pillar has github:// reference to Cocoon baseline.
Development version of pillar has gitfiletree:// reference to Cocoon
baseline.
Variant:
ConfigurationOfPillar in catalog browser has github:// reference to
Cocoon. Developpers of pillar write (Metacello baseline: 'pillar';
repository: 'gitfiletree://' ...) with a Pillar baseline referencing
gitfiletree for Cocoon.
Thierry
