git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFH] NetBSD 6?

From
GTGreg Troxel <gdt@ir.bbn.com>
Date
Jan 3, 2013, 00:30 UTC
Message-ID
<rmipq1numzj.fsf@fnord.ir.bbn.com>
In-Reply-To
<7vd2xn18p5.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
Show 5 quoted lines
> 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.

Previous: Greg TroxelNext: Junio C Hamano
Message 3 of 11 in “[RFH] NetBSD 6?”
  1. Junio C HamanoJan 2, 2013
  2. Greg TroxelJan 3, 2013
  3. Greg TroxelJan 3, 2013
  4. Junio C HamanoJan 3, 2013
  5. Greg TroxelJan 3, 2013
  6. Junio C HamanoJan 3, 2013
  7. Greg TroxelJan 3, 2013
  8. Stefano LattariniJan 3, 2013
  9. Greg TroxelJan 8, 2013
  10. Junio C HamanoJan 8, 2013
  11. Greg TroxelJan 8, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.