public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: GLEP 42 (Was: Getting Important Updates To Users)
Date: Tue, 8 Nov 2005 01:44:12 +0900	[thread overview]
Message-ID: <200511080144.12179.jstubbs@gentoo.org> (raw)
In-Reply-To: <20051107160608.GA9318@bmb24.uth.tmc.edu>

On Tuesday 08 November 2005 01:06, Grant Goodyear wrote:
> Jason Stubbs wrote: [Mon Nov 07 2005, 06:37:10AM CST]
> > I'm really just against having it in emerge, especially with the current
> > suggestion of portage just doing a little bit of maintenance work for
> > external tools and nothing else.
>
> I'm not sure exactly what you're arguing here.  Is it just that you
> think that the news stuff should be a post-sync hook instead of being
> triggered explicitly by "emerge"?

I just wrote several paragraphs but that got me thinking so I deleted 'em.

Ok. There's two levels of APIs here. There's the post-sync stuff which 
utilizes portage's API. There'll never be any need for portage to utilize the 
post-sync stuff that I can think of; if there is, that's a reason for putting 
it into portage. The second layer is between the post-sync stuff and the news 
readers. Here we have a problem.

As Brian mentioned, multiple independent repositories will be supported and 
each should be allowed to have it's own independent set of news items. 
Multiple repositories will bring new (or completely replace) portage APIs. 
Hence, the post-sync stuff will have to accomodate. Yet, that's going to 
propogate into the post-sync component's API provided for the readers.

Multiple independent repositories is just one change that we know is going to 
throw a spanner in the works. There'll likely be others. Hmm, I think I've 
just discovered what's unsettling about all this. We're being asked to throw 
something into portage that'll do XYZ to support external tools, yet we are 
guaranteed to break the XYZ.

I guess I'd be happy with portage doing it and responsibility for 
compatibility staying with portage as long as we can decide/lead how the 
external tools gains access to the information.

--
Jason Stubbs
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-11-07 16:47 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-31 23:36 [gentoo-dev] GLEP 42 (Was: Getting Important Updates To Users) Chris White
2005-10-31 23:41 ` [gentoo-dev] " Dan Meltzer
2005-10-31 23:52   ` Dan Meltzer
2005-11-01  7:56     ` Wernfried Haas
2005-11-01 14:32       ` Chris Gianelloni
2005-11-01 19:32       ` Stuart Herbert
2005-11-01 19:51         ` Chris Gianelloni
2005-11-03 19:40           ` Stuart Herbert
2005-11-04  1:10             ` Nathan L. Adams
2005-11-04  8:22               ` Sami Näätänen
2005-11-04 14:26               ` Xavier Neys
2005-11-04 16:44                 ` Jason Stubbs
2005-11-04 18:53                   ` Alec Joseph Warner
2005-11-05  5:08                     ` Jason Stubbs
2005-11-05  5:34                       ` Alec Warner
2005-11-07 10:11                         ` Paul de Vrieze
2005-11-07 12:37                           ` Jason Stubbs
2005-11-07 16:06                             ` Grant Goodyear
2005-11-07 16:44                               ` Jason Stubbs [this message]
2005-11-07 16:43                             ` Stuart Herbert
2005-11-05  9:58                       ` [gentoo-dev] " Duncan
2005-11-05 12:54                       ` [gentoo-dev] " Michiel de Bruijne
2005-11-06 19:32                       ` R Hill
2005-11-01 19:53         ` Mike Williams
2005-10-31 23:46 ` [gentoo-dev] " Brian Harring
2005-11-01 10:51   ` Jason Stubbs
2005-11-01  0:42 ` Ciaran McCreesh

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=200511080144.12179.jstubbs@gentoo.org \
    --to=jstubbs@gentoo.org \
    --cc=gentoo-dev@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