| 1 |
On Mon, Feb 11, 2008 at 12:58:51PM +0100, Selckin wrote: |
| 2 |
> On Monday 11 February 2008 12:50:39 Brian Harring wrote: |
| 3 |
> > On Mon, Feb 11, 2008 at 09:48:01AM +0100, Vlastimil Babka wrote: |
| 4 |
> |
| 5 |
> > > Well, the idea that devs will have to revbump packages just for RDEPEND |
| 6 |
> > > version restrictions so that portage picks it freaks me :) |
| 7 |
> > |
| 8 |
> > Relying on the vdb is far saner then relying on the tree; so no, it's |
| 9 |
> > not particularly dangerous, the inverse (relying on the tree to have |
| 10 |
> > the same deps for vdb) is far worse imo. |
| 11 |
> > |
| 12 |
> > Solution to this is to reuse the existing update infrastructure, and |
| 13 |
> > add a new command into it that resets the depends/rdepends- haven't |
| 14 |
> > looked to see if older portage versions would behave well if they |
| 15 |
> > encounter an unknown command in profiles/updates/* however. |
| 16 |
> |
| 17 |
> This should really be [possible|done] without introducing yet another ugly and |
| 18 |
> very difficult to maintain update/* hack? |
| 19 |
|
| 20 |
Err... hack? Justify that statement please. |
| 21 |
|
| 22 |
Few things you might as well address also- |
| 23 |
1) update/* runs once per sync; alternatives (building a mapping, or |
| 24 |
forcing 2x metadata lookup via hitting up the tree for new metadata) |
| 25 |
can't really compete from a amoritized cost standpoint |
| 26 |
2) it's simple to maintain; exact atom (rev included), metadata key, |
| 27 |
metadata value. Can't realistically rewrite eapi-1 IUSE via it |
| 28 |
(default iuse can change the pkgs USE configuration), same for other |
| 29 |
build values (CHOST), but it's powerful, and simple. |
| 30 |
3) basic infrastructure is already there, so why not reuse it? |
| 31 |
|
| 32 |
~brian |
Archives