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

support for building packages that depend on other aur packages #4

Open
mariuszste opened this issue May 13, 2024 · 2 comments · May be fixed by #15
Open

support for building packages that depend on other aur packages #4

mariuszste opened this issue May 13, 2024 · 2 comments · May be fixed by #15

Comments

@mariuszste
Copy link

let's say I wanted to build adw-gtk-theme but it depends on adw-gtk3 that is only available in the AUR. I have adw-gtk3 added as a separate package and it built successfully but even after that adw-gtk3 still fails to build.

@VirtCode
Copy link
Owner

Yes, serene does not yet properly support dependencies, and does not resolve them itself.

Adding dependencies manually is however already sort-of supported. You can use set REPOSITORY_URL environment variable (see in the docs) to an URL to the server for build containers to access it for dependencies. The server will then add that URL as a Pacman repository to the build containers, so make sure you provide a URL which is valid for the containers, the easiest option would just be the normal URL to the server. The server can't determine the URL automatically, as it strongly depends on the actual deployment which is always a bit different.

I know that this solution is not ideal, and automatically adding dependencies from the AUR should definitely be supported. I'm planning to implement this some time in the future. For now, you'll have to add the dependencies manually, wait for them to build, then rebuild the dependents.

@dumbasPL
Copy link

dumbasPL commented May 14, 2024

You can use set REPOSITORY_URL environment variable

didn't notice that, thanks

Another thing worth mentioning is that packages that don't specify the version of the dependency expect the latest version of that dependency. This is especially true for -git packages using other -git packages. For fast-moving projects building one without updating the other often results in problems or even failed builds. So keeping the right update order would definitely be a thing to consider

edit: I'm @mariuszste btw ;)

@VirtCode VirtCode linked a pull request Oct 6, 2024 that will close this issue
8 tasks
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

Successfully merging a pull request may close this issue.

3 participants