* 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 scripts need a few dependencies like iproute2, nftables, kmod and other things openrc and systemd anyway need... so it's also in gentoo.
Pretty much 66 itself is the only thing not packaged.
* Are you willing to become a proxy maintainer for 66 and any currently-unpackaged dependencies? https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers
I s6 and/or execline get orphaned any time, I am ready to take them up...
One reason a package might not get added to the main repo is not
that no-one has created an ebuild, but that no-one is willing to
commit to maintaining that ebuild, i.e. actively following
upstream updates and issues. An ebuild added to a repository
without anyone committing to maintaining it can create problems
for (a) Gentoo devs, who end up being forced to take on extra
volunteer work; and/or (b) users, who can't rely on that ebuild
getting security and bug fixes etc.
I am ready to commit to it and actively maintain it... for a long time...
Depending on the situation, the package might more appropriately
be added to the GURU repository:
https://wiki.gentoo.org/wiki/Project:GURU https://wiki.gentoo.org/wiki/Project:GURU/Information_for_Contributors
But I want 66 to be usable as an alternative to systemd and openrc, right out of the box... [i.e. stage3] [with all scripts etc... bundled...]
So NOT GURU...
But that's my last resort if the package gets rejected...
* At any rate, be sure to run pkgcheck on your ebuild:
https://wiki.gentoo.org/wiki/Pkgcheck
Thanks...
Best Regards,
Pramod
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)