Luca Barbato wrote: > Alin Nastac wrote: >> I reckon this could be solved by yet another *DEPEND variable. The only >> atoms accepted by this variable would be "CATEGORY/PN". Every time when >> a package gets updated from PV1 to PV2 (distinct versions, revisions >> will not count), portage will automatically re-emerge those packages >> that depend on it. >> >> Thoughts? >> > > It would require revdep resolution on emerge... how painful would be? > I don't know anything about portage intricacies, but I guess it would be fairly easy to have a map of CATEGORY1/PN1 -> CATEGORY2/PN2 key-values, where package 2 depends on package 1 (package 2 is the one that defines the xxxDEPEND variable). In order to add such (key, value) in the map the following assumptions must be satisfied: - package 2 must be installed (mandatory) - package 1 must be a direct or indirect RDEPEND dependency of the package 2 (optional).
signature.asc
Description: OpenPGP digital signature
