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

Add top level archs key #178

Open
eddiezane opened this issue Nov 21, 2022 · 1 comment
Open

Add top level archs key #178

eddiezane opened this issue Nov 21, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@eddiezane
Copy link

We should add a top level archs: []string key similar to apko to avoid having to pass a flag.

@eddiezane eddiezane added the enhancement New feature or request label Nov 21, 2022
@kaniini
Copy link
Contributor

kaniini commented Nov 21, 2022

I don't think that this is something we should add to Melange. In contrast to apko, we want Melange to be opportunistic when building packages, constrained by the .package.target-architecture property.

Basically, I think archs does the wrong thing here, because it would imply that the melange .yaml files would need to be updated to allow Wolfi to be built on a new architecture, which seems like it would be a lot of work.

I assume the issue is relating to Melange wanting to do multi-arch builds by default? We can and should change that to --arch host.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants