Skip to content
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: Add the ability to specify an "anchor" package, such that all rebuilds are listed after the anchor package #10

Open
ermo opened this issue Apr 19, 2024 · 0 comments

Comments

@ermo
Copy link
Contributor

ermo commented Apr 19, 2024

Context:

Reilly Brogan
Oh I just noticed that cifs-utils and notmuch are out of order
That's fine I'll bump them again after the stack is done
ermo
wait, what?
Reilly Brogan
https://github.com/getsolus/packages/pull/2282/commits
Note that cifs-utils and notmuch are before samba
build-pr builds in commit order
ermo
they're not out of order
they just depend on talloc only
(this is the exact order autobuild sussed out after doing a full-tree analysis w/DAG and stable topological sort)
Reilly Brogan
Ah okay
ermo
that said, I can see why you'd flag it, but it's actually correct if you look at it from the perspective of talloc alone.
(if that makes sense)
i.e. they're fully independent of the rest of the stack =)
though you did have me check that I wasn't misremembering xD
Reilly Brogan
I probably still would have adjusted the build order so they went after the "stack", but that's just me
I like rebuilds to be after all the updates
ermo
No, I get it.
I'm just trying to think of a way to have autobuild do that on its own
it'd likely need a way for the user to specify an "anchor" package
i.e. "any rebuilds should only happen after the anchor package is in"
meaning that, if I specify autobuild query src:packages/ samba talloc tevent tdb ldb --anchor=samba, it'd produce the order you are used to seeing/using
@GZGavinZhao : ^?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant