hgmerge.py in mainstream mercurial distribution

dhruva dhruvakm at gmail.com
Mon Dec 10 20:55:50 CST 2007

IMHO, having a dependency on cygwin for something that can easily be
done in python is not a very good idea. I would even prefer to have
'hgk' mplemented in PyTk so that we do not need TCL/Tk. If the
implementation is in a single language, it is easier to have a nice
framework approach and most importantly have more people hacking it
(and thereby using it). Mercurial having most of  it in python is the
main reason for me to select hg over git.

On 12/11/07, Patrick Mézard <pmezard at gmail.com> wrote:
> Jonathan S. Shapiro a écrit :
> > I don't have an opinion on the python merge script per se, but our
> > experience with teaching our clients how to use mercurial may be
> > relevant here.
> >
> > In brief: the less customization that needs to be done in order for a
> > mercurial install to "just work" -- even if it must do so with less than
> > optimal performance -- the better.
> >
> > For UNIX, we can mostly say to our clients "run this one command, then
> > you can use hg". For windows things are more complicated. There are
> > performance issues with cygwin,
> Cygwin ?
> > but more importantly it violates the
> > "too many steps" impediment. Ideally, we would like to be able to point
> > our Windows-based customers to a single installable "package" that will
> > either include all dependencies or resolve the dependency requirements
> > automatically (latter preferred).
> You probably already know about http://qct.sourceforge.net/Mercurial-BI.html
> and http://qct.sourceforge.net/Mercurial-NSI.html. What's wrong with them ?
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel

Sent from Gmail for mobile | mobile.google.com

Contents reflect my personal views only!

More information about the Mercurial-devel mailing list