On Oct-02, Nicholas Clark wrote: > $ make install > /home/nick/Install/bin/perl5.8.4 tools/dev/install_files.pl --buildprefix= > --prefix=/home/nick/Install/parrot --exec-prefix=/home/nick/Install/parrot > --bindir=/home/nick/Install/parrot/bin --libdir=/home/nick/Install/parrot/lib > --includedir=/home/nick/Install/parrot/include MANIFEST MANIFEST.generated | sh > > We have perl. Which is guaranteed to be on all platforms we build on. > So why are we making a big list of commands and then feeding them to Unix > shell? Which isn't going to be on all platforms that we build on.
Because long ago, when I implemented 'make install', I only did the minimum necessary to get RPM building working. And RPMs don't work so well on Windows, or so I hear. The "generate a script and pipe it through sh" approach is something I frequently use when cooking things up quickly, because you can develop without the pipe, and then when everything looks good, add it on and know what's going on. It's a nice way to get visibility into what something's doing. And the script itself uses forward slashes everwhere, so why bother pretending to be portable? Not that any of this matters. I've committed fixes to hopefully make it work portably. Of course, the MANIFEST.generated file is woefully incomplete, so the files actually installed aren't terribly useful.
