From: "EBo" <ebo@sandien.com>
To: <9fans@9fans.net>
Subject: [9fans] build system: [was: (no subject)]
Date: Sun, 7 Mar 2010 06:38:13 -0700 [thread overview]
Message-ID: <twig.1267969093.35494@swcp.com> (raw)
> Of course, one would then be tempted (as I have been) to look more
> seriously at porting the NetBSD package system to Plan 9. That's not
> out of the question, in fact it's probably not too difficult, but the
> residual pain of autoconf for each individual package has already
> frightened people with a stronger stomach than mine away. That is why
> I cannot suggest we catch up, but it may be nice to be ready when
> eventually the autoconf edifice falls down and something mildly
> intelligent takes its place!
>
> Ironically, Plan 9 may be the platform on which a replacement for
> autoconf could be designed and implemented. But that's too close to a
> pipedream to be given serious consideration.
Take a look at Boost's port of Perforce Software's build tool Jam
<http://www.boost.org/doc/tools/jam/index.html>. What little I have used it
in the past it came across as a much more elegant tool-chain. Now what I
would LOVE to see is a port of Joel de Gusman's Spirit++. Well I can dream
cannt I ;-)
I've also started on updating an old per-application portage ebuild based on
Anant's work back in 2007. If that is of any interest maybe I could get you
to either collaborate or just do a little testing.
EBo --
next reply other threads:[~2010-03-07 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-07 13:38 EBo [this message]
2010-03-07 16:31 ` erik quanstrom
2010-03-11 17:14 ` EBo
2010-03-11 17:47 ` David Leimbach
2010-03-07 17:22 ` lucio
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=twig.1267969093.35494@swcp.com \
--to=ebo@sandien.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).