On Tuesday, May 6th, 2025 at 8:17 PM, Michael wrote:
> Just to say thank you for working on this and for updating us on progress.
Many more frontends and packages are being added at a rapid pace, to the repo.
Kindly voice your opinion and requirement on what is priority and what is not.
To prep
s are currently in a separate overlay...
The repository:
https://github.com/pramodvu1502/66-svmgr-gentoo-overlay
The Gentoo Wiki Page (incomplete as of now):
https://wiki.gentoo.org/wiki/66-init
Kind regards,
Pramod V U
You need a rust compiler to compile rust's own rust compiler.
You either need dev-lang/rust-bin, a package with binaries... Either just use
it or compile the main rust package for use.
If that's a problem. dev-lang/mrustc is another compiler for rust, written in
C/C++. It has been written speci
systemd is a convenient service manager (and much more!!).
It provides too many things, which work well... for standard windows-like use
cases.
Seeing my post title, a question you might get is "Why not just use systemd? It
just works better!..."
(Please read below, then this; It is just a TL;D
> I am not sure I understand the proposal either, tbh.
Read below to understand
> Although in general, the job of an ebuild tends to be to ensure that
> mandatory requirements are satisfied somehow, so if 66 needs a launcher
> and provides its own (?) then adding a dependency on an external one
> The bot(s) also link to
>
> https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide
>
> If you are not a Gentoo Developer, you need a Gentoo Developer to merge
> changes for you. This is called proxying -- you author the change and
> someone else helps you by merging it.
>
> The Pr
> You are right, i was wrong - sorry. i was confused by what you had
> written previously, as in your previous messages, you didn't
> simply write:
>
> By setting USE=-launcher for dbus-broker, systemd doesn't get
> pulled in.
Exactly; However, some evaluation needed on how to handle this for u
> Firstly, as some context, i'm the author of a guide "D-Bus: The
> essentials":
>
> https://github.com/flexibeast/guides/blob/master/dbus.md
>
> and a guide "D-Bus and X sessions":
>
> https://github.com/flexibeast/guides/blob/master/dbus-and-x-sessions.md
>
> as well as having made various ed
> > > dbus-broker depends on systemd, and you probably don't want 66
> > > to
> > > pull in systemd. :-)
> >
> > Only with the USE=launcher
> > `66-dbus-launch` in `sys-apps/66-tools` provides an alternative
> > "launcher" which doesn't depend on systemd. It instead uses 66.
>
>
> This page
> dbus-broker depends on systemd, and you probably don't want 66 to
> pull in systemd. :-)
Only with the USE=launcher
`66-dbus-launch` in `sys-apps/66-tools` provides an alternative "launcher"
which doesn't depend on systemd. It instead uses 66.
> i don't understand why you're talking about elo
66 is an excellent service management suite which uses s6 under the hood,
provides a simple declarative INI format for services, manages dependency
without races, handles logging with s6-log such that logs from different
services stay separate, and makes sure that no line of logs is lost in the
> * All of 66's dependencies will need to be packaged as well, if
> they're not already available.
The only dependencies of 66 are a libc [musl or glibc whatever], s6 and
execline.
libc, obviously, is available.
s6 and execline are also supported in gentoo, right in openrc...
The included scrip
Soon, I will be back with an ebuild.
Will also PR on github for inclusion into repo...
But 2-4 days delay due to unforseen circumstances; sorry.
Regards,
Pramod
I'd like to disclaim beforehand that THIS ISN'T A PRO-SYSTEMD/ANTI-SYSTEMD
PROJECT; IT'S JUST ANOTHER ALTERNATIVE
obarun is an arch-based distro, and it has an init system named 66.
This init system is also available on Void linux.
For questionable reasons it isn't on Artix and Devuan.
It is jus
14 matches
Mail list logo
