| Summary: | Add ability to use sets in package.keywords | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
| Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | CC: | darkside, esigra, wschlich |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 144480, 376695, 204493 | ||
21:41 < Betelgeuse> zmedico: ping 21:41 < zmedico> Betelgeuse: pong 21:42 < Betelgeuse> zmedico: What do you think about a package.keywords atom that would automatically unmask the needed stuff. 21:42 < Betelgeuse> I wast thinking it would go like this: 21:42 < Betelgeuse> 1. try stable 21:42 < Betelgeuse> 2. try latest ~arch 21:42 < Betelgeuse> then for installed stuff only update if the ebuild is gone 21:42 < Betelgeuse> and then only the oldest ~arch 21:43 < astinus> Betelgeuse: the oldest ~arch could be older than stable. 21:43 < Betelgeuse> astinus: then use stable 21:51 < astinus> Betelgeuse: sounds like a neat idea, but I'd be worried about the "oldest arch" bit. If you're auto-unmasking, the *oldest* arch may be an issue, ie: if you have app-foo/foobar-1.0.1-r1 as the *oldest* and 1.0.1-r7 as teh newest, chances are there are fixes in there you'd want 21:51 < zmedico> Betelgeuse: I suppose that sort of thing could be represented as a package set. It's a bit simpler if the set can just accept keywords on all deep dependencies. 21:52 < Betelgeuse> zmedico: Yeah sets would help 21:52 < Betelgeuse> zmedico: I was unmasking xorg-server-1.5 earlier today 21:53 < zmedico> seems like it will require backtracking to implement 21:55 < zmedico> or maybe just a lookahead mechanism would work 21:56 < zmedico> I guess you'd sort of build a mini graph to determine the set 21:56 < zmedico> prior to building the whole graph 21:57 < zmedico> it's similar to how PROPERTIES=set would be implemented 22:01 < zmedico> seems like fun 22:03 < Betelgeuse> zmedico: Even the ability of people to list pkgs to file and then apply keywords to all of them would help 22:03 < Betelgeuse> zmedico: when set files come with the tree 22:03 < Betelgeuse> zmedico: I guess Portage only misses the latter part 22:04 < zmedico> yeah, that's a lot simpler to implement 22:04 < Betelgeuse> could just start with that and then go further 22:04 < zmedico> good idea