2
2
Fork
You've already forked 66-voidlinux
0

WIP: october_release #21

Draft
mobinmob wants to merge 3 commits from october_release into master
pull from: october_release
merge into: mobinmob:master
mobinmob:master
mobinmob:update-repo
mobinmob:user-services

This is a PR for the upcoming release

Goals

  • Deprecate /usr/bin/66 for /usr/bin/init-66. The next major release of 66 will provide an executable of the same name, so the project should be prepared for that. In that stage, renaming and retaining compatibility with a symlink should be enough.

    • Make the changes in boot-66serv
    • Change 66-void and
    • Test the transision...

  • Try to make the code that implements CHECK_CONFIGURATION better: fix bugs, sync with the updated 66boot scripts.

  • Revamp 66boot-initial-setup. The two helper scripts are solid, there is no reason not to call them during the initial setup. An alternative to this is to embed their functionality into the configure script for the boot@ module service. In any case the setup helper should be the single step needed to setup 66 in a new installation. Maybe implementing a clean function to remove generated trees should be added.

  • Take a crack at user services (again). The main issue is not the user-services themselves as 66 has pretty good support for them- but how to properly start and stop the user supervision tree on login and logout. I can use utlogd or turnstiled, or implement something that will work for both in the future. We 'll see...

## This is a PR for the upcoming release ### Goals - [ ] Deprecate `/usr/bin/66` for `/usr/bin/init-66`. The next major release of 66 will provide an executable of the same name, so the project should be prepared for that. In that stage, renaming and retaining compatibility with a symlink should be enough. - [x] Make the changes in boot-66serv - [x] Change 66-void and - [ ] Test the transision... - [ ] Try to make the code that implements CHECK_CONFIGURATION better: fix bugs, sync with the updated 66boot scripts. - [ ] Revamp `66boot-initial-setup`. The two helper scripts are solid, there is no reason not to call them during the initial setup. An alternative to this is to embed their functionality into the configure script for the boot@ module service. In any case the setup helper should be the single step needed to setup 66 in a new installation. Maybe implementing a clean function to remove generated trees should be added. - [ ] Take a crack at user services (again). The main issue is not the user-services themselves as 66 has pretty good support for them- but how to properly start and stop the user supervision tree on login and logout. I can use utlogd or turnstiled, or implement something that will work for both in the future. We 'll see...
This pull request is marked as a work in progress.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin october_release:october_release
git switch october_release

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff october_release
git switch october_release
git rebase master
git switch master
git merge --ff-only october_release
git switch october_release
git rebase master
git switch master
git merge --no-ff october_release
git switch master
git merge --squash october_release
git switch master
git merge --ff-only october_release
git switch master
git merge october_release
git push origin master
Sign in to join this conversation.
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
mobinmob/66-voidlinux!21
Reference in a new issue
mobinmob/66-voidlinux
No description provided.
Delete branch "october_release"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?