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

Unable to resolve dependencies for split packages #40

Open
pbrisbin opened this issue Oct 20, 2015 · 0 comments
Open

Unable to resolve dependencies for split packages #40

pbrisbin opened this issue Oct 20, 2015 · 0 comments

Comments

@pbrisbin
Copy link
Owner

(See #39 for example case)

Scenario

  • Given some package p which is a split package for building (at least) q
  • Given p (and therefore q) has an AUR dependency x
  • Given the user invokes aurget -Sy --deps q

What happens

  • Aurget attempts to download the PKGBUILD for q to resolve dependencies
  • This PKGBUILD does not exist (only the PKGBUILD for p does)
  • Aurget considers a missing PKGBUILD as "no dependencies" and continues with the build
  • The build will fail when makepkg can't satisfy x (because it's in the AUR)

What should happen

  • Aurget should download p's PKGBUILD and use it to resolve dependencies
  • Aurget should find x and add it as a dependency target
  • Building should succeed

Proposed fixes

  • I wonder if not finding the PKGBUILD should blow up
  • We probably need to hit the AUR API to know that we need p's PKGBUILD to resolve dependencies for q

Workaround

In general, manually resolve the dependencies:

aurget -Sy --deps --asdep x
aurget -Sy --deps q

Note that

aurget -Sy --deps x q

Will also work, but x will be installed explicitly and therefore would not be removed automatically with pacman -Rsn q, or be show in pacman -Qdt output when/if q were uninstalled.

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

No branches or pull requests

1 participant