add initial alpine packaging #814

Open
magmaus3 wants to merge 3 commits from magmaus3/continuwuity:alpine-packaging into main
First-time contributor

this PR adds the initial apkbuild for building the alpine package for the current release
notes:

  • to build the package, you must use the cargo version from the edge branch (by building on edge or by installing it manually), as the currently included version in v3.21 doesn't support rust 2024 edition stuff
  • building from git requires some work (abuild supports snapshots for getting the release from git, but the version number would remain unchanged)
  • the apkbuild doesn't include any packaging tests (as i don't know what to include)
this PR adds the initial apkbuild for building the alpine package for the current release notes: - to build the package, you must use the cargo version from the edge branch (by building on edge or by installing it manually), as the currently included version in v3.21 doesn't support rust 2024 edition stuff - building from git requires some work (abuild supports snapshots for getting the release from git, but the version number would remain unchanged) - the apkbuild doesn't include any packaging tests (as i don't know what to include)
nex 2025-05-03 15:23:14 +00:00
magmaus3 force-pushed alpine-packaging from 548432665d to 80e8900f04 2025-05-04 11:22:58 +00:00 Compare
magmaus3 changed title from add initial alpine alpine packaging to add initial alpine packaging 2025-05-04 11:24:02 +00:00
Owner

This looks pretty good to me so far, although I don't know much about Alpine or packaging.

Would it be possible to get some more automation in here? In particular keeping the source up-to-date in the package buildfile, and building the package in CI?

This looks pretty good to me so far, although I don't know much about Alpine or packaging. Would it be possible to get some more automation in here? In particular keeping the source up-to-date in the package buildfile, and building the package in CI?
Author
First-time contributor

Would it be possible to get some more automation in here? In particular keeping the source up-to-date in the package buildfile, and building the package in CI?

sure, i might try setting it up later :3

the aforementioned git related stuff could be automated there (mostly by replacing the source and version)

> Would it be possible to get some more automation in here? In particular keeping the source up-to-date in the package buildfile, and building the package in CI? sure, i might try setting it up later :3 the aforementioned git related stuff could be automated there (mostly by replacing the source and version)
Owner

Is this waiting on anything?

Is this waiting on anything?
Owner

The only thing was potential automation, because this is entirely manual right now, but it that can come later

The only thing was potential automation, because this is entirely manual right now, but it that can come later
Author
First-time contributor

@nex wrote in #814 (comment):

Is this waiting on anything?

no, i didn't really have time to work on the ci part (+ partially forgot to do it), sorry for the wait

as a note, i did some of the ci stuff on my forgejo instance, and it should build the release for the arch used by the runner (i haven't finished testing that part yet),
but the upload part isn't there yet (either one could upload the package from ~/packages as an artifact, or set up uploading to a http server (to set up a repo directly).

sorry for the issue, i'll try to work on it when i find time for that (i could do it in a separate PR if needed)

@nex wrote in https://forgejo.ellis.link/continuwuation/continuwuity/pulls/814#issuecomment-16033: > Is this waiting on anything? no, i didn't really have time to work on the ci part (+ partially forgot to do it), sorry for the wait as a note, i did some of the ci stuff on my [forgejo instance](https://git.magmaus3.eu.org/magmaus3/continuwuity), and it should build the release for the arch used by the runner (i haven't finished testing that part yet), but the upload part isn't there yet (either one could upload the package from `~/packages` as an artifact, or set up uploading to a http server (to set up a repo directly). sorry for the issue, i'll try to work on it when i find time for that (i could do it in a separate PR if needed)
magmaus3 force-pushed alpine-packaging from 80e8900f04 to 73854e42a3 2025-05-26 17:47:30 +00:00 Compare
Owner

Forgejo has a built-in Alpine package registry (https://forgejo.org/docs/latest/user/packages/alpine/) so you could use that

Forgejo has a built-in Alpine package registry (https://forgejo.org/docs/latest/user/packages/alpine/) so you could use that
Owner

And don't worry about the wait, no pressure haha

And don't worry about the wait, no pressure haha
Owner

What Jade said; we're all strapped for time, no pressure. Just wanted to make sure you weren't blocked on anything :)

What Jade said; we're all strapped for time, no pressure. Just wanted to make sure you weren't blocked on anything :)
Author
First-time contributor

@Jade wrote in #814 (comment):

Forgejo has a built-in Alpine package registry (https://forgejo.org/docs/latest/user/packages/alpine/) so you could use that

ah, didn't know about it, thanks :3

@Jade wrote in https://forgejo.ellis.link/continuwuation/continuwuity/pulls/814#issuecomment-16038: > Forgejo has a built-in Alpine package registry (https://forgejo.org/docs/latest/user/packages/alpine/) so you could use that ah, didn't know about it, thanks :3
Some checks failed
Documentation / Build and Deploy Documentation (pull_request) Has been cancelled
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u alpine-packaging:magmaus3-alpine-packaging
git checkout magmaus3-alpine-packaging

Merge

Merge the changes and update on Forgejo.
git checkout main
git merge --no-ff magmaus3-alpine-packaging
git checkout magmaus3-alpine-packaging
git rebase main
git checkout main
git merge --ff-only magmaus3-alpine-packaging
git checkout magmaus3-alpine-packaging
git rebase main
git checkout main
git merge --no-ff magmaus3-alpine-packaging
git checkout main
git merge --squash magmaus3-alpine-packaging
git checkout main
git merge --ff-only magmaus3-alpine-packaging
git checkout main
git merge magmaus3-alpine-packaging
git push origin main
Sign in to join this conversation.
No reviewers
continuwuation/Owners
No milestone
No project
No assignees
3 participants
Notifications
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: continuwuation/continuwuity#814
No description provided.