9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Mistake in Plan9 Mercual port?
Date: Sun,  1 Jun 2014 10:34:52 -0500	[thread overview]
Message-ID: <A7247DE9-924F-49E4-BD75-28FC0E42EA49@corpus-callosum.com> (raw)
In-Reply-To: <CAGNd-2P+dMBtc2f4qGFgScuhNNYxa_aKrJhHjyuH66dJtWQL1A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]


On Jun 1, 2014, at 9:46 AM, Pavel Klinkovský <pavel.klinkovsky@gmail.com> wrote:

> https://bitbucket.org/jas/cpython
> 
> you can pull hg directly from the mainline.
> 
> Well, I am a little bit confused...
> 
> 1. Is is a new 'python' interpretter implementation? What is a difference from 'bichued/python’?

It’s a ‘new’ CPython 2.7.x version.  No dependencies on 3rd party libs (e.g., openssl, bzip2, …).
There is an APE patch that’s needed to bring APE closer in line with the current decade.  Take
a look at http://9legacy.org/9legacy/patch/ape-erik.diff

> 2. Is my original problem with mercurial caused by 'hg' or 'python' on Plan9?

It’s a little of both.  The bichued/python + earlier hg does exec up external programs like ssh
using ape/psh.  The new version doesn’t use psh, mostly as none of my script tests on Plan 9
worked like using Python on BSD/Linux/OSX—so there’s a little conflict in what psh does and
what other variants are doing.

> 3. I see a little chicken-egg problem, to clone such 'python' version, I need 'bichued/python' and 'bichued/hg' already installed... ;)

No problem there, you can download source tar+gz|bz2 directly from both bitbucket and selenic.
To build just unpack:

	src/
	   cpython/
	   hg/

and follow the cpython/mkfile rules.

Or you can grab a mkfs from http://9legacy.org/download.html

-jas


[-- Attachment #2: Type: text/html, Size: 2892 bytes --]

  parent reply	other threads:[~2014-06-01 15:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-31 12:41 Pavel Klinkovský
2014-05-31 12:52 ` Steven Stallion
2014-05-31 13:43   ` Pavel Klinkovský
2014-05-31 15:45     ` Jeff Sickel
2014-05-31 16:03       ` Aram Hăvărneanu
2014-05-31 16:17         ` Jeff Sickel
2014-05-31 16:20           ` Aram Hăvărneanu
2014-05-31 16:56             ` Jeff Sickel
2014-05-31 17:07               ` Aram Hăvărneanu
2014-05-31 18:10                 ` erik quanstrom
2014-05-31 22:03                   ` Steve Simon
2014-05-31 18:12                 ` Jeff Sickel
2014-05-31 18:26                   ` Aram Hăvărneanu
2014-05-31 18:37                     ` Jeff Sickel
2014-05-31 18:45                       ` Aram Hăvărneanu
2014-05-31 19:18                         ` Brian L. Stuart
2014-05-31 19:36                           ` Pavel Klinkovský
2014-06-01  5:48                             ` erik quanstrom
2014-06-01  7:45                               ` Pavel Klinkovský
2014-06-01 14:12                                 ` erik quanstrom
2014-06-01 14:46                                   ` Pavel Klinkovský
2014-06-01 14:54                                     ` erik quanstrom
2014-06-01 15:34                                     ` Jeff Sickel [this message]
2014-06-01 17:28                                       ` Pavel Klinkovský
2014-06-01  5:52         ` erik quanstrom
2014-05-31 16:55     ` 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=A7247DE9-924F-49E4-BD75-28FC0E42EA49@corpus-callosum.com \
    --to=jas@corpus-callosum.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).