From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] nupas update
Date: Sun, 16 May 2010 15:51:28 +0100 [thread overview]
Message-ID: <5F6D7D62-ABA5-4426-B8CF-28980B2511E8@fastmail.fm> (raw)
In-Reply-To: <26f3b3b7fc6f7e8e8d90094305925bdd@kw.quanstro.net>
On 16 May 2010, at 15:03, erik quanstrom wrote:
> portage is horrid. i hate it more every time i use it.
> and it doesn't work. revdep rebuild is proof.
>
> it's not clear to me that this is gentoo's fault. linux and
> gnu together are one heck of a difficult place for
> a distribution to live. but replicating portage would seem
> to me to be a big mistake. not only does the plan 9
> community lack the resources to maintain 30 different
> versions of /bin/cp (or whatever), much less portage redux,
> it will encourage gnu/linux habits, because that's what it's
> built for.
>
> we should build something that encourages a simplier
> system, a system plan 9 people would really want.
>
> - erik
>
Indeed, Gnu/Linux is almost unique as an operating system in suffering
from an inconsistent base system which, without going into detail, is
at the very least a huge abuse of everyone's time.
The problem I see here is like this:
1: A consistent base system is extremely desirable.
2: Some parts of the base system sometimes need to be replaced.
3: It is often desirable to be able to safely experiment with
replacement basesystem parts.
Point 2 raises the questions of which parts, and when. Perhaps upas
should be replaced with nupas in the official distribution.
Point 3 is the only one which suggests a package manager, but it
equally alternatively suggests using a filesystem with history, or
perhaps care on the sysadmin's part to archive all files which will be
replaced by the new installation. Automated solutions are of course
possible, but I don't think there is one which solves conflicts
between packages to everyone's satisfaction.
I haven't written half what I could have, but I'm in no mood for
writing, today.
--
Simplicity does not precede complexity, but follows it. -- Alan Perlis
next prev parent reply other threads:[~2010-05-16 14:51 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-03 2:16 erik quanstrom
2009-09-03 2:29 ` David Leimbach
2009-09-03 2:37 ` erik quanstrom
2010-05-15 23:17 ` Akshat Kumar
2010-05-15 23:45 ` erik quanstrom
2010-05-16 2:36 ` ron minnich
2010-05-16 4:15 ` erik quanstrom
2010-05-16 4:28 ` Akshat Kumar
2010-05-16 4:35 ` ron minnich
2010-05-16 4:39 ` erik quanstrom
2010-05-16 4:51 ` ron minnich
2010-05-16 4:57 ` Akshat Kumar
2010-05-16 5:44 ` ron minnich
2010-05-16 13:42 ` EBo
2010-05-16 14:03 ` erik quanstrom
2010-05-16 14:51 ` Ethan Grammatikidis [this message]
2010-05-16 15:37 ` EBo
2010-05-16 15:53 ` Ethan Grammatikidis
2010-05-16 16:02 ` ron minnich
2010-05-16 17:10 ` Ethan Grammatikidis
2010-05-16 17:19 ` EBo
2010-05-16 15:21 ` EBo
2010-05-16 15:42 ` Ethan Grammatikidis
2010-05-16 17:34 ` EBo
2010-05-16 17:47 ` hiro
2010-05-16 18:58 ` Corey
2010-05-16 19:29 ` EBo
2010-05-18 21:35 ` Georg Lehner
2010-05-18 22:07 ` ron minnich
2010-05-16 15:46 ` Jorden M
2010-05-16 15:59 ` Ethan Grammatikidis
2010-05-16 15:42 ` Jorden M
2010-05-16 18:24 ` erik quanstrom
2010-05-16 18:49 ` EBo
2010-05-16 20:44 ` erik quanstrom
2010-05-16 21:44 ` EBo
2010-05-17 1:17 ` erik quanstrom
2010-05-17 1:52 ` EBo
2010-05-17 1:58 ` erik quanstrom
2010-05-17 1:35 ` Akshat Kumar
2010-05-17 4:09 ` ron minnich
2010-05-17 4:19 ` erik quanstrom
2010-05-17 4:56 ` ron minnich
2010-05-18 23:50 ` Federico G. Benavento
2010-05-18 23:59 ` ron minnich
2010-05-19 0:40 ` Jorden M
2010-05-19 1:40 ` Robert Ransom
-- strict thread matches above, loose matches on Subject: below --
2009-08-06 15:23 erik quanstrom
2008-10-23 0:08 erik quanstrom
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=5F6D7D62-ABA5-4426-B8CF-28980B2511E8@fastmail.fm \
--to=eekee57@fastmail.fm \
--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).