Project

General

Profile

Housekeeping #3290

[nonsystemd] OpenRC init scripts repackaging

Megver83 - about 2 months ago - . Updated about 1 month ago.

Status:
in progress
Priority:
discussion
Assignee:
% Done:

0%


Description

Our OpenRC init scripts PKGBUILDs are based on the deprecated Arch OpenRC and Manjaro OpenRC projects. Although they mostly work, they are outdated and it is better split them in separated PKGBUILDs, like Artix does, rather than creating big PKGBUILDs with split packages.

I'm opening this issue to keep track of this (kinda) long task, which I believe I'll do everything by myself after upgrading the super old kernels.

Roadmap (Step 1):
  • Separate init scripts from packages that integrate them (e.g. dbus, networkmanager)
  • Import Artix initscripts PKGBUILDs
  • Remove split packages
After concluding this task (Step 2):
  • Package s6
  • Package runit

My plan for [nonsystemd] is to closely follow Artix, I think they do a very good job at maintaining PKGBUILDs for alternative inits and most of the work I've done in [nonsystemd] is based on it

I'm assigning the "discussion" priority to discuss the possibility of importing Artix packages (at least the init scripts) directly to [nonsystemd]

History

#1

Updated by Zuss about 2 months ago

I do like the way Artix has done it as well, it's a lot more cleaner and organized.
I'll start with moving the [pcr] packages into [nonsystemd] and open up a PR on the Pagure repo to keep track of what has been done

#2

Updated by Zuss about 1 month ago

Just opened up a PR (#53) with all the packages I've migrated so far.

I've come into issues with a few packages so far with regards to the Arch PKGBUILD's referencing systemd.

[at] and [cronie] have a hook file which tries to restart the service with systemd. Trying to install the OpenRC hook file over it doesn't work.

The upstream [fcron] Arch package within the .install file tries to execute "systemd-sysusers fcron" but otherwise it launches the service just fine. (Haven't tested it beyond starting the service)

Is there any particular way you want to deal with these packages?

#3

Updated by Zuss about 1 month ago

82 packages have been added to the [nonsystemd] repo bar a few which need to be discussed. They can be seen at the PR mentioned above.

Packages that have issues/haven't been migrated:

at:         Arch hook file references systemd
autofs:     Package has been moved to the AUR (32bit package exists on Parabola)
cronie:     Arch hook file references systemd
fcron:      Arch .install file references systemd-sysusers
opensmtpd:  Arch .install file references systemd-sysusers
polipo:     Package no longer exists (Arch + AUR) but 32bit package in Parabola repos
salt:       Requires python-systemd
sane:       Crashes on startup: Socket operation on non-socket
shorewall:  Package has been moved to the AUR (32bit package exists on Parabola)
wicd:       Package no longer exists
x2goserver: Package has been moved to the AUR (32bit package exists on Parabola)

fcron and opensmtpd have been pushed through in the commits because they still seemed to work fine even with the systemd-sysusers error showing up, but they're probably packages that need dealing with as well.
Not sure why sane isn't starting either and couldn't figure out how to fix it.

Other than that, just need some input on what to do with the packages listed above.

Also available in: Atom PDF