On Sat, Dec 17, 2005 at 09:21:45PM +0000, Ciaran McCreesh wrote: > On Sat, 17 Dec 2005 13:16:04 -0800 Zac Medico <[EMAIL PROTECTED]> wrote: > | Ciaran McCreesh wrote: > | > Well, that depends... If you have sys-apps/foo installed from the > | > gentoo-x86 repository, and the breakmygentoo repository issues a > | > news item about sys-apps/foo, should it be displayed? > | > | Well, probably not. Off hand, perhaps portageq could provide a query > | that returns some type of UUID for a package, such as a hash of the > | ebuild. That way, the hash from /var/db/pkg could be compared to the > | hash from the repo that has the news item. If the hashes don't > | match, then the news item is irrelevant. > > Now do you see why I don't want to touch multi repo support without a > proper specification describing how it'll work? :)
Multi repo support is actually pretty simple, and doesn't require yet another glep/spec/paperwork- it's been sitting in the saviour branch for as long as the domain class has existed (3+ months); stand alone repository support (matching within that repo) is a resolver thing, where we're at in saviour is normal PORTDIR capabilities for all specified repo's (standalone, overlay, or otherwise). It's not that bloody hard to get it working- all of the noise here is about further additions to it (which is fine, but kindly rememeber that fact), noise which I'd *rather* see resolved down the line. Why? Frankly, the majority of this is portage internal crap. Either extension of portageq api, or extension of atom syntax. Unique ID's per packages isn't a good idea offhand. What's needed for the comments above is the ability to search installed pkg db's for pkgs yielded from repo ID x. Enter the restriction subsystem. Add a repo level matching class, and you've got the search right there. Pretty simple, actually, and not requiring yet another glep for saviour. Back in the land of stable, here's how it should be done- portageq root atom [repo id] ex: portageq / sys-apps/foo "break my gentoo" simple mod. Lack of repo id is old rules, match anything and everything. This actually can be implemented *now* without requiring a bunch of handwaving about specs/gleps. Next issue? ~harring
pgp1aAP8lv5g0.pgp
Description: PGP signature
