Hi people.
I want to publish Chalten and Aconcagua to the meta repo for 3.0. Could anybody do some magic or just add me as a contributor so I'd be able to upload these configurations.
Thanks in advance. Regards. Maxi |
and your user is… ?
Esteban On 19 Apr 2014, at 00:32, Maximiliano Taborda <[hidden email]> wrote: > Hi people. > I want to publish Chalten and Aconcagua to the meta repo for 3.0. > Could anybody do some magic or just add me as a contributor so I'd be able to upload these configurations. > > Thanks in advance. > > Regards. > Maxi |
Sorry, I forgot that. My username is maxi. 2014-04-19 5:05 GMT-03:00 Esteban Lorenzano <[hidden email]>: and your user is… ? |
done
On 19 Apr 2014, at 16:59, Maximiliano Taborda <[hidden email]> wrote:
|
thanks! 2014-04-20 7:53 GMT-03:00 Esteban Lorenzano <[hidden email]>:
|
Administrator
|
In reply to this post by Maximiliano Taborda
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 |
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 <[hidden email]>: Maximiliano Taborda wrote |
Administrator
|
Right now: - main repo has 3.1.1 and 3.1.4 - meta for 30 has 3.1.2 and 3.1.3 Neither did I at first, but I've found through painful exprience that people find projects through all different routes, and if they stumble upon the main repo and load an out-dated config, they may write the project off as unmaintained or reach out for support before finding out that they have to go to metarepofor30 to get the latest config. That would be welcome. I've wished for that at times, and didn't get around to implementing it...
Cheers,
Sean |
In reply to this post by Maximiliano Taborda
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:
|
Free forum by Nabble | Edit this page |