From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: DistroWatch and Gentoo packages: status quo and future
Date: Sun, 13 Sep 2009 13:59:26 +0000 (UTC) [thread overview]
Message-ID: <pan.2009.09.13.13.59.25@cox.net> (raw)
In-Reply-To: 4b0462b4d4cc0f26a7b45e6787d51890@localhost
Jesús Guerrero posted on Sun, 13 Sep 2009 11:11:42 +0200 as excerpted:
> 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.
>
> Seriously, I doubt that the average Gentoo user comes from Distrowatch.
> Gentoo is born from a necessity which is very different from the usual
> binary distro. Gentoo has never been about fame or marketing.
++
[package listing of not in Gentoo tree or way outdated]
>> Miro
>> .. Not in official tree (yet?), available through an Overlay
>>
>> xmms
>> .. Removed for security reasons, available through an Overlay
>>
>> Maybe we should move Miro to the main tree?
>
> Most Gentoo users will have no problem to use overlays as they need
> them.
Agreed. Yes, overlays are perhaps a bit more trouble to setup than
simply maintaining normal tree updates once setup. But let's get some
context here. layman's no difficulty at all, really, when compared to
the ordinary stuff we expect Gentoo users to do all the time. Gentoo has
never been about spoon-feeding and this is no exception. Layman is a
great and powerful tool, certainly, and like any powerful tool, it takes
a bit of learning to use, before even the user should trust himself with
it. =:^) But that's more true of Gentoo itself than it is of layman, and
anyone who can manage Gentoo can certainly manage layman with little
trouble.
> If we had more developers we could as maintain more packages, as
> simple as that.
Indeed.
> Besides that, if you want some new version, you are free to use
> bugs.gentoo.org to submit a bug, version bump, or whatever.
I'm not so sure about this. Sure, one can submit a bug, but would that
have done any good on, say, kde4, one popular overlay people use,
particularly during the period that portage didn't work with it? What
about the kde sets? Would they be allowed in the tree just based on a
bug? The obvious answer is no, and there's good reasons for it.
I can see the argument both ways for putting stuff like that in the main
tree -- masked, of course, and possibly in an obscure location that the
PMs could ignore unless configured otherwise. Personally, I'd like to
see more of it in the main tree, hard-masked when necessary, instead of
in the overlays. But I have a strong suspicion I'd feel otherwise if I
were one of the devs tasked with getting packages like that, particularly
huge interrelated conglomerations of packages like that, actually into
some sort of usable working (for ordinary Gentoo users. altho as I said
above, they're already a cut above ordinary users) shape.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2009-09-13 14:00 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
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 ` Duncan [this message]
2009-09-13 14:36 ` [gentoo-dev] Re: DistroWatch and Gentoo packages: status quo and future 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=pan.2009.09.13.13.59.25@cox.net \
--to=1i5t5.duncan@cox.net \
--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