public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ragnar Hojland Espinosa <ragnar@linalco.com>
To: Frantz Dhin <fd@redspot.dk>
Cc: Klavs Klavsen <kl@vsen.dk>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Ebuilds not getting in :(
Date: Tue, 22 Apr 2003 15:09:55 +0200	[thread overview]
Message-ID: <20030422130954.GA23629@linalco.com> (raw)
In-Reply-To: <1051016369.4102.46.camel@entropy>

On Tue, Apr 22, 2003 at 02:59:30PM +0200, Frantz Dhin wrote:
> I feel your pain. Usually it takes several weeks before the ebuild
> updates I submit get accepted, and if at all, they usually they get
> accepted unaltered, which makes those weeks a waste of time.
> 
> I wish stuff could get into the unstable branch of Gentoo much easier. I
> would like to see some people with freedom to roam the tree accept
> things into unstable, and not have everything depend on if a branch
> maintainer has time or interest currently or not. Gentoo is supposed to
> be bleeding edge, but fact is that 30-35% of the packages in portage
> tree are at least one version behind. A too large share of developer
> resources external to the official gentoo developer team remains largely
> unused. 

I'll add a "me too", it feels like getting a patch inside the kernel and
I've given up on submitting new things until the (at least precieved)
situation improves.

It cant be testing what takes so long.. you just have to see the masked -
unmasked - ooops masked again dances or things that just dont compile
avi-xmms or broken sandbox ebuilds like metakit.

I'm not blaming anyone, it's just that I would had never expected would have
to use stow to keep up to date with gentoo. :/

-- 
Ragnar Hojland - Project Manager
Linalco "Especialistas Linux y en Software Libre"
http://www.linalco.com Tel: +34-91-5970074 Fax: +34-91-5970083

--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2003-04-22 13:17 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22  7:38 [gentoo-dev] Ebuilds not getting in :( Klavs Klavsen
2003-04-22 12:59 ` Frantz Dhin
2003-04-22 13:09   ` Ragnar Hojland Espinosa [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2003-04-24  0:32 Stroller
2003-04-24  3:50 ` George Shapovalov
2003-04-25  1:01 Stroller

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=20030422130954.GA23629@linalco.com \
    --to=ragnar@linalco.com \
    --cc=fd@redspot.dk \
    --cc=gentoo-dev@gentoo.org \
    --cc=kl@vsen.dk \
    /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