From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: <8E336901-36C6-4A87-B957-AC839E0E7D02@corpus-callosum.com> <71A1FC5E-E3DF-4E7E-BB8F-3B99DD2F59C6@gmail.com> Date: Fri, 4 Jan 2013 15:10:26 -0800 Message-ID: From: Steven Stallion To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=f46d041826c8b9bb1504d27e9543 Subject: Re: [9fans] Mercurial and Plan 9 Topicbox-Message-UUID: fe9c599e-ead7-11e9-9d60-3106f5b1d025 --f46d041826c8b9bb1504d27e9543 Content-Type: text/plain; charset=ISO-8859-1 Hi Jeff, Mercurial has been taken care of! I more or less track the latest stable (stallion/mercurial). The existing Python port is sufficient for Mercurial, though having a native Python port would be great. I've added Plan 9 support upstream in the Mercurial repository, so future builds are very simple. In fact, it's even documented: http://mercurial.selenic.com/wiki/Plan9FromBellLabs Cheers, Steve On Fri, Jan 4, 2013 at 1:56 PM, Jeff Sickel wrote: > Has anyone completed an APE lib sec yet? > > I'm starting to roll an ape build of libsec in as it's needed for > a new Python 2.7.3+ port of Python. I'd gladly take someone else's > mkfile rework to save some time. Libsec is needed to implement a > new _hashlib module, one that doesn't require OpenSSL among others. > > The new Python release&build will be pushed out once I clean up > a few more details like getting new builds of Mercurial working. > --f46d041826c8b9bb1504d27e9543 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Jeff,

Mercurial has been taken car= e of! I more or less track the latest stable (stallion/mercurial). The exis= ting Python port is sufficient for Mercurial, though having a native Python= port would be great. I've added Plan 9 support upstream in the Mercuri= al repository, so future builds are very simple. In fact, it's even doc= umented:=A0= http://mercurial.selenic.com/wiki/Plan9FromBellLabs

Cheers,

Steve
=
On Fri, Jan 4, 2013 at 1:56 PM, Jeff Sickel = <jas@corpus-callosum.com> wrote:
Has anyone completed an APE lib sec yet?<= br>
I'm starting to roll an ape build of libsec in as it's needed for a new Python 2.7.3+ port of Python. =A0I'd gladly take someone else'= ;s
mkfile rework to save some time. =A0Libsec is needed to implement a
new _hashlib module, one that doesn't require OpenSSL among others.

The new Python release&build will be pushed out once I clean up
a few more details like getting new builds of Mercurial working.

--f46d041826c8b9bb1504d27e9543--