From: "Andrey G. Grozin" <A.G.Grozin@inp.nsk.su>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci team help
Date: Tue, 16 Oct 2007 12:01:56 +0700 (NOVST) [thread overview]
Message-ID: <Pine.LNX.4.64.0710161145380.10884@star.inp.nsk.su> (raw)
In-Reply-To: <20071015201410.GJ23990@supernova>
On Mon, 15 Oct 2007, Donnie Berkholz wrote:
> I think a good way to start is to make the overlay an "accepted"
> solution for where to keep packages. Get more people participating in
> the overlay, and even be willing to move packages from the main tree to
> the overlay if there's non-devs willing to help with things that are
> poorly maintained.
The original cryos' idea when he created the science overlay was a place
to develop ebuilds until they become mature enough to be moved to the main
tree (I can dig his original post about this subject). He suggested that
ebuilds whould, in most cases, be moved to the main tree quickly enough.
Gentoo users are not instructed to use overlays. Most of them just don't
know about them. Hunting for an interesting package in many tens of
overlays present at overlays.gentoo.org is not easy. A package in an
overlay can depend on some other packages in the same overlay, etc. So,
from the user's perspective, overlays are obscure (which ones should I add
to my tree? Where are packages that are of interest for me? Should I
browse all this stuff at overlays.gentoo.org? Oh my...) They also add an
extra layer of complexity (should I install layman? How to use it? Are the
overlays updated when I do emerge --sync? What, I should do this by hand?
Oh my...) And Gentoo is complex enough for users even without this extra
layer of new and unknown concepts.
If we *really* want to divide packages into first-class citizens and
second-class ones (residing in overlays), we should do several things.
1. Inform users *prominently* that some interesting packages don't live in
the main portage tree (currently, not many users know this).
2. Write a chapter about overlays and layman for the Gentoo user guide.
Who will decide which packages are first-class citizens and which are not?
What are the criteria?
Andrey
--
gentoo-science@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-16 5:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 18:39 [gentoo-science] sci team help Sébastien Fabbro
2007-10-15 19:09 ` C Y
2007-10-15 19:11 ` Yuriy Rusinov
2007-10-15 20:26 ` Sébastien Fabbro
2007-10-23 15:16 ` Redouane Boumghar
2007-10-15 20:14 ` Donnie Berkholz
2007-10-15 21:02 ` Jukka Ruohonen
2007-10-16 1:19 ` Markus Luisser
2007-10-16 9:50 ` Sébastien Fabbro
2007-10-16 10:18 ` Sébastien Fabbro
2007-10-16 5:01 ` Andrey G. Grozin [this message]
2007-10-16 7:20 ` Donnie Berkholz
2007-10-16 9:54 ` Sébastien Fabbro
2007-10-16 10:04 ` Jukka Ruohonen
2007-10-16 10:15 ` Donnie Berkholz
2007-10-16 2:41 ` Nuno Sucena Almeida
2007-10-16 13:57 ` M. Edward (Ed) Borasky
2007-10-16 15:03 ` Sébastien Fabbro
2007-10-16 19:11 ` Nuno Sucena Almeida
2007-10-16 22:51 ` Donnie Berkholz
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=Pine.LNX.4.64.0710161145380.10884@star.inp.nsk.su \
--to=a.g.grozin@inp.nsk.su \
--cc=gentoo-science@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