Multi-arch package building #35

New Issue

Closed

opened 2022-01-18 21:36:04 +01:00 by Jef Roosens · 2 comments

Jef Roosens commented 2022-01-18 21:36:04 +01:00

Owner

If we could detect what OS a runner is running on, we could allow for building packages on various architectures (might be useful when using Arch on a Pi)

If we could detect what OS a runner is running on, we could allow for building packages on various architectures (might be useful when using Arch on a Pi)

Jef Roosens added the

enhancement

label 2022-01-18 21:36:04 +01:00

Jef Roosens changed title from Multi-arch packages support to Multi-arch package building 2022-02-02 11:47:48 +01:00

Jef Roosens added

idea

and removed

enhancement

labels 2022-02-13 15:31:00 +01:00

Jef Roosens added this to the 0.2.0 milestone 2022-04-07 09:18:46 +02:00

Jef Roosens commented 2022-04-07 09:20:28 +02:00

Poster

Owner

Because we'll be adding support for multi-arch repos in 0.2.0 anyways, this PR can get added as well. It might be interesting to research https://github.com/Menci/docker-archlinuxarm. This repo builds an arm64 & amd64 compatible archlinux image every night, which might be more practical to use than the standard archlinux image. It would however be safer to build them ourselves.

Because we'll be adding support for multi-arch repos in 0.2.0 anyways, this PR can get added as well. It might be interesting to research https://github.com/Menci/docker-archlinuxarm. This repo builds an arm64 & amd64 compatible archlinux image every night, which might be more practical to use than the standard archlinux image. It would however be safer to build them ourselves.

Jef Roosens commented 2022-04-08 14:39:41 +02:00

Poster

Owner

I added a setting to select which base image to use for a builder. I'll put a notice in the docs about this specific image, but that's all that needs to be done.

I added a setting to select which base image to use for a builder. I'll put a notice in the docs about this specific image, but that's all that needs to be done.

Jef Roosens closed this issue 2022-04-11 09:33:58 +02:00

This repo is archived. You cannot comment on issues.

No Branch/Tag Specified

Branches Tags

renovate/nokogiri-1.x

renovate/redcarpet-3.x

renovate/busybox-1.x

dev

main

release-0.6.0

0.6.0

0.5.0

0.5.0-rc.2

0.5.0-rc.1

0.4.0

0.3.0

0.3.0-rc.1

0.3.0-alpha.2

0.3.0-alpha.1

0.2.0

0.1.0

0.1.0-rc1

Labels

Clear labels   

Roadmap

Tracking issue for a larger task   

V

This issue is blocked by a V issue   

bug

Something is not working   

docs

Something to add to the documentation   

duplicate

This issue or pull request already exists   

enhancement

New feature   

good first issue

A good issue to start out with as a new contributor   

help wanted

Need some help   

idea

Issue for brainstorming a new idea   

invalid

Something is wrong   

question

More information is needed   

wontfix

This won't be fixed

  

Idea

Issue for brainstorming a new idea   

Roadmap

Tracking issue for a larger task   

bug

Something is not working   

duplicate

This issue or pull request already exists   

enhancement

New feature   

help wanted

Need some help   

invalid

Something is wrong   

question

More information is needed   

wontfix

This won't be fixed

No Label

Roadmap

V

bug

docs

duplicate

enhancement

good first issue

help wanted

idea

invalid

question

wontfix

Idea

Roadmap

bug

duplicate

enhancement

help wanted

invalid

question

wontfix

Milestone

Clear milestone

No items

No Milestone

0.2.0

Projects

Clear projects

No project

Assignees

Clear assignees

No Assignees

1 Participants

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vieter-v/vieter#35

There is no content yet.