From: George Shapovalov <georges@its.caltech.edu>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Contribute many ebuilds at once
Date: Sun, 9 Jun 2002 11:53:37 -0700 [thread overview]
Message-ID: <200206091153.37850.georges@its.caltech.edu> (raw)
In-Reply-To: <3D03C6D0.80707@seul.org>
Hi guys.
I think you may be interested in taking a look at #1523:
http://bugs.gentoo.org/show_bug.cgi?id=1523
This is a proposal of ebuild submission/processing system, that involves
streamlined submission, multiple stability levels, votes, even some ideas on
developer ratings :).
Its implementation is moving not particularly fast I should admit. Quite
expectedly, as it involves modifications to numerous subsistems and
resolution of other problems along the way (such as enhanced
masking/stability levels).
Any thoughts/comments are wellcome!.
George
--------------
Jeremiah Mahler wrote:
>
> I imagine it as something where the user configures the
> minimum level of packages that they are willing to install.
> For example, a user might only be willing to install packages
> that are stable or rated 4/5 by 20 or more people.
I'm not sure that many people would like this,
because nothing stops someone to multiple rate a package.
(you can make it difficult, but not so difficult).
It could be good, and perhaps an option for
non production systems used to test gentoo. But I think
that a clean cut somewhere must be made. For
example all packages non labeled definitive are placed
in a category. When you emerge rsync
the files are updated and the rating is contained in the .emerge
"RATING = 5". You can browse packages, install them by hand,
but they should not be used as depend for a stable ebuild.
This way an administrator has more control over what gets installed
and it can be a bit more relaxed when installing official packages.
next prev parent reply other threads:[~2002-06-09 18:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 6:07 [gentoo-dev] Contribute many ebuilds at once Marko Mikulicic
2002-06-09 0:18 ` Karl Trygve Kalleberg
2002-06-09 0:53 ` Jano Lukac
2002-06-09 6:55 ` Marko Mikulicic
2002-06-09 15:41 ` Karl Trygve Kalleberg
2002-06-09 6:41 ` Marko Mikulicic
2002-06-09 10:56 ` Paul de Vrieze
2002-06-09 17:35 ` Marko Mikulicic
2002-06-09 12:25 ` Jeremiah Mahler
2002-06-09 15:29 ` Markus Krainer
2002-06-09 18:46 ` Marko Mikulicic
2002-06-09 14:40 ` Jeremiah Mahler
2002-06-09 21:21 ` Marko Mikulicic
2002-06-09 18:53 ` George Shapovalov [this message]
2002-06-09 19:57 ` Karl Trygve Kalleberg
2002-06-09 15:56 ` Karl Trygve Kalleberg
2002-06-09 19:31 ` Marko Mikulicic
2002-06-09 15:39 ` Karl Trygve Kalleberg
2002-06-09 21:53 ` Marko Mikulicic
2002-06-09 16:03 ` Karl Trygve Kalleberg
2002-06-09 16:17 ` Markus Krainer
2002-06-10 0:54 ` Marko Mikulicic
2002-06-09 19:53 ` Karl Trygve Kalleberg
2002-06-09 21:37 ` [gentoo-dev] cvs keywords (was: Contribute many ebuilds at once) Alexander Holler
2002-06-10 3:46 ` Marko Mikulicic
2002-06-09 22:25 ` [gentoo-dev] cvs keywords Alexander Holler
2002-06-10 7:41 ` Marko Mikulicic
2002-06-09 22:11 ` [gentoo-dev] Contribute many ebuilds at once Marko Mikulicic
2002-06-09 19:52 ` Karl Trygve Kalleberg
2002-06-09 21:04 ` [gentoo-dev] cvs keywords (was: Contribute many ebuilds at once) Alexander Holler
2002-06-10 1:33 ` Markus Krainer
2002-06-10 0:50 ` [gentoo-dev] Contribute many ebuilds at once Justin Lambert
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=200206091153.37850.georges@its.caltech.edu \
--to=georges@its.caltech.edu \
--cc=gentoo-dev@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