Sorry for the long delay in replying ... I have been in a cage
match with a GemStone 3.4 deadline for several months now and have
been keeping my head down:)
I think the standard procedure in this case is to manage the two
configurations independently:
copy mcz files from github to sthub and update ConfigurationOf
separately ...
The git and mcz file universe should never really cross streams ...
sharing copies of mcz packages makes sense, but tying a
ConfigurationOf to a BaselineOf adds too much complication ...
If you have forked the project, why are you concerned with the
ConfigurationOf at all ... for your purposes you can ignore it, I
assume...
Dale
On 6/3/17 7:04 PM, Sean DeNigris wrote:
I forked NeoCSV on GitHub. However, when I went to
load my fork into an image, I realized that it seemed to be a
straight package for package copy from an MCZ repo, and, as
such, had a Config and not a Baseline. How does one manage such
a project most effectively? Let's say I convert the Config into
a BaselineOf for GH; can I reuse/access that baseline logic in a
Config for the MCZ repo? Thanks!
--
You received this message because you are subscribed to the Google
Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
[hidden email].
For more options, visit
https://groups.google.com/d/optout.
Locked
