fishe has quit [Quit: Connection closed for inactivity]
_whitelogger has joined #crux
ppetrov^ has joined #crux
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
joe9 has quit [Remote host closed the connection]
<ppetrov^>
hi, the post-install script of xorg/xorg-font-bh-type1 does: mkfontdir and mkfontscale in /usr/lib/X11/fonts/Type1, while fonts are installed in /usr/share/fonts/X11/Type1/
<SiFuh>
Wonder if this is the reason some are saying the fonts are ugly :-P
<farkuhar>
ppetrov^: what prompted you to try building id3lib, anyway? Another stroke of nostalgia? It looks as if the upstream package hasn't been touched since 2004.
<ppetrov^>
grip looks for it
<ppetrov^>
and since it's in contrib, i naively expected it to build
<farkuhar>
Ahh, with an unassuming name like "grip" it was easy to overlook the possible dependency. Not as obvious a connection as "abcde" or "asunder" ;)
<farkuhar>
I was browsing your repository looking for ports that might require id3lib, and the name "grip" was too innocuous to trigger the association in my mind.
<ppetrov^>
you could've just asked
ardo has joined #crux
<farkuhar>
I actually did ask on this channel, but only after you had already signed out.
<ppetrov^>
ah
<ppetrov^>
well, mystery resolved
<ppetrov^>
or who knows, maybe i enjoy just building the stuff in contrib
<farkuhar>
thanks, we definitely need more testers to keep the quality of the contrib repo high.
<ppetrov^>
heh
<ppetrov^>
crux definitely needs some better quality control, but that's another topic of conversation
<SiFuh>
heh
<SiFuh>
Hmm grip is that okd gtk application for ripping audi cd's?
<farkuhar>
here's what one of the core maintainers recently said on that topic: "if upstream doesn't keep working with current versions of system libraries I usually just look for a modern alternative. I don't hold any sentimentals for old software on a modern workstation setup."
<farkuhar>
So thanks for raising awareness that id3lib doesn't build with the current toolchain.
<farkuhar>
The modern alternative in this case would be opt/taglib, but it would be nontrivial to replace all the grip code that expects the id3lib API.
<ppetrov^>
farkuhar, I agree with what the core maintainer said; I know that's swimming against the current and I don't plan to do it for long
ocb has quit [Remote host closed the connection]
ocb has joined #crux
maledictium has quit [Remote host closed the connection]
fernando has joined #crux
<fernando>
hello?
<fernando>
is CRUX still up to date?
<ppetrov^>
always
fernando has quit [Remote host closed the connection]
<SiFuh>
ppetrov^: Always? Hahah No, it is more about being a game of catchup ;-)
<ppetrov^>
from the perspective of a Slackware user, it is :P
<SiFuh>
I heard recently they stopped using the old 5 1/4" floppy disks
<ppetrov^>
to boot the kernel? yep
<ppetrov^>
jokes aside, the info on its webpage is so outdated that it's getting ridiculous. It has been brought up on several occasions, but not much of an improvement. Quite a pity
maledictium has joined #crux
<farkuhar>
the outdated webpage inspired some users to take matters into their own hands: witness https://gitlab.com/SiFuh/Documentation/ and the fine work of dlcusa. But if you want to help out, ppetrov^, I'm sure they'd appreciate patches and new wiki contributors.
<SiFuh>
But your better off following the cheat sheet
<SiFuh>
you're*
<ppetrov^>
you sound like an american
<SiFuh>
After writing that and with a bit more research it is much better to use efi/BOOT/
<ppetrov^>
every time i see this, i know i am speaking with a native speaker
<ppetrov^>
thanks, i guess i'll try it for 3.7
<ppetrov^>
so in syslinux.cfg i specify the kernel, which should be copied
<SiFuh>
Yeah it is very simple once you see what is being done. The biggest trip-up for those new to it is when they need to use efibootmgr and cannot figer out why /boot/efi/boot/ isn't working. Then you have to explain to them that UEFI is not looking for /boot because it doesn't exist. It is looking for the partion and efi/boot. Like sda1/efi/boot
<SiFuh>
Yeah, configuration is similar to lilo setup. But once you have it installed. You never need to install it again. Just edit config and your done. Not like lilo where you edit config then must run lilo
<SiFuh>
I have actually installed syslinux with slackware, then formatted slackware and installed void, and formatted that and installed artix and so on, and never touched syslinux. Just copied the kernel over or edited the config to the location of the new kernel.
<ppetrov^>
*you're done
<SiFuh>
Haha
<ppetrov^>
sorry couldn't resist
<ppetrov^>
thanks for the explanation
<SiFuh>
I knew there was on in there
<SiFuh>
Oh and another thing. You can uninstall the syslinux port once you have successfully configured it and your system boots.
<ppetrov^>
isn't it the same with lilo?
<SiFuh>
But if you use my program ckut and it is not installed I think it won't show the syslinux menu
<ppetrov^>
man, changing the distro, changing the bootloader... i am not good with changes
<SiFuh>
No because with lilo if you update the kernel you need lilo installed to reconfigure it.
<ppetrov^>
yes, of course
<SiFuh>
Hah, just remembered something. Someone asked me last year if I could look at modifying ckut to build kernels as a normal user.
<SiFuh>
I made lynx optional, bloody github. I have a back up I will upload to gitlab
<SiFuh>
That was weird. My system has version 2.1, my local repo and gitlab repo have version 1.3.
<ppetrov^>
actually i meant to ask you about optional dependencies: how do you know which ones are optional? What I do is: get all deps (except from core), then filter them by findredundantdeps -s
<SiFuh>
ppetrov^: uploaded already.
<ppetrov^>
thansk
<SiFuh>
I use a core based system and build the port from that. What it requires I add as a dependency. What it doesn't can be put in #Optional: or #Nice to have:
<ppetrov^>
only a core based system?
<SiFuh>
Yes
<ppetrov^>
like in chroot environment?
<SiFuh>
VM
<ppetrov^>
ok
<SiFuh>
Then I use ROmsters pkg-clean port to clean the system back to core
<SiFuh>
Usually I build it on my main system first. Then I transfer it to the VM and build there and that is when I can pick out what is needed and what it is not
<ppetrov^>
yes, makes sense
<SiFuh>
Telegram Messenger keeps updating like every hour and they don't provide much of anything valuable
<SiFuh>
It is like, changing the icon colour 24 times in a day because he didn't like the look of it, and uploads each change 24 times in a day
<ppetrov^>
i removed it from my ports
<SiFuh>
I disabled the update feature, so when a new version appears it shows a white arrow.
<ppetrov^>
i am looking at pkg-clean
<SiFuh>
I was considering re-enabling the update feature, but one version added something extra which would have been a ghost file on CRUX so I didn't bother changing it
<ppetrov^>
how do I specify that i want to keep everything from core? there's this line: PKG_CLEAN_KEEP=
<SiFuh>
ppetrov^: it basically remove everything you installed that is not from core. There is a config file in /etc/ where you can add programs you want to keep from being removed.
<ppetrov^>
ok, so I cannot specify that I want to keep stuff from, say, opt
<SiFuh>
You can
<SiFuh>
But each port
<ppetrov^>
yes, that's what i was afraid of
<ppetrov^>
handy tool, for sure
<SiFuh>
so for mine I have syslinux ckut ccache and sccache
<ppetrov^>
of course syslinux :P
<ppetrov^>
hmm,... and what is pkg-not?
<SiFuh>
No idea
<ppetrov^>
"List untracked files from package database"
<farkuhar>
ppetrov^: sorry I misunderstood your reference to outdated webpage. I thought it was an echo of stenur's plea from several months ago, something like "set me up with a crux.nu wiki account, there's so much that needs fixing!"
<SiFuh>
I remember that
<ppetrov^>
well, the handbook is kept updated, which is already something
<ppetrov^>
quite a lot, actually
<farkuhar>
Oh, it looks like the mesa project slipped in a fix for the webkitgtk issue, sometime between the bump of the crux port from 22.0.1 to 22.0.2 (https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/15822) I guess it's safe to prt-get unlock mesa and say farewell to the 21.3 branch.