jobcomm/66-EOL/boot@-66serv
2024-02-22 13:37:09 +02:00
..
clean mv old s6 & 66 to jobcomm/66-EOL 2024-02-22 13:37:09 +02:00
deps mv old s6 & 66 to jobcomm/66-EOL 2024-02-22 13:37:09 +02:00
install mv old s6 & 66 to jobcomm/66-EOL 2024-02-22 13:37:09 +02:00
PKGBUILD mv old s6 & 66 to jobcomm/66-EOL 2024-02-22 13:37:09 +02:00
README.txt mv old s6 & 66 to jobcomm/66-EOL 2024-02-22 13:37:09 +02:00
time mv old s6 & 66 to jobcomm/66-EOL 2024-02-22 13:37:09 +02:00

  This pkg was created with the sole purpose of blocking Obarun's boot@-66serv replaced by our own
  boot-66serv.  If you were to install the authentic Obarun boot@-66serv you would break the system,
  unless you are saying goodbye to runit and want it permanently removed, thus switching to the
  full Obarun setup.  The reason we rebuild boot-66serv as our own is so the conflicting files
  with runit/runit-rc do not conflict and can be located separately, while the 4 power functions
  (reboot, poweroff, halt, shutdown) can operate either one of the two systems (runit s6).

  With the new version of 66 marked as -v2 a new bundle will be created and the previous setup
  with appropriate s6/skarnet dependencies will be marked 66-EOL.  The reason is that older 66
  2018-2023 will not build past a specific version of the skarnet stack bundle.  66-v2 (>=0.7.0.0)
  will build with skarnet's latest stack.  The functionality has changed so much that old users
  of obarun and joborun may not wish to shift at the time and relearn new software, or may wish
  to see bugs be ironed out (actively running with antiX and possibly void through mobinmob 
  repository) before they switch.  So we have decided to keep both.

  66-EOL group/bundle is the previous last version of 66 and s6 stacks
  66-v2  will carry the latest of 66 and s6/skarnet software

  You have a choice, a bit complicated but you do.
  All this software will from now be found in jobcomm repository (skarnet and obarun)