You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to deliver binaries to arch users, but how? How does packaging for arch work? How can we run our own repo for arch?
More context can be found in the goals for phase one.
We have the binaries that we want to distribute already compiled using oven, which outputs binaries which we can import into any packaging system.
What we want is to have a good system/workflow that will create/maintain an archlinux repository, with packages which are built using binaries provided by our oven.
An example of something similar done for apt/debian is available here.
Open questions:
Can an archlinux repository be easily pushed to and hosted on a webserver or s3 bucket?
Can the package manifests (PKGBUILD?) be templated similar to what's done here?
The text was updated successfully, but these errors were encountered:
We need to deliver binaries to arch users, but how? How does packaging for arch work? How can we run our own repo for arch?
More context can be found in the goals for phase one.
We have the binaries that we want to distribute already compiled using oven, which outputs binaries which we can import into any packaging system.
What we want is to have a good system/workflow that will create/maintain an archlinux repository, with packages which are built using binaries provided by our oven.
An example of something similar done for apt/debian is available here.
Open questions:
Can an archlinux repository be easily pushed to and hosted on a webserver or s3 bucket?
Can the package manifests (PKGBUILD?) be templated similar to what's done here?
The text was updated successfully, but these errors were encountered: