From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@9fans.net
Subject: Re: [9fans] Building Go on Plan 9
Date: Fri, 2 Dec 2011 05:39:13 +0200 [thread overview]
Message-ID: <6c4047deda8f6556c4f68b34b8f78dd6@proxima.alt.za> (raw)
In-Reply-To: <alpine.OSX.1.10.1112011153090.649@peregrinwifi.orthanc.ca>
>> There's nothing wrong with mk. It's just that
>> I highly doubt we could get a separate set of
>> mkfiles included in the Go distribution.
>
> Have you tried? It's a non-invasive change, and once they are set up it's
> unlikely they will need to be updated often.
I think Anthony is on the right path on this point, in that I've had
to update a couple of mkfiles in the recent past because I had
overlooked changes to the coresponding Makefiles. Not many, but they
do trigger additional maintenance problems.
The only alternative option I would pick is to merge the Go release
into the Plan 9 (and nix) distribution - mkfiles and all - then use a
mechanism analogous to mine to keep them in sync. The unsuspecting
public would never see the hard backroom effort.
In my fantasies, I see p9p as a stepping stone in that direction.
Lastly, my congratulations to Anthony, if there is any way I can
assist in merging the code, I'd be happy to help (just don't ask me to
install Python and Mercurial on my Plan 9 system - mind you, I'll
probably have to do so, sooner or later :-(.
Lucio.
next prev parent reply other threads:[~2011-12-02 3:39 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 17:48 Anthony Martin
2011-12-01 17:51 ` erik quanstrom
2011-12-01 18:00 ` John Floren
2011-12-01 18:05 ` Stanley Lieber
2011-12-01 18:14 ` Anthony Martin
2011-12-01 18:19 ` Charles Forsyth
2011-12-01 18:25 ` Lyndon Nerenberg
2011-12-01 19:07 ` Anthony Martin
2011-12-01 19:54 ` Lyndon Nerenberg
2011-12-02 3:39 ` Lucio De Re [this message]
2011-12-02 14:33 ` Anthony Martin
2011-12-02 14:57 ` erik quanstrom
2011-12-02 15:23 ` Anthony Martin
2011-12-02 17:14 ` Skip Tavakkolian
2011-12-02 15:19 ` Lyndon Nerenberg
2011-12-02 15:59 ` Lucio De Re
2011-12-02 16:09 ` Lucio De Re
2011-12-02 17:24 ` ron minnich
2011-12-02 17:55 ` Lyndon Nerenberg
2011-12-02 17:58 ` Francisco J Ballesteros
2011-12-02 18:19 ` ron minnich
[not found] ` <CAP6exYKKqsc0Kwyhxp_LiXf0oRUJ79UYWZM=Ugp2WPZ7TZATwQ@mail.gmail.c>
2011-12-02 21:42 ` erik quanstrom
2011-12-02 22:12 ` andrey mirtchovski
2011-12-02 22:13 ` andrey mirtchovski
2011-12-02 17:58 ` Lyndon Nerenberg
2011-12-02 18:01 ` erik quanstrom
2011-12-02 6:34 ` ron minnich
2011-12-02 6:42 ` Lucio De Re
2011-12-02 8:49 ` Francisco J Ballesteros
2011-12-02 17:21 ` ron minnich
2011-12-01 18:28 ` Anthony Martin
2011-12-01 18:30 ` erik quanstrom
2011-12-01 18:45 ` Anthony Martin
2011-12-01 18:48 ` Anthony Martin
2011-12-01 18:18 ` Anthony Martin
2011-12-02 14:40 ` Pavel Zholkover
2011-12-02 14:57 ` Anthony Martin
2011-12-02 20:25 ` [9fans] go v. mk Lyndon Nerenberg
2011-12-02 20:37 ` ron minnich
2011-12-03 0:06 ` Steve Simon
2011-12-03 0:11 ` Lyndon Nerenberg
2011-12-03 0:12 ` ron minnich
2011-12-05 0:32 ` Federico Benavento
2011-12-05 0:44 ` John Floren
2011-12-05 12:20 ` Federico Benavento
2011-12-27 14:38 ` Aram Hăvărneanu
2011-12-01 19:20 [9fans] Building Go on Plan 9 lsub
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=6c4047deda8f6556c4f68b34b8f78dd6@proxima.alt.za \
--to=lucio@proxima.alt.za \
--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).