From: Greg Troxel <gdt@ir.bbn.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [RFH] NetBSD 6?
Date: Wed, 02 Jan 2013 19:30:24 -0500 [thread overview]
Message-ID: <rmipq1numzj.fsf@fnord.ir.bbn.com> (raw)
In-Reply-To: <7vd2xn18p5.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed, 02 Jan 2013 15:11:50 -0800")
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
Junio C Hamano <gitster@pobox.com> writes:
> I would appreciate if somebody with more familiarlity with the
> platform can suggest a better alternative than applying the
> following patch to our Makefile. Right now I have an equivalent of
> this change in config.mak locally when building on the said
> platform.
I realized after sending my previous reply that you are probably trying
to have a way to build and run tests on NetBSD-6 from a git checkout as
part of development testing.
One approach I've taken with other programs is to have a README.NetBSD
file which is actually an executable /bin/sh script with comments,
explaining the prereqs in terms of pkgsrc and invoking configure to get
dependencies from pkgsrc (-I/usr/pkg/include plus -L/-R).
So in the git case, this could set PYTHON_PATH in the environment.
I realize a README.foo file for N different systems could be clutter,
but having these checked in would provide the concise help that people
on any of those platforms need.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2013-01-03 0:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-02 23:11 [RFH] NetBSD 6? Junio C Hamano
2013-01-03 0:25 ` Greg Troxel
2013-01-03 0:30 ` Greg Troxel [this message]
2013-01-03 2:15 ` Junio C Hamano
2013-01-03 13:58 ` Greg Troxel
2013-01-03 16:17 ` Junio C Hamano
2013-01-03 18:27 ` Greg Troxel
2013-01-03 19:28 ` Stefano Lattarini
2013-01-08 18:53 ` Greg Troxel
2013-01-08 19:03 ` Junio C Hamano
2013-01-08 19:08 ` Greg Troxel
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=rmipq1numzj.fsf@fnord.ir.bbn.com \
--to=gdt@ir.bbn.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.