Copying is nice because people can load when they get to your repo.
I systematically copy configuration.
On 19/5/14 21:16, Maximiliano Taborda wrote:
Ready. You got it now.
I decided to not update the config from the aconcagua repo, and
maintain up to date only the one in the meta repo, because I can´t
find a way to publish the same config version to more than one repo
and I don't see the point of "copy" the same package in more than one
repo.
If it doesn't exist the option, is a craziness thinking in publish to
more than one repo the same config just in one action?
Regards.
Maxi.
2014-05-19 15:06 GMT-03:00 Sean P. DeNigris <[email protected]
<mailto:[email protected]>>:
Maximiliano Taborda wrote
> I want to publish Chalten and Aconcagua to the meta repo for 3.0.
If it's safe, will you copy the config to
http://smalltalkhub.com/mc/maxi/Aconcagua/main/ (there is an outdated
version there now)? I'd like to depend on it in my project without
involving
meta repo for 3.0. In general I've found it's always a good idea
to keep
copies of configs with the main project because you never know how
users
will find you! Thanks :)
-----
Cheers,
Sean
--
View this message in context:
http://forum.world.st/Grant-for-MetaRepoForPharo30-tp4755362p4759574.html
Sent from the Pharo Smalltalk Developers mailing list archive at
Nabble.com.
