03:01 <iceman[m]> Hi, I was going through the wayland package and checked the depends file. There's some dependencies which have make suffixed after them, are they supposed to be build time dependencies or something indicating that it is provided in the package's source and they need to be made from there and then subsequently build the actual package need?

04:12 <testuser[m]> Hi

04:12 <testuser[m]> iceman: make means build deps

04:13 <iceman[m]> Oh i c

04:14 <iceman[m]> well I went to wayland's website and check dependencies and drew the correlation later, but thanks for confirming 👍

05:31 <iceman[m]> was looking at some utilities, noticed many use `ninja` to build, but `ninja` doesn't exist in the repos and I seem to have it. Went through the kiss repos and noticed that it might have been build and installed (not as a KISS package) with wayland.

05:31 <iceman[m]> So anything that I package now can technically use `ninja` that's available on my system tho I can't put `ninja make` in the `depends` file. What would be the best course of action to fix this for me?

05:31 <iceman[m]> - package ninja myself and find every occurrence of pre-existing `ninja` and get rid of it

05:31 <iceman[m]> - just yolo it cuz it `ninja` already exists on system

05:39 <illiliti> ninja is provided by samurai

05:39 <illiliti> kiss-owns /bin/ninja

05:40 <iceman[m]> illiliti: owh

05:40 <iceman[m]> i c

05:41 <iceman[m]> hm hm, so meson, nodejs and swaybg on my machine need samurai

05:42 <iceman[m]> illiliti: would it be fine for me to list `samurai make` as a dependency just because I want ninja?

05:42 <illiliti> yes

05:51 <iceman[m]> LOL

05:51 <iceman[m]> I just realised I can do kiss help xyz

05:52 <iceman[m]> saw samurai readme page, i c

09:37 <sewn> Hi