💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2020-12-10.txt captured on 2024-05-26 at 16:20:17.
⬅️ Previous capture (2021-12-17)
-=-=-=-=-=-=-
2020-12-10T00:36:32 #kisslinux <micr0> k it took like two and half hours, but i went from 125 .* files and directories down to 21, and 131 non-hidden files and directories down to 27
2020-12-10T00:37:34 #kisslinux <micr0> also make 10 PRs and a 11 issues for antidot, so a lot of these should be automagic for others
2020-12-10T00:42:48 #kisslinux <acheam> nice!
2020-12-10T12:44:06 #kisslinux <Necrosporus> Does kisslinux support ARM yet?
2020-12-10T12:44:16 #kisslinux <testuser[m]> yes
2020-12-10T12:46:23 #kisslinux <testuser[m]> https://github.com/jedavies-dev/kiss-aarch64
2020-12-10T12:49:55 #kisslinux <Necrosporus> testuser[m], thanks, but let's be more specic armv5t
2020-12-10T12:50:03 #kisslinux <Necrosporus> or arm v7l
2020-12-10T12:59:04 #kisslinux <testuser[m]> You can compile it yourself
2020-12-10T12:59:07 #kisslinux <testuser[m]> Should be easy
2020-12-10T12:59:36 #kisslinux <testuser[m]> Not sure if kiss has been ported to those
2020-12-10T13:02:26 #kisslinux <testuser[m]> https://github.com/jedavies-dev/kiss-armv7
2020-12-10T13:14:54 #kisslinux <Necrosporus> Not as easy as using a precompiled tarball though
2020-12-10T13:15:09 #kisslinux <Necrosporus> but I might try aarch64 when I receive new board
2020-12-10T16:06:40 #kisslinux <onodera> does anyone know how i can see my gpu info/name
2020-12-10T16:08:46 #kisslinux <onodera> lspci busybox displays way less info
2020-12-10T16:25:55 #kisslinux <ominous_anonymou> anything under /proc/driver that has info?
2020-12-10T16:32:29 #kisslinux <testuser[m]> pciutils?
2020-12-10T18:25:27 #kisslinux <systemE> onodera: maybe dmesg
2020-12-10T18:27:57 #kisslinux <onodera> ` error: expected identifier or '(' before numeric constant`
2020-12-10T18:28:09 #kisslinux <onodera> extern int PAGE_SIZE;
2020-12-10T18:28:28 #kisslinux <onodera> is this some kind of error related to musl? I'm following the exact same build instructuons as arch and gentoo
2020-12-10T18:28:31 #kisslinux <onodera> for some package im porting
2020-12-10T18:43:57 #kisslinux <micr0> onodera share the package?
2020-12-10T18:44:06 #kisslinux <micr0> also might i recommend kiss-steal x)
2020-12-10T18:44:37 #kisslinux <micr0> it searches the aur, void, oasis i think for their build scripts and opens it in a folder in your editor
2020-12-10T18:45:13 #kisslinux <micr0> i usually look at a few scripts and the readme to see the difference between how something *should* build and how its practically built
2020-12-10T18:54:01 #kisslinux <ominous_anonymou> ohhhh man that's a good idea
2020-12-10T18:58:38 #kisslinux <micr0> honestly i could hack together a kiss-steal-aur that would autmatically migrate the whole PKGBUILD, but i often find it overkill
2020-12-10T18:59:48 #kisslinux <ominous_anonymou> most of the things i've done myself are standard configure, make, make install but when i look at other people's repos that have packaged the same things they always have all these different options specified
2020-12-10T19:00:38 #kisslinux <ominous_anonymou> meanwhile mine's like "uhhh --prefix yeah yeah that's good enough", always feels like i'm doing it wrong
2020-12-10T19:00:41 #kisslinux <micr0> ominous_anonymou i see the same thing, but do you have specific examples?
2020-12-10T19:00:50 #kisslinux <micr0> ominous_anonymou I think that is the correct thing to do
2020-12-10T19:01:29 #kisslinux <micr0> keep it as vanilla as possible - let the maintainers of the software choose how they want to (auto-detect) and enable/disable features
2020-12-10T19:01:56 #kisslinux <micr0> if you have specific reasons to specify something enabled/disable (for example, the wayland repo has software its fine to say '--disable-xorg' or whatever)
2020-12-10T19:02:19 #kisslinux <ominous_anonymou> well that makes me feel a little better. but some of the Gnu stuff where i had no clue i could disable documentation would be nice to know and it's not always obvious that it's even an option
2020-12-10T19:02:28 #kisslinux <micr0> also ominous_anonymou I would be happy to do 'repo reviews' where I take a look at your repo packages and suggest changes and vice versa
2020-12-10T19:03:06 #kisslinux <ominous_anonymou> i appreciate that. if i ever put them up on github i'll toss a link over for sure
2020-12-10T19:03:09 #kisslinux <micr0> omg, I never thought I would be pissed at all the different ways to write 'flavour of the year markup language' -> manpage that is a pain in the butt
2020-12-10T19:03:27 #kisslinux <micr0> asciidoc, txt2man, all of them annoying to package
2020-12-10T19:03:44 #kisslinux <micr0> I understand as someone who writes software if you dont wanna write a manpage but dang
2020-12-10T19:03:59 #kisslinux <ominous_anonymou> and it takes forever to compile that shit on some packages
2020-12-10T19:04:22 #kisslinux <micr0> yeah, thats the main thing I have manually disabled in a lot of packages 'i just want to work with kiss' is disable documentation
2020-12-10T19:04:27 #kisslinux <micr0> which kinda sucks for other users but oh well
2020-12-10T19:04:38 #kisslinux <micr0> and most of my software thats cli have good enough --help, or tldr-pages
2020-12-10T19:04:52 #kisslinux <ominous_anonymou> my benefit is i'm the only user so i don't have to care too much lol
2020-12-10T19:05:29 #kisslinux <micr0> :)
2020-12-10T19:09:19 #kisslinux <ominous_anonymou> are there standard configure flags that can be used "everywhere", or does it come down to sucking it up and just reading through makefiles?
2020-12-10T19:11:07 #kisslinux <micr0> i look for build instructions first (in the repo, or if hosted, if there is a wiki), then other people's build scripts (lfs/aur/void/alpine/etc...), then tab-complete with make, then the Makefile itself
2020-12-10T19:11:29 #kisslinux <micr0> generally i've found that what is 'standard' really depends on the second year after a project was created
2020-12-10T19:11:40 #kisslinux <micr0> and that changes about every 7 or so years
2020-12-10T19:12:25 #kisslinux <micr0> so like, DESTDIR, --prefix, ./configure+make+make install VS cmake VS meson VS go build with modules VS go build without
2020-12-10T19:12:48 #kisslinux <micr0> there are patterns, but if there was only one standard way to build things, well, likely there would be only distro or one package format tbh
2020-12-10T19:13:35 #kisslinux <ominous_anonymou> here's a good example: https://github.com/periish/kiss-ricing/blob/master/kiss-ricing/fvwm/build
2020-12-10T19:14:12 #kisslinux <micr0> well a| periish left from what i remember b| ricing implies a level of customization a little bit beyond 'just vanilla'
2020-12-10T19:14:14 #kisslinux <micr0> but ill look now
2020-12-10T19:14:52 #kisslinux <micr0> like sbindir and mandir may not be necessary, or it may be. you can kiss build && kiss install without those options, then use `kiss manifest` to see how it changes things
2020-12-10T19:15:11 #kisslinux <micr0> --enable-{feature} and --disable-{feature} for ./configure / make is pretty normal
2020-12-10T19:15:33 #kisslinux <micr0> also you can use `ccmake` to get a nice curses menu for cmake based configuration
2020-12-10T19:15:33 #kisslinux <ominous_anonymou> ah ok
2020-12-10T19:15:55 #kisslinux <micr0> i dont understand autogen/autoconf/autoreconf
2020-12-10T19:16:19 #kisslinux <micr0> and i dont care to learn them. ive gotten by well enough just treating them like a cmake step before configure+make+make install
2020-12-10T19:16:29 #kisslinux <micr0> some packages need it, some dont
2020-12-10T19:17:16 #kisslinux <micr0> also one thing to keep in mind - if you git checkout something, vs download a 'release' tarball, sometimes one of the build-from-source steps has already been done for you
2020-12-10T19:17:34 #kisslinux <micr0> like you might not need autogen.sh from a tarball release, but you do need it for a git clone
2020-12-10T19:17:38 #kisslinux <ominous_anonymou> i noticed that, yeah. bit me a time or two
2020-12-10T19:17:54 #kisslinux <micr0> again, no hard and fast rules, just some intuition built over years of from-source building
2020-12-10T19:18:06 #kisslinux <dilyn> ./configure --help | less and meson configure | less are the best for seeing what's up
2020-12-10T19:18:07 #kisslinux <micr0> of course, some people actually understand all this stuff and are better for it
2020-12-10T19:18:25 #kisslinux <micr0> oh meson configure, i'll add that to the sluethkit
2020-12-10T19:18:37 #kisslinux <dilyn> after that, it's digging into configure.in and stuff to see what tests trigger what feature I don't want
2020-12-10T19:19:00 #kisslinux <ominous_anonymou> thanks for the info!
2020-12-10T19:19:03 #kisslinux <dilyn> my biggest thing is disabling tests and docs because building tests is a waste of time when I'm not running them :v
2020-12-10T19:19:31 #kisslinux <ominous_anonymou> yes totally agree. and i'm running kiss in a 1GB ram vm so cutting out extraneous things really helps
2020-12-10T19:20:24 #kisslinux <dilyn> if that's the case I'd appeal to arch/alpine/etc less than you might want just because they tend to enable most of the options available
2020-12-10T19:20:59 #kisslinux <ominous_anonymou> although if they have an --enable-xxx it might clue me in that there's a --disable-xxx available too i guess
2020-12-10T19:21:00 #kisslinux <dilyn> generally feature-checking should only take <5min per package; for bigger things (like qt5) it could take a bit longer but ultimately it's a pretty trivial process and eventually you learn what to look for
2020-12-10T19:21:22 #kisslinux <ominous_anonymou> yeah sounds like just getting the experience helps
2020-12-10T19:45:26 #kisslinux <micr0> chmod -222 $HOME is working for me, crazy
2020-12-10T19:47:50 #kisslinux <ominous_anonymou> glad to hear it! i thought it was a neat approach for sure, and helps "force" compliance for lazy people like me
2020-12-10T21:48:49 #kisslinux <nerditup> I don't know why I'm having such a hard time with this, but would someone be able to explain what is happening here: https://git.k1ss.org/kiss/file/contrib/kiss-chroot.html#l34 ?
2020-12-10T21:49:02 #kisslinux <nerditup> I think the underscores `_` throw me off
2020-12-10T21:54:22 #kisslinux <nerditup> chmod -222 was the tip of the week for me
2020-12-10T21:56:08 #kisslinux <micr0> nerditup I *think* the _ is just kinda "ignore this" in a sense
2020-12-10T21:57:43 #kisslinux <ominous_anonymou> so "ignore first word, assign second word to target, ignore all other words"?
2020-12-10T21:58:02 #kisslinux <micr0> echo here three words | while read -r _ target _ ; do echo "_ is $_"; echo "target is $target"; done
2020-12-10T21:58:04 #kisslinux <micr0> that might help
2020-12-10T21:59:19 #kisslinux <micr0> yeah, it is ignore all other words
2020-12-10T22:14:38 #kisslinux <nerditup> Interesting, I can't find that relevant documentation explaining how that works - dylan is next level :D
2020-12-10T23:17:03 #kisslinux <nerditup> micr0: that helps, thanks!
2020-12-10T23:46:42 #kisslinux <aarng> nerditup: `read` can word split it's input, based on IFS, into multiple variables
2020-12-10T23:47:09 #kisslinux <aarng> if there are less variables than fields, the last one will receive all remaining fields
2020-12-10T23:47:52 #kisslinux <aarng> using underscore as variable names is just a way of signaling "let's ignore this field, we are not interested in it"
2020-12-10T23:48:42 #kisslinux <aarng> any other variable name would work too though, like using x's for example