1 |
On Tuesday 08 November 2005 01:06, Grant Goodyear wrote: |
2 |
> Jason Stubbs wrote: [Mon Nov 07 2005, 06:37:10AM CST] |
3 |
> > I'm really just against having it in emerge, especially with the current |
4 |
> > suggestion of portage just doing a little bit of maintenance work for |
5 |
> > external tools and nothing else. |
6 |
> |
7 |
> I'm not sure exactly what you're arguing here. Is it just that you |
8 |
> think that the news stuff should be a post-sync hook instead of being |
9 |
> triggered explicitly by "emerge"? |
10 |
|
11 |
I just wrote several paragraphs but that got me thinking so I deleted 'em. |
12 |
|
13 |
Ok. There's two levels of APIs here. There's the post-sync stuff which |
14 |
utilizes portage's API. There'll never be any need for portage to utilize the |
15 |
post-sync stuff that I can think of; if there is, that's a reason for putting |
16 |
it into portage. The second layer is between the post-sync stuff and the news |
17 |
readers. Here we have a problem. |
18 |
|
19 |
As Brian mentioned, multiple independent repositories will be supported and |
20 |
each should be allowed to have it's own independent set of news items. |
21 |
Multiple repositories will bring new (or completely replace) portage APIs. |
22 |
Hence, the post-sync stuff will have to accomodate. Yet, that's going to |
23 |
propogate into the post-sync component's API provided for the readers. |
24 |
|
25 |
Multiple independent repositories is just one change that we know is going to |
26 |
throw a spanner in the works. There'll likely be others. Hmm, I think I've |
27 |
just discovered what's unsettling about all this. We're being asked to throw |
28 |
something into portage that'll do XYZ to support external tools, yet we are |
29 |
guaranteed to break the XYZ. |
30 |
|
31 |
I guess I'd be happy with portage doing it and responsibility for |
32 |
compatibility staying with portage as long as we can decide/lead how the |
33 |
external tools gains access to the information. |
34 |
|
35 |
-- |
36 |
Jason Stubbs |
37 |
-- |
38 |
gentoo-dev@g.o mailing list |