public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: George Shapovalov <george@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuilds not getting in :(
Date: Wed, 23 Apr 2003 20:50:28 -0700	[thread overview]
Message-ID: <200304232050.28318.george@gentoo.org> (raw)
In-Reply-To: <49401.192.168.1.70.1051144378.squirrel@gentoo.lan>

On Wednesday 23 April 2003 17:32, Stroller wrote:
> On Tuesday, April 22, 2003, at 02:17  pm, Peter Ruskin wrote:
> > On Tuesday 22 Apr 2003 13:59, Frantz Dhin wrote:
> >> ... maybe we could make a
> >> new keyword? x86 for stable, ~x86 for unstable, and ^x86 for lunatic?
> > I couldn't agree more!
> Me, either! I don't know that "lunatic" is the best word, but it seems
> to me that an additional hierarchy [0] allows for a framework more
> flexible & extensible for end lusers. As I understand it builds with the
Unfortunately this is not that easy. Just accepting ebuild in and letting them 
rot is either a dead-end or a security breach (or both :). Think about what 
to do with them as they get tested and about possible submisisons overlappig 
already existing *core* ebuilds, yek.. ).

Please take a look at #1523 to see what's on the plate ;). Only bear in mind, 
that almost everything in that proposal was written before even KEYWORDS came 
around, so terminology and, well, pretty much all implementation details are 
out of date by now.. However the general structure still applies and contains 
few more (relatively minor as compared to KEYWORDS and gentoo-stats/stable 
(AKA voting system in that text)) additions.

I am afraid it is still too early to talk about implementation details (except 
may be starategic things), as we need to complete the internal restructuring 
we are attempting right now (and convincing more devs, that we need this kind 
of thing implemented, as this was not universally accepted yet :)). But the 
logical structure can and IMHO should be discussed.

One thing I can already tell for sure, is that security of any such system 
will be an issue of paramount importance if this kind of thing to be 
accepted. Namely guarantying by implementation that some unassisted 
submission does not wreak a havoc on user system no mater what profile that 
user runs (possibly except "definitely-unstable-you've-been-warned" or 
whatever it's going to be called :)).
There are of course more issues of lesser but still major importance to be 
considered, such as efficiency on all levels...

> [1] Am I correctly appreviating "^86, ^PPC or whatever" here? I'm not
> doing too well tonight.
That'd work, especially if you spell appreviate as abbreviate and make ppc 
lowercase ;).

George

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-24  3:50 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-24  0:32 [gentoo-dev] Ebuilds not getting in :( Stroller
2003-04-24  3:50 ` George Shapovalov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-25  1:01 Stroller
2003-04-22  7:38 Klavs Klavsen
2003-04-22 12:59 ` Frantz Dhin
2003-04-22 13:09   ` Ragnar Hojland Espinosa
2003-04-22 13:17   ` Peter Ruskin
2003-04-22 13:24     ` FRLinux
2003-04-22 13:30       ` Klavs Klavsen
2003-04-22 13:50     ` Ragnar Hojland Espinosa
2003-04-22 14:05       ` Jon Portnoy
2003-04-22 16:18     ` Brad Laue
2003-04-23 15:25     ` Peter Ruskin
2003-04-23 18:18       ` Paul de Vrieze
2003-04-22 14:26   ` Dan Armak
2003-04-22 14:57     ` Peter Ruskin
2003-04-22 15:40       ` Tony Clark
2003-04-22 15:45         ` Ragnar Hojland Espinosa
2003-04-22 16:00       ` Klavs Klavsen
2003-04-22 16:14         ` Tony Clark
2003-04-22 16:23           ` William Hubbs
2003-04-22 16:59         ` Jon Portnoy
2003-04-22 17:55           ` Mark Bainter
2003-04-22 18:00             ` Klavs Klavsen
2003-04-22 18:06               ` Jon Portnoy
2003-04-25 16:58     ` Brad Laue
2003-04-25 17:31       ` foser
2003-04-25 21:03         ` Brad Laue
2003-04-26  0:38           ` foser
2003-04-22 19:11   ` Fredrik Jagenheim
2003-04-22 23:53     ` Fernand Albarracin
2003-04-22 15:57 ` Brian Jackson
2003-04-22 22:07   ` Brian Jackson
2003-04-22 22:36     ` Robin H.Johnson
2003-04-23  7:43       ` Mark Gordon
2003-04-23 12:46         ` Jon Portnoy
     [not found]       ` <20030425134659.I30851@leftmind.net>
2003-04-25 21:59         ` Robin H.Johnson
2003-04-23  2:56     ` Brian Jackson
2003-04-23 15:27       ` Peter Fein
2003-04-23 15:38         ` Grant Goodyear
2003-04-24 18:20       ` Brian Jackson
2003-04-23  5:47   ` Thomas Arnhold

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=200304232050.28318.george@gentoo.org \
    --to=george@gentoo.org \
    --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