From: mobinmob <mobinmob@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: s6/66 integration (previously boot-66serv )
Date: Wed, 07 Feb 2024 18:37:16 +0100 [thread overview]
Message-ID: <20240207173717.A03AB21131@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45578@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 2235 bytes --]
New comment by mobinmob on void-packages repository
https://github.com/void-linux/void-packages/pull/45578#issuecomment-1932552536
Comment:
> > preprod for 66 in not a final release, it is an rc (I know, I am the one who proposed beta etc releases to @Obarun ).I am waiting for the final release and (more) testing. Going from 0.6.0.x to 0.7.0.x is a major change and I didn't have the time yet to test as much as I like.
>
> That is why I created a draft PR for testing. Building looks fine now and of course we would need to wait for `66` to have a stable `0.7.0.0` available. But seeing check marks already is a good sign for testing the packages.
I already have a PR (https://github.com/void-linux/void-packages/pull/47177), since the 66 has to be upgraded (breaking changes from the skarnet stack), but have not yet pushed all needed programs. Maybe your approach is better :)
> > You are ofc free to create another PR and the devs to merge whatever they want.
>
> I would like to go further together with you if you don't mind. If you've other plans I don't want to get into your way.
>
I will gladly work with you to advance **66** in voidlinux, please sent an email - github comments is not the ideal place for collaboration beyond reviews :)
> I'm not yet using s6 and with the PR on the way and all green. I would now test the PR versions and try out s6 and the other packages as well.
The current 66 release is stable and well-tested. See the links in the first post on how to setup a system with this. 0.7.0.0 is quite different - my current working branch for boot-66serv voidlinux is void-linux-dev: https://git.obarun.org/mobinmob/boot-66serv/-/tree/voidlinux-dev?ref_type=heads
What needs to be done for this is:
- revamp the 66boot-* utils to use the new 66 subcommands (not really diffcult) - developed in [codeberg](https://codeberg.org/mobinmob/66-voidlinux)
- revise the services in [voidlinux-66-services](https://github.com/mobinmob/void-66-services) for the new format (easy)
- revice the documentation (straightforward)
- test and then test some more :P
I plan to do most of the above if not all (well testing will continue...) in the following days and the weekend...
next prev parent reply other threads:[~2024-02-07 17:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 14:23 [PR PATCH] s6/66 integration (previously boot-66) mobinmob
2023-08-13 14:34 ` mobinmob
2023-10-01 17:12 ` s6/66 integration (previously boot-66serv ) mobinmob
2023-12-31 1:47 ` github-actions
2024-01-01 10:30 ` mobinmob
2024-02-07 16:52 ` dataCobra
2024-02-07 17:01 ` mobinmob
2024-02-07 17:05 ` mobinmob
2024-02-07 17:11 ` dataCobra
2024-02-07 17:37 ` mobinmob [this message]
2024-02-07 17:38 ` mobinmob
2024-02-17 14:42 ` dataCobra
2024-02-17 14:44 ` dataCobra
2024-02-17 14:50 ` dataCobra
2024-02-17 14:51 ` dataCobra
2024-02-17 14:51 ` dataCobra
2024-02-17 14:52 ` dataCobra
2024-02-17 15:14 ` mobinmob
2024-02-17 15:15 ` mobinmob
2024-02-17 15:28 ` dataCobra
2024-02-17 15:30 ` dataCobra
2024-02-17 15:40 ` mobinmob
2024-02-17 15:48 ` mobinmob
2024-02-17 15:50 ` mobinmob
2024-02-17 15:51 ` mobinmob
2024-05-18 1:46 ` github-actions
2024-05-18 20:49 ` mobinmob
2024-08-17 1:49 ` github-actions
2024-08-30 15:55 ` mobinmob
2024-08-30 16:08 ` [PR PATCH] [Updated] " mobinmob
2024-08-30 16:09 ` mobinmob
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240207173717.A03AB21131@inbox.vuxu.org \
--to=mobinmob@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).