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

How to build packages with vendor folder? #1291

Open
fwilhe2 opened this issue Jun 16, 2024 · 1 comment
Open

How to build packages with vendor folder? #1291

fwilhe2 opened this issue Jun 16, 2024 · 1 comment

Comments

@fwilhe2
Copy link

fwilhe2 commented Jun 16, 2024

Hi, I'm looking into how wolfi is built and try to rebuild a few core packages.

I've looked into the wolfi git repo and I see it uses wolfictl as a wrapper for melange. I'd like to use 'plain' melange. I've rebuilt a few packages successfully, but so far I don't know how to handle cases of packages that use a vendor dir like wolfi-baselayout or glibc.

The issue is that when trying to build I get an error like cp: can't stat 'vendor/hello.txt': No such file or directory. I assume I'd need to mount this directory into the build container somehow, but I have not found an option in melange to do that. Also I found no example or documentation on this issue.

I have put a reduced example up here https://github.com/fwilhe2/melange-vendor-test

Please help me understand: Can melange do this, or do I need to use wolfictl?

Btw: Kudos, great work overall. melange, apko, wolfi are pretty awesome projects.

@fwilhe2
Copy link
Author

fwilhe2 commented Jun 22, 2024

Ok, it seems like pwd is mounted automatically, so the solution seems to be to prefix the package-directory like in this commit.

This seems to mean that wolfi files need to be edited to work with plain melange, unless I still miss something. Leaving the ticket open in case some one has a more elegant solution, but feel free to close if this is intended.

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

No branches or pull requests

1 participant