-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RFE "rebuild-dependents" #50
Comments
That was a little hard to understand - re-reading, okay I think you talking about a dependency tree of packages. Maybe you could give a small concrete real example to make it clear: currently fbrnch only run one command at a time, though there is
Interesting idea - probably good to start from some example again. The thing is once you have built the package |
Basically, let's say we have LibA that is having a SOVERSION bump, the workflow there is to bump all dependent packages as if queried by |
Ah gotcha: so you want something like BTW rpmbuild-order can already generate a dependent tree list of packages, based on adjacent package checkouts. |
(Also just for reference there is |
(Also |
--rq
option to rebuild from branch to leaf
Yeah, but we might need to have these supported separately if we don't have write access to all dependencies. Or maybe we can assume #51 would take care of that. |
Just to have a tracker for the discussion on matrix. The feature request is to be able to
bump
,push
,build
, etc. starting from a branch update, e.g. a rust library, up to the leaf consumers (rust binary in the example). Would also be useful to create a file or outputting to text so that we can start restart from different points inbump
,push
,build
step without having to recompile the list each time.Another idea in the discussion was that tools like
fedrq wr
cannot be 100% accurate due to arch specific dependencies, but this could be complemented by scraping abuild.log
/root.log
. Maybe would require to store some database of dependencies locally, though no complaints if there was a hosted one or directly insidekoji
;)The text was updated successfully, but these errors were encountered: