SiFuh_ has quit [Remote host closed the connection]
SiFuh_ has joined #crux-musl
<SiFuh>
ukky: I mentioned to the wife your "AI Comments" thing. She said "But you don't use AI. You hate it" I said "But how do you know I didn't secretly ask it to do it for me?" She said "I'd know, because I would hear you screaming and yelling and cursing it" HAHAHAHAHAHAHAHAHA
<remiliascarlet>
SiFuh: I don't think you can easily turn a GPL license into BSD, on paper at least. When the AI craze started, we've seen you can just do so in practice.
<remiliascarlet>
Also, I think I'd prefer more of a governance style as seen in OpenBSD; Theo de Raadt has the final say, so if he says no, then it's a no.
<remiliascarlet>
SiFuh: Well, good thing that patents in China are considered useless.
<SiFuh>
remiliascarlet: It is mine, so it can't be GPL
dlcusa has quit [Ping timeout: 276 seconds]
<remiliascarlet>
SiFuh: Oh, I thought you meant the entire distro.
<remiliascarlet>
So Linux kernel, coreutils, and all.
<SiFuh>
remiliascarlet: Just my binary rc
<farkuhar>
Hmm, hotplugd lets you send HUP to a running daemon when a particular class of devices is plugged into the USB port. https://dpaste.com/FQTJC4DSX.txt
<SiFuh>
farkuhar: Yes, when I unplug the bluetooth it switches to speakers. When I plug in the bluetooth, it switches back to bluetooth again.
<farkuhar>
There's probably a direct equivalent in terms of udev rules. But the rule I'm using simply runs `sed -i` on the file /var/lib/sndio/server.default, and any program that sources that file on startup can see the new value of environment variable AUDIODEVICE.
<farkuhar>
Restarting the program to re-read the file that sets an environment variable is probably more disruptive than restarting the daemon itself. Maybe I should switch to a udev rule that restarts the daemon instead.
<SiFuh>
farkuhar: Probably easier if you switch to OpenBSD
<farkuhar>
SiFuh: If I wipe out my CRUX installation to make space for OpenBSD, how would I ever fix the interaction between gimp and poppler-ink (ppetrov^s #38)? In a virtual machine?
<SiFuh>
farkuhar: Video call ppetrov^ and hurl abuse at him
<SiFuh>
farkuhar: If I decide to not use colour at all. I might change the printf to puts and fputs
<farkuhar>
SiFuh: hurling abuse at ppetrov^ won't fix a problematic interaction between ports in the official repos.
<SiFuh>
farkuhar: No that's what happens when you try to explain to people what to do over a video call. You end up abusing them for not listening and wasting your time.
<farkuhar>
SiFuh: Are you speaking from past experience video calling zorz?
<farkuhar>
One of the selling points of SourceHut is that downstream users can use an email-based workflow to propose improvements, no need to register an account. I wonder whether olutmies seriously considered the downsides of Gitea when setting up the git.crux.nu frontend.
<farkuhar>
It would be weird for the Outlaw or Crucial project to register a domain name completely different from the name that's eventually chosen for the distro. But there's a precedent for that: cat-v.org is a semi-official site for information on Plan9. In a similar way, rc-printf.org can be a semi-official site for Outlaw or Crucial.
<farkuhar>
In both cases, the domain name would reflect a design decision that the new OS wanted to distance itself from.
<SiFuh>
Alien
<SiFuh>
emmett1 and I were talking about that today
<SiFuh>
Alien Linux. I said change the e to a 3 like you do with Krak3n
<farkuhar>
Isn't there an AlienBob in the Slackware world?
<SiFuh>
Aliən
<SiFuh>
CRUX Origin
<farkuhar>
Heh, that reminds me of the truncated spelling aliasOrignalName in pkgdb.cpp, as if jw couldn't be bothered to spell out all the letters.
<SiFuh>
FarkUcrux
<SiFuh>
farkuhar: emmett says he doesn't particulary like the name Cruxial or crucial, but I think he doesn't want CRUX anywhere near the name anyway.
<SiFuh>
Although he said the name CRUX is perfect
<farkuhar>
Speaking of aliases, I wonder if there's any demand for this feature: `prt-get dependent --recursive $foo` would inspect /etc/prt-get.aliases to see if anything in the reverse-dependency tree is serving as an alias to the actually-listed dependency, and run the reverse lookup using the actually-listed dependency instead (rust instead of rust-bin, for example).
<SiFuh>
I don't have $foo installed
<farkuhar>
Hahaha
<farkuhar>
I agree with emmett1, the name CRUX is fine. Why should olutmies & company get to retain ownership of that name, if they're the ones who are deviating from Per's vision?
<SiFuh>
"Then either you kick beerman then take over CRUX or create a distro with different name and identity" emmett Hehehe
<SiFuh>
/usr/local/ Tertiary hierarchy for local data, specific to this host. Typically has further subdirectories
<SiFuh>
That's contrib!
<SiFuh>
Hence the reason it is commented out in prt-get.conf and disabled. I don't have any contrib ports installed here.
<farkuhar>
SiFuh: lucky you, not having any contrib ports installed. Meanwhile olutmies has assigned me the task of figuring out why contrib/gimp does not play nicely with contrib/poppler-ink.
<SiFuh>
You using the right version?
<SiFuh>
libpoppler-glib 0.69.0 poppler-data 0.4.9
<farkuhar>
I didn't blindly copy the contents of /etc from a 3.7 installation to 3.8, if that's what you had in mind.
<farkuhar>
poppler-data is version 0.4.12, and poppler itself will optionally be built against glib (if gobject-introspection is found).
<SiFuh>
farkuhar: Well the INSTALL files says what versions to compile against
<SiFuh>
And since GIMP now hard codes poppler in, it would probably mean it is more difficult to upgrade versions of poppler
<SiFuh>
So unless you want to resort to something that could possibly involve heavy patching, you may have no choice but to downgrade to the appropriate version
<farkuhar>
I have to trust the reports of ppetrov^ and olutmies (that removing poppler-ink is sufficient to fix the gimp build), because so far I cannot even get a successful build when poppler-ink is not installed. I keep hitting the "illegal variable name" error when generating gimp-splash.png
<farkuhar>
It's the same error regardless of whether poppler-ink is installed, which led me to question whether ppetrov^s initial assessment was accurate. So I might follow up on that hunch, and edit the gimp-3.0.2/data/environ/meson.build to remove the offending BIN_PATH directive.
<farkuhar>
It would be presumptive of me to close #38 as a non-issue, now that I've gotten successful builds of gimp 3.0.2 both with and without poppler-ink present. Keep in mind, my test platform is CRUX-MUSL 3.8, and presumably ppetrov^ and olutmies discovered the harmful interaction on CRUX-glibc 3.8
<farkuhar>
So if someone still running CRUX-glibc can try building gimp with poppler-ink present, it would help to hear from you before I report my conclusions in the #38 discussion. Tentative finding: poppler-ink is not detrimental to the build, and the "illegal variable name" error can be avoided by turning off the splash screen target.
<farkuhar>
Actually using the compiled gimp is a different matter. Now when I try to run it, gtk complains that "Icon 'image-missing' not present in theme Default". I might need to edit a dotfile somewhere to set the correct gtk theme.