9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Steven Stallion <sstallion@gmail.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Mercurial and Plan 9
Date: Wed, 14 Mar 2012 08:17:17 -0700	[thread overview]
Message-ID: <CAGGHmKFiUeCWBqDkrWZzNEiyOSYrhL0=JmEg=oDv7p1z72vc5A@mail.gmail.com> (raw)
In-Reply-To: <8E336901-36C6-4A87-B957-AC839E0E7D02@corpus-callosum.com>

On Tue, Mar 13, 2012 at 11:28 PM, Jeff Sickel <jas@corpus-callosum.com> wrote:
> Do you see this as a potential GSoC effort?  The sans-ape version,
> build based off CPython 2.7 or 3.x?  There are more dependencies
> than just Python, but if we did have this updated then there would be
> more opportunity for people to experiment with a Plan 9 system.

I think a new port regardless of flavor would be much welcomed.
Something based on 2.7 would be great for Mercurial, but I know there
is a need elsewhere for a 3.x port. I have not looked into how much
would work it would take to mitigate the apishness of a new port but
it looks like others have (bummer). I suspect dropping openssl will be
tricky but it would be quite worthwhile especially given Mercurial's
penchant for https.

Cheers,

Steve



  reply	other threads:[~2012-03-14 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14  6:15 Steven Stallion
2012-03-14  6:28 ` Jeff Sickel
2012-03-14 15:17   ` Steven Stallion [this message]
2012-03-14 15:22     ` Yaroslav
2012-03-20 22:11       ` Federico Benavento
2013-01-04 21:56         ` Jeff Sickel
2013-01-04 23:10           ` Steven Stallion
2013-01-05  1:17             ` Charles Forsyth
2013-01-05  2:35             ` Federico G. Benavento
2013-01-07 15:13               ` Yaroslav
2012-03-14  9:19 ` Charles Forsyth
     [not found] <CAGGHmKHPkNw5Sf5YfO7TkLVYrZLmbK7jj0nmd2osByyF9sYC2Q@mail.gmail.c>
2012-03-14 12:58 ` erik quanstrom

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='CAGGHmKFiUeCWBqDkrWZzNEiyOSYrhL0=JmEg=oDv7p1z72vc5A@mail.gmail.com' \
    --to=sstallion@gmail.com \
    --cc=9fans@9fans.net \
    /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).