From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] sci team help
Date: Tue, 16 Oct 2007 00:20:30 -0700 [thread overview]
Message-ID: <20071016072030.GS23990@supernova> (raw)
In-Reply-To: <Pine.LNX.4.64.0710161145380.10884@star.inp.nsk.su>
On 12:01 Tue 16 Oct , Andrey G. Grozin wrote:
> 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.
OK, sure, but historic reasons are not future reasons. If things should
change, this is not a reason to hold it back.
> 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.
There is http://www.gentoo.org/proj/en/overlays/userguide.xml -- for
some reason, it doesn't appear to be linked from the main docs section.
I just asked in #gentoo-doc about this.
I agree that hunting could be difficult, but most of the project (rather
than developer-owned) overlays are topical by definition. If I'm looking
for a scientific application, it shouldn't take a leap of logic to try
the science overlay. Also, eix (a searching tool) includes a searchable
package cache of every overlay, generated daily.
> 1. Inform users *prominently* that some interesting packages don't live in
> the main portage tree (currently, not many users know this).
Yep.
> Who will decide which packages are first-class citizens and which are not?
> What are the criteria?
I suggested a few.
- Is a developer willing to commit to maintaining it?
- Is it expected to be fairly popular, or is it extremely specific?
- (for apps already in the tree) Is it unmaintained? Should it be
moved to an overlay?
Thanks,
Donnie
--
gentoo-science@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-16 7:31 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
2007-10-16 7:20 ` Donnie Berkholz [this message]
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=20071016072030.GS23990@supernova \
--to=dberkholz@gentoo.org \
--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