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
Re-add --batchinstall and fix dep issues #1053
Conversation
Can you just point me out what was the issue with the deps? |
DepOrder is built from DepPool. And as it builds it drains the dep pool. Meaning that |
Fair enough, happens. What would you say are the biggest challenges in extracting it to its own package so it doesn't depend on yay runtime information? |
Also missing is manpages and completion data for this |
I wouldn't really say there's any challenges, just a lot to write. |
I know what you mean, just setting up all of the CI/"CD" pipeline has been hammering away at everything. I would leave this PR unmerged until pacman 5.2 has passed (which I hope is soon). Meanwhile I've set go-alpm to check and build when pacman enters testing and also to compile against pacman-git once a week and on branches named |
6135458
to
90c0099
Compare
90c0099
to
4d91acc
Compare
What did I say an hour ago 🤣 ? |
My message was the last time I checked the thread, whoops. |
I just don't want to deal with the extra conflicts really. |
Fine by me, no issue. I was planning on testing automatic releasing on master branch on these last commits but I'll have to implement release-branch releasing before, just moves the cycle a bit back. |
No description provided.