Sorry about that Werner ... I had been getting my mail forwarded from
the Metacello Group to my work email and apparently a year ago, the mail
(silently) stopped being forwarded, so I was none the wiser until you
mentioned it just now ... and I've approved your membership request
along with several others that had queued up ...
It would be easier for me to understand what you are proposing with an
actual example of spec - the way that you'd like to see it...
Also I don't quite understand what you mean by "no git involved" are you
using a filetree:// repo or an mcz repository or what ... Metacello
knows about github:// repos but as far as Metacello is concerned a "git
repo" is just a filetree repo ...
Dale
On 2/16/16 10:04 AM, Werner Kassens wrote:
Hi Dale,
since you are reading this forum, may i ask you another qestion here
(btw i asked for access to the metacello forum, i dont know, a year
ago or so but didnt get it)? assumed i have a project (with a config)
in a baseline and several packages in that baseline with dependencies
on specific packages of this project. with that #import: method i
could model this dependencies of course, but i guess #import: is only
for git-baselines, or? if this is correct, is there a possibility to
model these dependencies without making a special project for each of
these? or simpler: project consists of packA & packB, my baseline
consists of project (only via its config) and packC & packD, packC
depends on packB, and packD depends on packA. now i want to load eg
packD via my baseline and this should of course load also packA but
not packB. (and no git involved.)
werner
