<iceman[m]>
where the custom environment is passed various envvars along with a DESTDIR, what can I expect this variable to be? Is it just `/` or `/usr` or `/usr/bin` ?
<iceman[m]>
s/os-prober/something/, s/<//, s/>//
<testuser[m]>
iceman: DESTDIR is set to that path in the temporary build directory which is tar'd up after the build finishes
<testuser[m]>
Eg /tmp/kiss/1234/pkg/firefox
<testuser[m]>
the tarball.is generated by tarring up this dif
<testuser[m]>
dir
<iceman[m]>
what can I expect in that location? directories like $DESTDIR/usr/lib, $DESTDIR/usr/share $DESTDIR/usr/bin etc?
<iceman[m]>
I'm sorry for asking too many questions about DESTDIR but the wiki page is quite abstract and doesn't have specifics
<iceman[m]>
thats it
<iceman[m]>
testuser:
<testuser[m]>
No that directory is empty
<testuser[m]>
The build script is what fills it
<testuser[m]>
eg make DESTDIR="$1" PREFIX=/usr
<testuser[m]>
In most cases the makefile would make /usr/bin and install a binary there, similarly for /usr/lib
<testuser[m]>
then kiss install literally just unpacks this directory on /
<testuser[m]>
basically it just contains new files to be added to the filesystem
<SdVb>
testuser[m] any news on dylan?
<iceman[m]>
oh so say, DESTDIR="whatever"
<iceman[m]>
then my build can create directories and place binaries and library files and other pages etc in the local directory along with setting all user permissions
<iceman[m]>
kiss is going to archive DESTDIR into a tar and extract it in `/`
<iceman[m]>
just rephrasing to make sure I'm understood it right
<testuser[m]>
lol i don't know him personally, maybe he setup a farming business or something SdVb
<testuser[m]>
iceman: build script doesn't set perms
<testuser[m]>
But other stuff is correct
<iceman[m]>
post-install then?
<iceman[m]>
testuser[m]: what if I just use `install` to copy and set perms, is that non-conventional?
<testuser[m]>
what perms? execute bit?
<testuser[m]>
755
<iceman[m]>
yep
<testuser[m]>
that's done by default by most build systems, otherwise you can do chmod +x; cp
<shokara>
yeah you can use the install(1) program instead, I think it's only non-conventional when the program doesn't have a build system with an equivalent "make install"
<iceman[m]>
`install -Dm755 xyz $DESTDIR/usr/bin`
<iceman[m]>
if I did this in `build` script, does it matter?
<testuser[m]>
install -Dm755 works too but some people are anal about posix compliance and install command isn't specified by posix
<testuser[m]>
so it might break for that 1 guy rolling his own coreutils lol
<shokara>
that 1 guy can replace it with cp and chmod
<testuser[m]>
it's fine imo, it's used by many packages anyways
<iceman[m]>
shokara: I'm packaging os-prober and it doesn't have the install target
<iceman[m]>
* have the `install, * install` target
<shokara>
yeah install(1) wouldn't be non-conventional then
<testuser[m]>
btw be sure to quote variables
<testuser[m]>
And lint scripts with shellcheck
<iceman[m]>
yeah
<iceman[m]>
testuser[m]: i did not know about this
<iceman[m]>
testuser[m]: i learned this the hardware some years ago
<testuser[m]>
BTW the build scripts don't even have to be in shell you can write them in js if you want
<iceman[m]>
testuser[m]: ik
<iceman[m]>
shell is easy
<iceman[m]>
cuz familiarity
<iceman[m]>
and I read the wiki page
<iceman[m]>
it says DSL instead of specific kind of shell
<iceman[m]>
i'm going through dylan's pure sh bible, and is the [[ ]] non-posix? I can't find anything like it, only [ ]
<iceman[m]>
ok read some manuals apparently it's bash/zsh stuff
<iceman[m]>
test or [] is the way to go
<testuser[m]>
Shellcheck will point this out
<rohan>
testuser[m]: if i wanna use my NVIDIA card just for gaming in kiss i can use it?
<rohan>
i mean using steam with flatpak and a NVIDIA card for it
<rohan>
or i will need a dual boot?
<testuser[m]>
You could but your host would be running wayland anyways
<testuser[m]>
also you'd still need atleast the kernel module for nvidia
<iceman[m]>
huh lmao wtf did I just get an error about modprobe being unable to find headers
<iceman[m]>
interesting, efibootmgr says EFI variables are not supported on this system while non-chroot (host) efibootmgr dumps proper info as it should
<iceman[m]>
iceman[m]: and kiss modprobe is looking for host kernel version directory instead of local