From: Sebastian Pipping <webmaster@hartwork.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] DistroWatch and Gentoo packages: status quo and future
Date: Sat, 12 Sep 2009 19:26:44 +0200 [thread overview]
Message-ID: <4AABD9D4.3030802@hartwork.org> (raw)
In-Reply-To: <200909120048.54012.bauman.aaron@gmail.com>
Aaron Bauman wrote:
> Sebastian,
> I definitely admire your point and know that through your tracking and Google
> SoC project you have good visibility on this I do however have to disagree.
> As much as I enjoy the open source community and admire the products they put
> out I do believe Gentoo has the right approach to packaging.
> My standpoint is that Gentoo always ensures stability in the fact that we
> require packages to be tested prior to release in the main portage tree and
> secondly the Gentoo developers always ensure security as best as they can.
> These I believe are what keep the portage tree somewhat behind the latest and
> greatest and as always there are overlays and options that allow users to pull
> these packages down if they want.
> I believe the great thing about Gentoo is the choice of whether to be cutting
> edge or not. If I have missed anything please let me know.
I don't think we should trade away quality. You said you disagree with
me but with that said I don't see at which point.
Sebastian
next prev parent reply other threads:[~2009-09-12 17:26 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 ` [gentoo-dev] " Ryan Hill
2009-09-12 12:15 ` 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 [this message]
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=4AABD9D4.3030802@hartwork.org \
--to=webmaster@hartwork.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