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] using git
Date: Mon, 30 Mar 2015 11:16:38 -0500	[thread overview]
Message-ID: <B6B24435-A5C5-415F-B3C1-7BD9E423233D@corpus-callosum.com> (raw)
In-Reply-To: <CAHL7psF0z34nJxfaaW7EMx6QUvBam9vmTvu59K7bG-9pLJe6Kg@mail.gmail.com>


> On Mar 30, 2015, at 4:55 AM, Giacomo Tesio <giacomo@tesio.it> wrote:
> 
> Ah, a small addendum: obviously we also use tags a lot to give a specific commit (and related history) a name.
> This is done automatically by build servers for the "official" tags, and manually by developers whenever they want in their own repository (often with tags like, "workedhere", "shittorefactortomorrow" and so on).

All of those features are available in hg, darcs, and other dscm tools.

But to get back on topic, unless I’ve overlooked a contrib package somewhere, how about we begin with the requirements to get a fully working git installed on Plan 9.  For example,

## the dependencies required for git on a bare-bones FreeBSD install:
# pkg install git
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
The following 18 packages will be affected (of 0 checked):

New packages to be INSTALLED:
        git: 2.3.4
        expat: 2.1.0_2
        p5-Authen-SASL: 2.16_1
        p5-GSSAPI: 0.28_1
        perl5: 5.18.4_11
        p5-Digest-HMAC: 1.03_1
        p5-Net-SMTP-SSL: 1.01_3
        p5-IO-Socket-SSL: 2.012
        p5-Mozilla-CA: 20141217
        p5-Net-SSLeay: 1.68
        p5-Socket: 2.018
        p5-IO-Socket-IP: 0.37
        python27: 2.7.9
        libffi: 3.2.1
        p5-Error: 0.17023
        curl: 7.41.0
        ca_root_nss: 3.18
        cvsps: 2.1_1



I’m not sure what cvsps is for, that seems to have cropped up on the fbsd pkg sometime between git versions 2.3.1 and 2.3.4.  It’s been years^wdecades since I’ve tinkered with perl, and I’m fairly certain the perl 5.8 version available on Plan 9 won’t support the modules included in the above list.  So Plan 9 needs a modern perl to run git effectively with specific attention to the additional modules.  Expat is the “eXpat XML parser library”.  Libffi is something maintained on sources.redhat.com.  Many of those modules depend on OpenSSL, so add that to the list.  It’s also possible a recent port of bash will also be required as the git support scripts may not work with our ape/sh or ape/psh.  We’ve got python 2.7.8 [.9 soon] covered.  

Piece of cake, all that should fit on a coaster.

-jas







  reply	other threads:[~2015-03-30 16:16 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 20:30 [9fans] ken cc for linux Aharon Robbins
2015-03-11 20:34 ` Aram Hăvărneanu
2015-03-11 21:04 ` Ryan Gonzalez
2015-03-11 21:54   ` Quintile
2015-03-11 23:04     ` Ryan Gonzalez
2015-03-11 23:19       ` Steve Simon
2015-03-12  6:39         ` arnold
2015-03-13  1:31     ` erik quanstrom
2015-03-13 13:24       ` Charles Forsyth
2015-03-13 17:59         ` Ryan Gonzalez
2015-03-13 18:19           ` Kurt H Maier
2015-03-19 15:35             ` Jeff Sickel
2015-03-19 16:09               ` [9fans] using git arnold
2015-03-19 16:22                 ` Stanley Lieber
2015-03-19 16:34                 ` Charles Forsyth
2015-03-19 16:36                   ` Charles Forsyth
2015-03-19 16:39                     ` Federico Benavento
2015-04-03 18:46                       ` Jeff Sickel
2015-03-19 18:03                   ` Skip Tavakkolian
2015-03-19 20:30                     ` Jeff Sickel
2015-03-19 21:46                       ` Skip Tavakkolian
2015-03-19 21:54                         ` Devon H. O'Dell
2015-03-20  1:02                           ` Kurt H Maier
2015-03-19 18:26                   ` arnold
2015-03-28 11:14                     ` Charles Forsyth
2015-03-28 14:00                       ` Paul Lalonde
2015-03-30  9:48                         ` Giacomo Tesio
2015-03-30  9:55                           ` Giacomo Tesio
2015-03-30 16:16                             ` Jeff Sickel [this message]
2015-03-30 19:47                               ` Stanley Lieber
2015-03-30 20:41                                 ` Bakul Shah
2015-03-30 20:20                               ` Giacomo Tesio
2015-03-30 20:32                                 ` Ryan Gonzalez
2015-03-31  3:17                                 ` arnold
2015-03-19 17:00                 ` Jeff Sickel
2015-03-19 17:36                   ` Ori Bernstein
2015-03-12  8:50   ` [9fans] ken cc for linux Aram Hăvărneanu
2015-03-12 17:53     ` Ryan Gonzalez
2015-03-12  8:51   ` Aram Hăvărneanu
2015-03-12 10:06     ` Charles Forsyth
2015-03-12 15:23       ` Charles Forsyth
2015-03-12 15:41         ` Brantley Coile
2015-03-12 17:14           ` Charles Forsyth
2015-03-13  1:28             ` erik quanstrom
2015-03-12 17:52     ` Ryan Gonzalez

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=B6B24435-A5C5-415F-B3C1-7BD9E423233D@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).