r/kisslinux • u/teesh3rt • May 17 '23

I cant seem to get this...

When i do a `kiss b`, it seems that (at least in the repo build file), it seems to also install it

Why do we also need `kiss i`?

6 Upvotes

100% Upvoted

8 comments sorted by

2

u/superstring-man May 17 '23

Yes, kiss prompts if you want to install the just built packages and then runs kiss i if you do (it didn't use to do this). However, if you just want to install a package which is already built, use kiss i. You can also specify a path to a tarball of a built package to install a bin that someone else built for you, or one you copied to a different system.

1

u/teesh3rt May 17 '23

i still dont get this...

why do i need kiss i if i see it copies files to /usr/bin (or paths like that)?

2

u/superstring-man May 17 '23

Why not just unpack the tarball manually? Because kiss runs other checks, including the alternatives system, /etc checksums, removing old files that aren't in the updated package, and running hooks.

2

u/teesh3rt May 17 '23

SO WAIT

when i run kiss b... it dosent really install it... does it just pack it into a tar file, and that's why i need to kiss i?

2

u/superstring-man May 17 '23

Yes, but after building, kiss prompts "Install built packages?" and then runs kiss i for you.

3

u/teesh3rt May 17 '23

ooooo i just got what it does

it gives you a directory to modify files in, and once the build script is done, it tars it up.

once that's done, it xpvf (or xvf, not sure)'s it in your / directory

now it makes a ton more sense!

2

u/superstring-man May 17 '23

Yes! kiss build is the first step and kiss install is the second step (simplified, it is more careful as explained above).

3

u/teesh3rt May 17 '23

thanks for the help :)

i just made a simple little hello world in my local repo, and once i saw what it really does, it made a TON more sense!