Nicolas Williams wrote:
> On Wed, Feb 27, 2008 at 10:41:20AM -0800, Mike.Sullivan at sun.com wrote:
>
>> >From Nicolas.Williams at sun.com Wed Feb 27 10:10:19 200
>> Then again, if you're putting it into the proto area anyway then moving &
>> deleting I don't know why you just do the install into the right spots in
>> the first place, then delete the bits you don't want? Though perhaps
>> there's a lot more to delete individually then.
>>
>
> Because that means knowing what those bits are. What if the next
> version of SQLite3 installs lemon (a parser generator)?
>
> I'd much rather have full control over what gets installed.
>
Yes, it does mean knowing what those bits are. If it delivers a new
file or stops delivering a file, you will find out the first time you
run nightly(1). The proto area and packages won't match. If you cherry
pick (install-sfw), and don't pay attention, you can end up leaving
things out. When I integrate or upgrade a component in SFW, I build
that component and install just that component into it's own proto area
using it's install target (cd $(VER) ; make ROOT=/tmp/component install)
so that I can figure out just what needs to be packaged, changed in the
packaging, and/or removed from the proto area after (cd $(VER) ; make
install).
-Norm
