From: Rene Rivera (grafik666_at_[hidden])
Date: 2003-08-21 23:48:36
[2003-08-19] Administrator wrote:
>> Don't you think that if
>> bjam install
>> did nothing and reported success we'd have a lot of confused users?
>I'm not saying don't tell what's happening, no. I want it to tell me what
>exactly it's installing and where. I'm just advocating a position where
>install does not necessarily build, but just looks at what is already
>then, quite verbosely in the present tradition, installs it in $PREFIX.
>Also, if nothing is built, it needs to say that out loud, and give the user
>the chance to opt out.
After thinking about it a bit... doing it that way has more problems than
the solution is worth. There are just too many things that can go wrong by
taking that simple approach. And the more things can go wrong the more
things we have to check for. Problems dealing with which files the user
realy meant to install, wethere there are any left over files from other
builds in the way, etc.
So that leaves creating an options file to use when asked to install. And I
think there's a not too difficult way to do that -- cross-fingers ;-)
Any other suggestions out there?
-- grafik - Don't Assume Anything
-- rrivera (at) acm.org - grafik (at) redshift-software.com
-- 102708583 (at) icq
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk