07:13 <testuser[m]12> Hi

09:13 <Ogromny> Hi

12:19 <Ogromny> Hum how do you update git package ?

12:20 <Ogromny> I mean, I have neovim (git) installed but when I do `kiss u` it seems that everything is up to date

12:21 <Ogromny> I can do `kiss b $(kiss l | grep "git-1" | cut -d" " -f1 | xargs)` but I will rebuild everything even if there's no update

12:21 <Ogromny> s/I will/it'll/

12:22 <testuser[m]12> That's the only way

12:22 <testuser[m]12> manually updated

12:25 <Ogromny> That's sad

13:24 <Guest91> noocsharp: https://voidlinux.org/packages/?arch=x86_64&q=wayclip

19:25 <wael[m]> can variables exported by a kiss hook be read by KISS to be forwarded to the build?

19:28 <ioraff> no, unfortunately, since the hook is executed rather than sourced. you'll need to have the hook insert the exports into the build file

19:30 <wael[m]> wouldn't that overwrite the existing build file?

19:30 <wael[m]> or do you mean to have to insert the variables manually into the build files?

19:32 <ioraff> yes. I make a backup of the original to /tmp and then restore it upon build failure or completion

19:32 <ioraff> https://git.owenrafferty.com/bin/file/kh.html

19:33 <wael[m]> interesting

19:33 <wael[m]> i only need to set 3 variables, so i guess i can have a pre-install file in the package directory to set that variable?

19:34 <wael[m]> or is that just executed and not sourced too?

19:34 <ioraff> the hooks in the package directory that are executed are post-install and pre-remove

19:35 <ioraff> do the variables have anything to do with the build?

19:35 <wael[m]> they set the compiler

19:37 <ioraff> as far as I know, you can either run CC=... kiss ... or insert CC=... in the build file.

19:37 <wael[m]> thing is, its for many packages, so im simply trying to save like 10 kilobytes lol.

19:39 <ioraff> as per the hook I sent, you can add each package in a case statement

19:40 <wael[m]> does your hook directly modify the build file and save the old to a temporary file, and once the build is complete it brings the old build file back?

19:41 <ioraff> yes

19:41 <wael[m]> oh wow your hook displays the time

19:41 <wael[m]> i didnt know hooks could be that useful

19:42 <wael[m]> i will try to do something similar, thanks!!

19:45 <wael[m]> ~~also by similar i meant shamelessly copying~~

19:57 <ioraff> as did I, from dylan. reminds me to add a license

20:01 <wael[m]> is it still a good idea to instead add the variables directly to the build files or to do what the hook does

20:03 <ioraff> that's up to you. it's just my personal preference that environmental variables be modified via a hook, since they only need to be prepended to the build file, while all other changes warrant a fork of the package

20:06 <wael[m]> you know what? i guess it wouldnt hurt to add a few variables to each build file

20:07 <wael[m]> unless...?

20:07 <wael[m]> does sed support inplace ?

20:08 <ioraff> busybox sed does, yes. as does ed, which I use. the backup is only for "safety"

20:09 <wael[m]> hmmmmmmmmmmmmmmmmmmmmmm

20:09 <wael[m]> okay fuck it

20:44 <wael[m]> is there a way to prevent kiss from cleaning? i want to make simple post-compilation changes to the build file, and i have to constantly recompile for whatever change i did.

20:57 <soliwilos> You want to keep the temporary build dir? I think setting KISS_DEBUG=1 does that.

21:01 <wael[m]> not exactly, i want to make use of the existing build dir for tiny changes. however the build directories are by processor, i think a better solution is to use ccache to speed it up some more for recompilation.

21:01 <wael[m]> how can ccache be used with KISS otherwise?

21:02 <wael[m]> nvm found the wiki page for it.

21:51 <phoebos> wael[m]: i like to put a `sh >/dev/tty` somewhere into the build script

21:52 <phoebos> i also tweaked kiss so that you can run `kiss continue` from within /tmp/$$/pkg/pkg/ to finish the build after installing