To explain in a short way, my package manager need to run some command inside another system. For that it run a generated sh script under the system via chroot. This way make things easier for the user who implement a software installer (packager). They don’t need to think about the implementation of the path.
Because the path at some point (it’s quite technical at this point) is related about 2 things:
-Is it a path related to the chroot or not?
-The package manager have the installation by chroot mode enabled or not ?
Sorry It’s just I don’t want to write a full explanation of the process, it’s too long
You need just to understand that ISM manage the installation before any chroot are possible, that make the things even more tricky.
It not a standard package manager, it really build everything from zero
Just to show you, after my last update , this is now how look an installer for a software , for example Gcc. I think I really made the API very easy to read and understand
It’s still technical of course , but much easier to read