From: "Russ Cox" <rsc@swtch.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] complaints about new web site
Date: Sat, 28 Jan 2006 09:18:28 -0500 [thread overview]
Message-ID: <20060128141832.88F171E8C29@holo.morphisms.net> (raw)
In-Reply-To: <20060128085244.GA442@routi.local.net>
> 1.) We create two places to look for software (sources and web)
>
> 2.) It may be stuff _new_ people commonly want - I don't want GCC on
> Plan 9. And those people probably don't really want GCC either.
No one really wants gcc. But TeX was the original "additional software"
and it remains useful and worth being easy to find. So is Python.
Everything on the additional software page is links to sources,
so there's really only one place to find the archives. There's also
only one real place to look for software, and that's the web page,
unless you like reading large unsorted lists of software packages.
(What Uriel has built is not an index. It is a table of contents.
A real index would actually help a lot.)
Russ
next prev parent reply other threads:[~2006-01-28 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-27 17:21 Russ Cox
2006-01-27 17:38 ` erik quanstrom
2006-01-27 18:42 ` Sascha Retzki
2006-01-27 19:04 ` Russ Cox
2006-01-28 8:52 ` Sascha Retzki
2006-01-28 14:18 ` Russ Cox [this message]
2006-01-28 18:41 ` uriel
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=20060128141832.88F171E8C29@holo.morphisms.net \
--to=rsc@swtch.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).