From: "Anselm R. Garbe" <garbeam@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Standalone unix port of the original rc shell
Date: Wed, 10 Aug 2005 17:36:55 +0200 [thread overview]
Message-ID: <89d1e7b805081008362e6f31a9@mail.gmail.com> (raw)
In-Reply-To: <42FA1764.2050801@lanl.gov>
On 8/10/05, Ronald G Minnich <rminnich@lanl.gov> wrote:
> I wonder if the objections to how p9p builds is the now-common syndrome
> of viewing the world through Linux and/or GNU eyes only. I see this
> frequently -- packages modified to be better on linux, or under some
> wacky GNU build environment, which then break on other OSes.
Nah, that was not my point, then we misunderstood each other. I don't
like the GNU way as well. My impression can be summed up to "why using
shell scripts, make and mk - instead of make and mk" - which means
getting rid of shell scripts at first glance seemed me to make it
simplier. But as mentioned I understand the sense of 9* shell scripts.
> It's the new definition of portable -- "It builds fine on all versions
> of gentoo I've tried, but only with kernel 2.6.9".
>
> p9p is remarkable to me in that it builds on anything, without automake,
> configure, autoconfig, dev-wrappers, and that other horrible stuff. You
> just type make. What a concept!
>
> GNU has somehow managed to create a "portability environment" which is
> far less portable and and far less convenient than p9p, but also about
> 100 times harder to deal with. NOT progress. There's a lesson in p9p
> that I wish the GNU world would heed.
Tell that the GNU morons, I'm hopefully far away from them... I prefer
one system, wether make or mk doesn't matters and try to reduce all
additional dependencies when possible. Maybe the GNU world prefers
shell scripts+m4+autoconf+automake+Make+ant+wtf to build their
software, because they want to notice the build process at a speed
level with todays computers they can follow (./configure == for each
line; perform line; sleep 2s; continue;)...
Regards,
--
Anselm R. Garbe ><>< www.ebrag.de ><>< GPG key: 0D73F361
prev parent reply other threads:[~2005-08-10 15:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 14:16 Anselm R. Garbe
2005-08-09 15:22 ` Federico Benavento
2005-08-09 15:28 ` Anselm R. Garbe
2005-08-10 5:54 ` Skip Tavakkolian
2005-08-10 10:03 ` Anselm R. Garbe
2005-08-10 10:29 ` Gabriel Diaz
2005-08-10 12:38 ` Anselm R. Garbe
2005-08-10 12:43 ` Gabriel Diaz
2005-08-10 12:57 ` Anselm R. Garbe
2005-08-10 14:55 ` Ronald G Minnich
2005-08-10 13:50 ` Russ Cox
2005-08-10 14:23 ` Anselm R. Garbe
2005-08-10 15:31 ` Russ Cox
2005-08-10 15:52 ` Anselm R. Garbe
2005-08-10 15:04 ` Ronald G Minnich
2005-08-10 15:18 ` Russ Cox
2005-08-10 15:33 ` Artem Letko
2005-08-10 15:38 ` Ronald G Minnich
2005-08-10 22:34 ` Andy Newman
2005-08-10 15:36 ` Anselm R. Garbe [this message]
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=89d1e7b805081008362e6f31a9@mail.gmail.com \
--to=garbeam@gmail.com \
--cc=9fans@cse.psu.edu \
/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).