-
-
Notifications
You must be signed in to change notification settings - Fork 349
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
Request: Equivalent of Yaourt's Sync Option: --build #5
Comments
Is this feature still being considered? |
I'm not actively working on it or have plans do but its possible it may get implemented at some point. |
Same here, not working on it but willing to accept the feature getting integrated |
Sad, that this feature is still not implemented. I think it should be somewhat easy to implement since it's basically just a different source for the PKGBUILD etc. files :) |
I haven't contributed to Yay before, but I'd really like to have this working. Does anyone have time to write out the basic steps someone might take to start working on this feature? |
I might have some time but doing it would take too long for me alone. If somebody would join me I think we could implement it. |
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. |
Has this feature actually been implemented? I don't think the issue should be closed until it is, unless a decision has been made specifically to not implement the feature. |
I'd say its more about who will implement it rather than discussing whether to implement it or not. If the idea was rejected, @Jguer would've said so earlier. I'd really like to see this feature inside yay but It'd be a lot of work to implement it properly. If someone (or a group of people) were saying to implement it, I guess this issue will be opened again. |
Thanks for closing this automatically, I support the idea that inactive issues should be closed to make space for the active ones. ❤️ I'm mostly incapable of moderation and tried to turn Arch into a source-based distro like Gentoo. I've given up, and would suggest that anyone else with similar ideas does the same: Arch doesn't package applications to avoid circular references, so it's very common to see package that depend on themselves (e.g. Vala depends on Vala). Building from source is fine for some use-cases, but if anyone has similar ideas about turning Arch into a source-based distro I hope you'll email me first so I can talk you out of it. |
I almost created a new issue but decided to search first and found this ancient request. I hope @Jguer is still considering it. My use case is that I am using the unofficial Arch Power distro for IBM POWER processors. This is a small, experimental distro, and its maintainers only provide a subset of packages. However, most packages will compile just fine from the AUR and ABS. This requires manual dependency resolution for any packages not maintained by the distro or not available in the AUR. If yay could resolve any unavailable dependencies from the ABS it would be a huge benefit for us niche users. edit: And I just realized this was closed four years ago 😅. Whoops. I will open a new issue instead. |
The text was updated successfully, but these errors were encountered: