On Fri, Aug 30, 2013 at 10:38 AM, Norman Gray <nor...@astro.gla.ac.uk>wrote:
> > Greetings. > > On 2013 Aug 30, at 17:01, Konrad Hinsen <konrad.hin...@fastmail.net> > wrote: > > > One possible development could be that the de-facto standard for > > Racket packages becomes development on Github, with people installing > > from specific Github commits rather then going through any of the > > catalogs, for better version control. That may well be a good enough > > solution. > > I don't think that would necessarily be optimal, to the extent that it > would couple Racket packages to github. I've nothing against github (it's > the good thing about git), but... other version control systems do exist. > > Money where mouth is time: supposing that the next package I release will > be after the package manager system has become finalised, I will probably > feel obliged to offer patches to the package manager system, to support > retrieving packages from Mercurial/bitbucket. > > Would such patches be welcome, or is there in fact a > plan/expectation/resignation to couple Racket to github? > They would be very welcome. Github is especially convenient because of the API and ability to get zips for every commit/branch/tag. A lot of us use it, so it was natural to implement first. Jay > > All the best, > > Norman > > > -- > Norman Gray : http://nxg.me.uk > SUPA School of Physics and Astronomy, University of Glasgow, UK > > > ____________________ > Racket Users list: > http://lists.racket-lang.org/users > -- Jay McCarthy <j...@cs.byu.edu> Assistant Professor / Brigham Young University http://faculty.cs.byu.edu/~jay "The glory of God is Intelligence" - D&C 93
____________________ Racket Users list: http://lists.racket-lang.org/users
