<ehawkvu>
so, right now I'm working on having builds that occur inside bubblewrap
<sewn>
is there no bwrap library
<sewn>
or are you unable to do that in listp
<sewn>
also wow i never knew this was that big
<ehawkvu>
I'm shelling out to the cli so it's a non-issue
<ehawkvu>
anyways
<ehawkvu>
the first time that the code runs, it immediately fails, claiming that it is unable to find the package's build script
<ehawkvu>
however, when you run the code a second time, it magically works
<ehawkvu>
Maybe there's something I'm not understanding when it comes to how you are properly supposed to expose binds, but that behavior seems completely wrong
<sewn>
kisslinux has 49 members
<sewn>
i recall kisslinux having like alot more than that
traidare has joined #kisslinux
<sewn>
I wonder where everyone went
<sewn>
it used to be super active back then!!!
traidare has quit [Ping timeout: 252 seconds]
phinxy has quit [Ping timeout: 252 seconds]
chomwitt has joined #kisslinux
phinxy has joined #kisslinux
rfaa has quit [Remote host closed the connection]
sad_plan has joined #kisslinux
<sad_plan>
hi
<sad_plan>
sewn: im asking myself the same question. used to me so much more activity here
<ukky>
sad_plan: hi. I hope you don't mind me staying here, as I am not using KISS Linux, just curious.
<sad_plan>
ukky: I dont. I just pointed out that its alot less activity here now, than what it used to be
<sad_plan>
why arent you using kiss though?
traidare has joined #kisslinux
<ukky>
when time came to switch from previous distro, made a decision to try another distro first. But I like many features of KISS Linux.
<sad_plan>
I see. what distro are you on now?
<ukky>
using CRUX now. switched from Gentoo.
<sad_plan>
cool. never tried crux myself. can you use only personal ports on crux aswell as kiss' personal repos?
<ukky>
yes, you can. I modify a lot of official ports, plus create new ports.
<sad_plan>
cool. its nice to see that other distros also allow aloot of user freedoms, in terms of customization
<sewn>
what is crux's package format? makefiles?
<sad_plan>
i think theyre just called pkgfiles
<ukky>
main file is 'Pkgfile', which is sourced from a shell script. Pkgfile defines deps, optional deps, source locations, and build() function that compiles and creates files in package dir
jslick has quit [Ping timeout: 272 seconds]
jslick has joined #kisslinux
<ukky>
which device manager is mostly used in kiss linux, mdev or udev? Does anybody use static /dev? Just curious.
<sad_plan>
busybox's mdev is probably the most used, then comes mdevd.
<sad_plan>
I personally dont use anything at all
<ukky>
I tried static /dev first, then moved onto busybox' mdev. Most crux users use eudev (default).
<sad_plan>
I see. static /dev didnt cut it for you?
<ukky>
Static /dev was working well, I just like to experiment and find optimal solution. I might switch back to static /dev if something will bother me using mdev.
<sad_plan>
sure. I personally dont need it, because I use tinyx, so the devices I use gets detected just fine without it
<ukky>
Switching from SystemV to Runit made my system boot faster, from 50 seconds to 10 seconds, measuring from starting /sbit/init to agetty login prompt.
ghoulpine has quit [Quit: Connection reset by purr]
<ukky>
Do you mean non-configurable, or 'gcc -static' ?
<sad_plan>
gcc -static. although I now use -static-pie so that I can enable aslr or w/e it was called
<ukky>
Why static? It seems like everybody voices agains it?
<ukky>
I even disable '-static' for non-initramfs busybox build.
<sad_plan>
why not? that is also part of why I enjoy it.
<sad_plan>
static linking is also getting rather niche, which is something I can enjoy
<sad_plan>
I also have none of the issues with abi instabilty
<sad_plan>
I dont *have* to rebuild a package when a library gets updated an thus breaks several packages
<ukky>
of course, there are advantages to static linking
<sad_plan>
yep. old system like plan9 iirc, is statically linked, so its somewhat a thing of the past. I does however require you to rebuild packages when libraries and such are updates, so it does take a more toll on your system. not that it matters to me
<sad_plan>
for the most part I did initially just enjoy that I could remove aloot of packages which wasnt needed at runtime anymore due to static linking.
<sad_plan>
potentially, I can even remove zlib
<sad_plan>
with oasislinux, you can even skip having a libc
<sad_plan>
that said, if you have a 100% statically linked system
<sad_plan>
alot of people would probably scoff at that, and ask; why the hell would you even do that?
<sad_plan>
my answer to this is simple; because I can
<ukky>
respect for going extra mile beyond what is considered normal/default
<sad_plan>
yeah. my biggest hurdle is really the browser though. if you cant use mesa, available browsers is.. lacking.
<sad_plan>
your mostly left with textbased browsers like links or lynx, or perhaps netsurf like oasis uses
<sewn>
/join #sourcemage
<sewn>
oops
<ukky>
yeah, most browsers have crazy dependencies. ATK, D-Bus, you name it
<sewn>
chromium and firefox doesnt need atk
<sewn>
nor dbus
<sewn>
they are optional, each provide their own notification handling
<sad_plan>
I knoow.. theyre rather horrible, or I like firefox initially, but its horrible to build from scratch.. alot of work, and takes ages to build everything needed
<sad_plan>
not that webkit is that much better though. actually has more deps, and takes just about the same time to build as firefox does
<ukky>
I couldn't remove sime stuff from chromium, but could remove ATK and D-Bus from firefox. Removing ATK from Gentoo was painful.
<paradigm>
The Bedrock Linux project's definition of a metadistro also includes LFS, but I'm not sure if LFS considers themselves a metadistro: https://bedrocklinux.org/faq.html#what-is-meta
<sewn>
lfs is a 1000-page book of instructions, a plank of wood, and no tools
<sad_plan>
so basically it means that the distro does not distrobute end-goal software. what
<sad_plan>
that means that more or less all source-based distros are technically meta-distros, as they dont distrobute the software it self. atleast thats how I understand it
<paradigm>
This is one of those things where you may not have clean groupings, and definitions here get blurry. Even non-meta "Linux distro" can be hard to define; Debian is usually categorized as such, but they offer non-Linux kernels like FreeBSD and HURD/Mach. But yes, I think the Bedrock definition would effectively include all source-based Linux distros (along with other not necessarily source based