You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
e.g. ebuild revision bumps would trigger the rebuild of their immediate revdeps automatically
If you modify the code for a package with a patch between version bumps, the revdeps will still need to be rebuilt. But, with the current setup, portage will not know this even if you make a revision bump for the ebuild. Using $PVR as the subslot instead of $PV would tell portage that the first level of revdeps need to be rebuilt, which could reduce some need to run haskell-updater between emerge failures.
The only downside I could see to this is if, for some reason, you needed to do a revision bump for the ebuild but did not touch the .cabal file, RDEPEND, or the code in any significant way. In this scenario, it would trigger a pointless rebuild of the first level of revdeps. However, this seems like it would be such an uncommon scenario that it wouldn't outweigh the usefulness of switching subslots to $PVR.
It would also mean people would need to be more thoughtful about why they are doing a revision bump for an ebuild.
::haskellIn reference to the gentoo-haskell overlayhackportIn reference to the hackport tool
1 participant
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Switch the default of
SLOT="0/${PV}"
to
SLOT="0/${PVR}"
e.g. ebuild revision bumps would trigger the rebuild of their immediate revdeps automatically
If you modify the code for a package with a patch between version bumps, the revdeps will still need to be rebuilt. But, with the current setup, portage will not know this even if you make a revision bump for the ebuild. Using
$PVR
as the subslot instead of$PV
would tell portage that the first level of revdeps need to be rebuilt, which could reduce some need to runhaskell-updater
betweenemerge
failures.The only downside I could see to this is if, for some reason, you needed to do a revision bump for the ebuild but did not touch the
.cabal
file,RDEPEND
, or the code in any significant way. In this scenario, it would trigger a pointless rebuild of the first level of revdeps. However, this seems like it would be such an uncommon scenario that it wouldn't outweigh the usefulness of switching subslots to$PVR
.It would also mean people would need to be more thoughtful about why they are doing a revision bump for an ebuild.
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions