Didier Kryn <kryn@???> writes:
> Le 02/03/2016 16:04, Steve Litt a écrit :
>> I'm constructing my wpa_supplicant toolset. So far it's 100% /bin/sh.
>> Installation involves nothing more than copying its directory tree
>> somewhere on your computer, and then, on your executable path, putting
>> a 1 line shellscript that calls the main program in my toolset with
>> argument $@.

[...]

>     This installation method is used almost consistently by
> Sabotage-Linux.

It's of no big use except if the files belonging to a particular package
have to be kept physically together because there's no other way to
identify them. I've been using this method for software developed as
part of my work and for infrastructure code needed by it and it indeed
works very nicely provided investing the fairly high amount of human
effort required by maintaining it is no problem.

Because this became impossible some years ago, I've then switched to
building (usually pretty bare-bones) Debian packages and found no reason
to regret that so far as this means I only have to maintain one central
package repository and can deploy these to any number of machines with
existing tools very easily.