> There is no rule for "make install" because plex86 is run in place--not
> installed to a separate directory. This is because of several things:
>
> 1) We don't distribute binaries, so we don't need the option to build into
> a location (which should be optional anyway, but I've noticed that RPM's
> don't like that)
That's why one can make them relocatable.
A properly-constructed "make install" step could put the binaries into
~plex86/bin or any other location the user chooses.
With an rpm, /usr/bin is a fine default location.
> 2)plex86 is development, so it doesn't make sense to copy the binaries
> (once compiled) to a different place on the machine than the local copy of
> the CVS--or to delete the local CVS entirely
Bad reasoning. Some people don't like to muddy their CVS tree.
> 3)plex86 isn't done yet, so it doesn't make any sense to go to a great
> effort setting up an install script for a finished product if there isn't
> one to install yet.
Has to be done some time. It's easy, makes it easier for others to test.
--
Cheers
John Summerfield
Microsoft's most solid OS: http://www.geocities.com/rcwoolley/
Note: mail delivered to me is deemed to be intended for me, for my disposition.
