Hello dear community,

Hyperbola is done by the community for the community, so this thread is for sure a noted help for everyone interested in packaging and sharing the results later. So if you find sources by yourself post them within here. I start with one helper being useful: https://github.com/OpenRC/openrc/blob/m … t-guide.md

Appreciate the link.

Btw, I keep forgetting to ask Luke, about something specific.

https://unix.stackexchange.com/question … a-pkgbuild
https://wiki.archlinux.org/title/PKGBUILD
https://wiki.archlinux.org/title/Creating_packages

I see that in my Hyperbola install, I can look at PKGBUILD templates with all the variables under /usr/share/pacman:
PKGBUILD.proto : this is the most commonly used template, and you would copy the release version number from the source
PKGBUILD-split.proto : this one is used only when the package is a split package (rare and probably never gonna happen in Hyperbola)
PKGBUILD-vcs.proto : this one is used only when the source is only available on a version control system like git, in which case all version numbers must be whole integers and not decimal points.
proto.install : is a default template for a post-install script, if the source uses one

In order to package, then, we would consult the package source for the functions we need to include in the PKGBUILD.

For good hygiene, we should create a chroot, follow the compilation and install process and then create a PKGBUILD from that. If the install process fails, we should delete the chroot and start over with a clean one until the package compiles and installs successfully, Then PKGBUILD must draw from a successful install. Then, create a separate chroot for making a nice Hyperbola package, and using the PKGBUILD follow the Hyperbola install process. If it fails, delete chroot and make a fresh one, correct the PKGBUILD file, and try again. Sooner or later, the package will build, and so long as the Hyperbola Packaging Guidelines are followed you will have created a package that can be included.

The entire website is down! Will I be needing this?

The PKGBUILD is the central file needed, for the mentioned package there are more besides the source-file: Another local patchset and the service-definitions being used later on. When downloaded within a folder, you can use the command makepkg for a local tryout (outside of a clean chroot). When dependencies are missing: makepkg -s

When further packages are missed you should for sure add them throughout the same workflow. This is only the first run for starting. I have mentioned the chroot-environment: This would be the next step. Here to read more about: https://forums.hyperbola.info/viewtopic.php?id=632

I know what the standards are, but:
What are the steps I need to take to follow the security and privacy guidelines?
Does it matter if I use chroot, firejail, bubblewrap or containers?

Should I follow the Parabola workflows? -->
https://wiki.parabola.nu/Package_maintainer_guide
https://wiki.parabola.nu/How_to_help
https://wiki.parabola.nu/Category:Packaging
https://wiki.parabola.nu/Creating_-libre_packages
https://wiki.archlinux.org/title/Develo … ean_Chroot
https://wiki.parabola.nu/Libremakepkg
https://wiki.parabola.nu/PKGBUILD

I tend to do well if there are some instructiions. So if anyone can recommend some links to guides to make packages on Hyperbola in a way that follows the standards, please post them!

I plan on learning to do the good practices well for myself before taking on the further responsibility.

Hyperbola is done by the community for the community, so this thread is for sure a noted help for everyone interested in packaging and sharing the results later. So if you find sources by yourself post them within here. I start with one helper being useful: https://github.com/OpenRC/openrc/blob/m … t-guide.md