From: Ryan Hill <dirtyepic@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: DistroWatch and Gentoo packages: status quo and future
Date: Fri, 11 Sep 2009 20:24:02 -0600 [thread overview]
Message-ID: <20090911202402.19ae0319@gentoo.org> (raw)
In-Reply-To: 4AAAD714.1010107@hartwork.org
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
On Sat, 12 Sep 2009 01:02:44 +0200
Sebastian Pipping <webmaster@hartwork.org> wrote:
> Among other information the Gentoo page at DistroWatch [1] displays a
> table on about 200 selected packages [2] and how up to date Gentoo is
> per package. I assume that DistroWatch is still one of the first places
> people go to get a feeling for a Distro they heard about, besides
> Wikpedia and ${distro}.org.
>
> The freshness of these 200 packages have influence on how people
> perceive Gentoo on DistroWatch. While the tree as a whole is what we
> should keep as up to date as possible keeping these 200 packages (list
> further down) up to date can therefore be of particular importance.
Personally I don't see how gaming the system helps us in any way.
Also, screw DW.
--
fonts, Character is what you are in the dark.
gcc-porting,
wxwidgets @ gentoo EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-09-12 2:24 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-11 23:02 [gentoo-dev] DistroWatch and Gentoo packages: status quo and future Sebastian Pipping
2009-09-12 2:24 ` Ryan Hill [this message]
2009-09-12 12:15 ` [gentoo-dev] " Sebastian Pipping
2009-09-14 2:46 ` Ryan Hill
2009-09-29 1:08 ` Donnie Berkholz
2009-09-12 4:48 ` [gentoo-dev] " Aaron Bauman
2009-09-12 17:26 ` Sebastian Pipping
2009-09-12 11:23 ` Marijn Schouten (hkBst)
2009-09-12 17:29 ` Sebastian Pipping
2009-09-13 9:11 ` Jesús Guerrero
2009-09-13 10:47 ` Richard Freeman
2009-09-13 10:57 ` Jesús Guerrero
2009-09-13 13:24 ` Richard Freeman
2009-09-13 19:39 ` Sebastian Pipping
2009-09-13 19:38 ` Sebastian Pipping
2009-09-13 11:30 ` [gentoo-dev] overlay usage and maintainence [was: DistroWatch and Gentoo packages: status quo and future] Thomas Sachau
2009-09-13 18:57 ` Patrick Lauer
2009-09-13 19:03 ` Jesús Guerrero
2009-09-13 19:41 ` Patrick Lauer
2009-09-13 20:04 ` Jesús Guerrero
2009-09-13 19:25 ` Alexander Færøy
2009-09-13 19:45 ` Sebastian Pipping
2009-09-13 20:00 ` Alexander Færøy
2009-09-13 20:02 ` Ciaran McCreesh
2009-09-13 20:17 ` Sebastian Pipping
2009-09-14 14:05 ` Ciaran McCreesh
2009-09-14 18:28 ` Sebastian Pipping
2009-09-14 18:51 ` Ciaran McCreesh
2009-09-14 22:03 ` Zac Medico
2009-09-16 20:31 ` Sebastian Pipping
2009-09-16 21:21 ` Zac Medico
2009-09-13 13:59 ` [gentoo-dev] Re: DistroWatch and Gentoo packages: status quo and future Duncan
2009-09-13 14:36 ` Dale
2009-09-13 15:05 ` Albert Hopkins
2009-09-13 15:45 ` Dale
2009-09-13 19:52 ` Sebastian Pipping
2009-09-13 21:25 ` Dale
2009-09-13 21:54 ` Alex Legler
2009-09-13 22:08 ` Dale
2009-09-13 22:53 ` Alex Legler
2009-09-13 23:06 ` Dale
2009-09-13 20:00 ` Sebastian Pipping
2009-09-20 19:12 ` Duncan
2009-09-21 2:10 ` Angelo Arrifano
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=20090911202402.19ae0319@gentoo.org \
--to=dirtyepic@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/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