ChanServ changed the topic of #kisslinux to: Unnofficial KISS Linux community channel | https://kisscommunity.bvnf.space | post logs or else | song of the day https://vid.puffyan.us/H7PvgY65OxA
<cem> Because you're writing the config script using cat <<EOF
<cem> And the positional variables you use on that config script are assigned by the build script
<cem> Just make a regular file in the package directory and install it, much less complicated
<ehawkvu> cem: It's generated because I'm not aware of a way that you could do it generically
<ehawkvu> so it's made at build time for the users system
<ehawkvu> But yes, I agree it could be simpler
<cem> What I mean is, move the alpine.config to a file on its own
<cem> It doesn't seem like you get any benefits from generating it on the build script
<cem> Does the $alpinever variable actually do anything?
<ehawkvu> No, I actually don't remember why I added it ...
<ehawkvu> lol
<ehawkvu> nvm, I use it in the post-install hook
<cem> I see, but it's not the version it's just a list of files
<ehawkvu> I was intending it to capture the version under /lib/modules - assuming it's the only one there
shokara__ has joined #kisslinux
<cem> I mean, you already have the version from the APKBUILD, no?
Torr has joined #kisslinux
<cem> (btw, I didn't generate checksums nor tested it)
<ehawkvu> cem: ty!
<ehawkvu> Real test will be if it still kernel panics...
ehawkvu has quit [Read error: Connection reset by peer]
ehawkvu has joined #kisslinux
<ehawkvu> cem: the kernel refuses to boot
<ehawkvu> just hangs
<cem> Maybe it's about alpine's kernel config
<cem> Does an alpine live image boot?
<ehawkvu> brb, just made the usb
ehawkvu has quit [Remote host closed the connection]
<midfavila> hey what was that nordic posix microkernel
<midfavila> the one that emphasizes linux compatability
<midfavila> i can't remember its name
<midfavila> it's not seL4
<cem> The rust thing?
<midfavila> no, it's not written in rust
<midfavila> it's C
<midfavila> hildebrand
<midfavila> i think that's what it was
<midfavila> tyvm semantic scholar
<midfavila> it was that or managarm
<midfavila> unironically considering attempting a KISS port
<cem> C++? cringe
<midfavila> okay buh muh microgernel
<cem> interesting stuff
<midfavila> ideally i'd be able to use sortix
rohan has quit [Read error: Connection reset by peer]
<midfavila> so
<midfavila> modal editor, with an ed-style command mode and an emacs-style line mode, with an emacs-style UI but vi/vim-style extensibility
<midfavila> editor idea
<midfavila> how cursed is this on a scale of 1 to 10
shokara__ has quit [Quit: WeeChat 3.6]
<midfavila> i'm imagining like
<midfavila> exposing the editor's internal state via a pseudofilesystem and using a very simple interpreted language (FORTH or Scheme probably) as an internal extension language, basically nothing but a thin layer of glue to run hooks, manage the UI, etc -- stuff that can't easily be communicated via a fifo
<midfavila> and then that internal language, instead of being an all-singing-all-dancing thing like Emacs and ELisp, takes a more subtle approach more like a shell (maybe shell would be a better extension language ala acme), serving largely to call programs in the wider environment as necessary
<midfavila> so you could have like... an "EDForth" script that implements a C mode, but the C mode doesn't have to be written in EDForth -- you just use EDForth to glue together the internals of the program and, say, an external C or AWK program that reads from the FIFO representing the current buffer's contents and then pipes it back into that to update the buffer on a given event (say, a newline, or you invoke an editing macro)
<midfavila> maybe i'm completely insane
<midfavila> i might have finally lost it
<midfavila> (it's basically a shitty acme)
rohan has joined #kisslinux
<wael_> Hi
<Torr> midfavila: U might like this book: https://oshi.at/aEhE/gtbq.jpg
<Torr> wael_: Hey
<midfavila> honestly shocked that that's not just a meme and that it actually exists
<Torr> Right?!! xD
<midfavila> assuming it's not a complete joke, it might be useful
<midfavila> i'll have to add it to my archive
<midfavila> gaaah
<midfavila> se is *so close* to being my perfect editor
rohan has quit [Ping timeout: 272 seconds]
rohan has joined #kisslinux
<Torr> Started reading it recently, so far it's been quite insightful.
<Torr> Oh, the perfect *thing*.
<Torr> I often have to manage my perfectionism, otherwise it'd kill me.
<midfavila> mine *is* killing me
<midfavila> every time i sit down to work on apportate i see more and more flaws in its design
<Torr> Lol
<Torr> I know the feeling buddy.
<midfavila> still, for a first program i don't think it's that bad
<Torr> It's almost always not that bad, perfectionism is just magnifying its flaws to us. As flaws are but opportunities for betterment.
<midfavila> oh, of course
<midfavila> and i mean,
<midfavila> as long as it's better than hurl I can sleep at night
<midfavila> :D
<midfavila> once I know more about object orientation I'd like to rewrite apportate with it in mind. ideally main wouldn't know anything about the actual protocols it's using, those would be the domain of the objects implemented by optional modules
<midfavila> i really think that in this case OO could massively simplify the design and make it much more modular. right now main has to account for some implementation differences between Gopher and HTTP in a really unsightly manner. dial is kind of clunky too
<midfavila> anyway i'm rambling again
<midfavila> i need to get ready for bed
<Torr> Me too ^^
<Torr> Hey, check out Data Orientation tomorrow. U may like it.
<Torr> (and I said *tomorrow*)
<Torr> See ya
Torr has quit [Quit: leaving]
ehawkvu has joined #kisslinux
<ehawkvu> cem: live usb boots fine
ehawkvu has quit [Remote host closed the connection]
ehawkvu has joined #kisslinux
<testuser[m]> Hi
rohan has quit [Read error: Connection reset by peer]
lanodan has quit [Ping timeout: 260 seconds]
lanodan has joined #kisslinux
aelspire has joined #kisslinux
<aelspire> Hi
<aelspire> "soft" fork of gitea
<aelspire> anyone uses gitea (I've used in the past until I degraded my server to potato to conserve energy) has opinion on it?
rohan has joined #kisslinux
rohan has quit [Read error: Connection reset by peer]
soliwilos has joined #kisslinux
mcpcpc1 has joined #kisslinux
mcpcpc1 has quit [Client Quit]
lanodan has quit [Quit: WeeChat 3.6]
lanodan has joined #kisslinux
<testuser[m]> To write in the ways of the POSIX, she must bang your script with #!/bin/sh That she bangs #!/usr/bin/env sh is wrongful for env is not a guarantee but a privilege. Only guarantee is her ability to she bang #!/bin/sh
<soliwilos> :D
rohan has joined #kisslinux
soliwilos has quit [Ping timeout: 255 seconds]
soliwilos has joined #kisslinux
rohan has quit [Ping timeout: 268 seconds]
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
<wael[m]> ehawkvu: why is libglvnd in kiss-xorg
rohan has joined #kisslinux
macslash1[m] has quit [Quit: You have been kicked for being idle]
rohan has quit [Ping timeout: 264 seconds]
soliwilos has quit [Remote host closed the connection]
soliwilos has joined #kisslinux
<midfavila> dunno if anyone here's interested but i'll be releasing a rootfs of my KISS fork later today
<wael[m]> wats ur kiss fork
<midfavila> doesn't really have a name yet. i've been tentatively referring to it as A/OS
<midfavila> it's nothing too special. just something I work on in my spare time
<midfavila> if nothing else sad_plan might get use out of it
<wael[m]> mid linux
<midfavila> minux
<midfavila> minix
<midfavila> wait-
<wael[m]> minux
<wael[m]> no
<midfavila> yes
<midfavila> too late
<wael[m]> you are going to get sued
<midfavila> andy can *try*
<wael[m]> is it me or did i have so many fortune files that i made the kiss sh/awk fortune implementation really slow
<midfavila> there's an awk fortune?
<wael[m]> in community yess
aelspire has quit [Quit: aelspire]
oak has joined #kisslinux
oak has quit [Client Quit]
oak has joined #kisslinux
oak is now known as _oak
_oak has quit [Quit: Client closed]
schillingklaus has joined #kisslinux
oak has joined #kisslinux
oak has quit [Client Quit]
schillingklaus has quit [Remote host closed the connection]
oak has joined #kisslinux
oak is now known as oak6969
ehawkvu has quit [Ping timeout: 252 seconds]
ehawkvu has joined #kisslinux
oak6969 has quit [Quit: Client closed]
sad_plan has joined #kisslinux
<sad_plan> hi
<sad_plan> midfavila: yeah, id be interested in checking it out anyway
Torr has joined #kisslinux
<sad_plan> midfavila: do you get an issue with cp when building musl?
<sad_plan> I get this; cp: /tmp/4364/extract/musl/usr/bin/ldd -> /usr/bin/./ldd: same file
<sad_plan> I cant seem to replicate it on other packages.
<midfavila> sad_plan i can't build musl on my system rn
<midfavila> because muh tcc
<midfavila> anyway, just finished gzipping the next tarball
<midfavila> might not get out tonight
<midfavila> but it's 10 meg right now
<sad_plan> hm..
<midfavila> which is a pretty substantial decrease compared to the last version
<sad_plan> thats small :p
<midfavila> i think the last was around 26 or 27 meg
<sad_plan> yeah, that sounds more resonable in comparisson to the regular kiss tarballs :p
<midfavila> keep in mind, my userspace is entirely statically linked by default
<midfavila> if you were to modify it to not be... you'd probably reduce it even further
<midfavila> what's upstream at? seven meg?
<sad_plan> I like static linking, so I dont really se the issue there. with some exceptions like me using mesa for my browser though
<midfavila> well, the "problem" is that coreutils are generally pretty tiny executables
<midfavila> statically linking every single one of them introduces a lot of redundant object code
<sad_plan> hah, no, latest is 59mb
<midfavila> lmao
<midfavila> then again my distro's significantly less capable so
<midfavila> no point in flexing
<sad_plan> the previous ones used to be ish 30 something iirc
<sad_plan> how is tiny coreutils a problem?:p
<sad_plan> cant those reduncies simply be stripped?
<midfavila> nnnnnno
<midfavila> by definition statically linked binaries *need* to include all of the code that's necessary for them to run
<midfavila> if you just strip that information out, you... end up with pre-link object code
<midfavila> you get around that problem by using dynamic linking
<sad_plan> hm, ok
<midfavila> ye
<midfavila> it's kind of funny actually, my repository was the largest directory in the new tarball
<midfavila> 18.8mb compared to 14mb for /bin and 15mb for /lib
<midfavila> i want to see if i can just link /usr to /, for shits and giggles
<sad_plan> are you removing headers and static libs too in the tarball? I think you should be able to initially anyway. however, doing a rebuild is now a tad bit more cumbersome :p
<sad_plan> you can do that. its what oasis does
<midfavila> >removing headers
<sad_plan> kiss will happily accept prefix set to / or empty
<midfavila> that's a horrible idea, and i doubt that oasis actually does that
<sad_plan> which will give you the *unix* filesystem or w/e they call it
<sad_plan> oasis does that by default
<midfavila> well, i'm not going to do that
<midfavila> implicit function definitions are cance
<midfavila> cancer*
<midfavila> idek if stuff would *compile* without headers
<midfavila> there has to be more to that story
<sad_plan> because its crosscompiling. which means its uses those headers and libs in the outdir, then just copies everything over to /. massivly simplified though
<sad_plan> you should, atleast in theory, be able to copy /usr/bin/gcc to a new dir, and build something with it
<midfavila> i don't use gcc, and i'm not going to set up cross compiling
<midfavila> that defeats the entire point of my system, which is to reduce mechanical complexity as far as possible
<sad_plan> gcc was just an example in this case though :p