> Thanks Lukas to be agree. I like your scripts, but the problem is that you > use your own forked repository to get an stable version. I would love to > have THAT, but in the original repositories. Examples: omnibrowser, > unsorted, etc. Do you know how we can fix this ?
Well, if you want to do a stable distribution you need to fork, even if you just copy the versions to a separate repository. We learned this with Seaside 3.0alpha1 the hard way. Servers disappear, repositories disappear, versions get deleted, versions get renamed or replaced. When we release a Seaside version we always copy all the dependencies to a single place that we control, e.g. <http://builder.seaside.st/distributions/004-Seaside3.0.0-a5/>. Forking is not something bad. Fork early and fork often. Forking is good. Monticello is excellent at merging. Lukas -- Lukas Renggli http://www.lukas-renggli.ch _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
