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
Always get the PKGBUILD from trunk, not from repos #1843
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hi, I'm working on a PR for this.
|
Hey @tchaudhry91 , thanks for taking a look at this
|
@Jguer
I almost have this bit done. Will add a PR soon, can rework it if needed. The other option is to do a sparse checkout (but that still downloads the whole repository, just restricts the checkout from what I can tell) and will need a bunch of chained git commands instead of a single clone. In general it seems more hassle than required. If there is any other suggestion, let me know. |
There is an alternative fancy way that was implemented at some point but then reverted for some reason.
when the user tries to fetch the same package, you fetch/merge the upstream to the local cache (how yay does for AUR installs and link it again 🤷 try it out if you want |
Closing with mirror changes |
When I use yay on a package from ABS e.g.
yay -G haskell-glob
I'll getI'd be satisfied with a single PKGBUILD. How do I advice yay to ignore any other sources than trunk?
The behavior of
yay -Gp
is great, not giving me a tree of PKGBUILDs.Thanks in advance!
The text was updated successfully, but these errors were encountered: