From: Jeff Sickel <jas@corpus-callosum.com>
To: nix-dev@googlegroups.com
Cc: 9fans@9fans.net
Subject: Re: [9fans] current python & hg support
Date: Fri, 10 Feb 2012 10:29:40 -0600 [thread overview]
Message-ID: <1898D5B4-7CFA-4289-B099-19406B182028@corpus-callosum.com> (raw)
In-Reply-To: <dc1007c9a8dbcd3cb6b642e9fc2438a0@chula.quanstro.net>
On Feb 10, 2012, at 12:43 AM, erik quanstrom wrote:
> On Thu Feb 9 21:07:08 EST 2012, jas@corpus-callosum.com wrote:
>> A quick question for everyone, is there interest in getting a more
>> current version of hg working for Plan 9 & NIX? If so, given I've
>> spent way too much time in the past getting both working for other
>> platforms, I could devote a little time to get both prepped for future
>> work.
>>
>> Python 2.5.1 is stable, but it wouldn't hurt us to be a little closer
>> to the 2.7.1 release. Hg has made significant strides since 1.0.2.
>
> stallion/hg is what we're using. it's version 1.7.5. we're using it with
> bichued/python.
>
> as i see it, the slight staleness of the port is tertiary. the primary
> problem is that python modules tend to assume they're on linux,
> and the secondary problem is that the python port is not as complete
> as it could be.
>
> it would also be nice for a python port to not depend on
> openssl, bz2 or z.
You've got a few dependencies for mercurial:
bz2, zlib, & ssl
So w/o those included in the Python build, no mercurial.
Getting current will help making the transition to modules that support
the Plan 9 file systems and architecture a little more robust.
Mercurial's a good example as it's got a lot of logic in place to
deal with all sorts of odd filesystems already.
-jas
next prev parent reply other threads:[~2012-02-10 16:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 2:06 Jeff Sickel
2012-02-10 3:33 ` Anthony Sorace
2012-02-10 5:03 ` John Floren
2012-02-10 5:55 ` Jens Staal
2012-02-10 6:43 ` erik quanstrom
2012-02-10 16:29 ` Jeff Sickel [this message]
2012-02-10 16:44 ` erik quanstrom
2012-02-10 17:03 ` John Floren
2012-02-10 17:50 ` Jeff Sickel
2012-02-11 11:43 ` Aram Hăvărneanu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1898D5B4-7CFA-4289-B099-19406B182028@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.net \
--cc=nix-dev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).