From: Gabriel Diaz <gabidiaz@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 12:29:23 +0200 [thread overview]
Message-ID: <82c890d0050810032916704473@mail.gmail.com> (raw)
In-Reply-To: <89d1e7b8050810030348f99ef0@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Hello,
Afaik plan9ports main target is make a plan9-like environment on unix
clones to develop in the same way plan9. And to make a program work in plan9
and unix without modifications.
I think that is the reason of that extra-abstraction you mention.
may be i'm wrong, so wait for Russ comment :)
gabi
2005/8/10, Anselm R. Garbe <garbeam@gmail.com>:
>
> On 8/10/05, Skip Tavakkolian <9nut@9netics.com> wrote:
> > > It doesn't depends on mk, because in my eyes the mk-based build chain
> > > in p9p is rather complex.
> >
> > see an optometrist ☺
>
> I don't need to, nothing wrong with my eyes. Just have a look into
> bin/9* and I ask why this extra-abstraction is needed... Then see
> src/mk* - pretty much stuff, isn't one general inclusion sufficient?
> Why are shell scripts (like INSTALL), make and mk needed? Isn't make
> for bootstrapping enough and afterwards only mk?
>
> I didn't said that the system is bad, but it can be done simplier. For
> the monolithic character, the main reason to me is, that all headers
> reside in $PLAN9/include, which could be done in two places, that it
> is easier to just have a bunch of independent libs with their headers
> and a central place (poorly there is no union mount in *NIX) where all
> headers get together... Currently it is very much effort to determine
> which headers are needed/provided by which lib in src/lib*...
>
> Regards,
> --
> Anselm R. Garbe ><>< www.ebrag.de <http://www.ebrag.de> ><>< GPG key:
> 0D73F361
>
[-- Attachment #2: Type: text/html, Size: 2019 bytes --]
next prev parent reply other threads:[~2005-08-10 10:29 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 [this message]
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
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=82c890d0050810032916704473@mail.gmail.com \
--to=gabidiaz@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).