SiFuh_ has quit [Remote host closed the connection]
SiFuh_ has joined #crux-musl
zorz_ has joined #crux-musl
zorz_ has quit [Quit: leaving]
zorz is now known as zorz_
zorz has joined #crux-musl
zorz has quit [Client Quit]
<dlcusa>
So will the doc allow those interested to create and support a notcore collection that would provide all packages necessary to resolve the crux.nu CRUX dependencies expected to be in core that will not be in the forked distro??
<dlcusa>
Theoretically all other crux.nu packages should then be installable on the forked distro without modification.
<SiFuh_>
dlcusa: My custom distro?
<SiFuh_>
dlcusa: "Preforked CRUX" :-)
zorz has joined #crux-musl
<dlcusa>
I think it good to make a clear statement up front if there will be any consideration for supporting crux.nu packages, as opposed to all users are advised to just use that distro.
<SiFuh_>
dlcusa: I was making it for myself because no one has stepped up
<dlcusa>
Then I suggest you put such a statement in your doc.
<SiFuh_>
Why would I need a doc? I already stated I won't even be making an ISO
<dlcusa>
Then you need discuss this no further--it applies to your distro not.
<SiFuh_>
It has libressl, emacs_no-x11.
<farkuhar>
Rolling up disparate components into one port? They did that by lumping together revdep (which needs compilation) with a bunch of interpreted programs (which don't). Every time I push an update to prt-utils, I think: there's got to be a better way to distribute changes to the interpreted programs, without forcing a recompilation of revdep for everybody.
<farkuhar>
So if you rolled all the gcc dependencies into one port, and they get updated on vastly different schedules, then some components will get rebuilt unnecessarily whenever another component gets an update.
<SiFuh_>
Well, point taken
<SiFuh_>
farkuhar: How about this. Each package is complied and archived separately and checked if they need to be recompiled again. Some fancy pkgmk shit there for you to play with.
<farkuhar>
SiFuh_: okay, that's an interesting challenge to work on. Maybe emmett1 has a few ideas.
<SiFuh_>
You'd need checksums
<SiFuh_>
SO you go to gcc-compilation compile it. You now have about 20 ports in one port.
<SiFuh_>
Ahh shit. I had another idea for you too. But I forgot to write it down.
SiFuh_ has quit [Remote host closed the connection]
SiFuh_ has joined #crux-musl
<SiFuh_>
Well I am angry
<SiFuh_>
I don't think it should be my sole responsibility to build an ISO for you guys
<SiFuh_>
It should be former-CRUX users team effort
<SiFuh_>
ukky: You have a way to make rc and runit on the same distro?
<SiFuh_>
I can do the installer to create a selective meny.
<SiFuh_>
menu*
<ukky>
SiFuh_: it depends. /etc/inittab is not used by runit. I believe sysvinit and runit could be installed side by side. Only /sbin/init should point to actual init. It might be possible to create startup and shutdown scripts managing both sysvinit and runit startup/shutdown sequence.