In message <BE3C11DB.12659%peter@boku.net>, Peter Eisch writes:
>On 2/18/05 8:37 PM, "Steven M. Bellovin" <smb@cs.columbia.edu> wrote:
>
>>>> 2.    pkgtools/pkg_chk:
>>>> 
>>>> pkg_chk -i
>>>> 
>>>> pkglint-4.05: version mismatch - pkglint-4.04
>>>> netpbm-10.26.3: version mismatch - netpbm-10.26.1
>>>> 
>>>> This tool can update your programs that need to be upgraded with:
>>>> 
>>>> pkg_chk -u (e.g.)
>>> 
>>> Great! That's what I was looking for!
>>> 
>> 
>> I don't recommend this path.  Note what it says about extra rebuilds in
>> the BUGS section.  A better path is to use pkgdepgraph:
>> 
>> lintpkgsrc -i >/tmp/out_of_date
>> pkgdepgraph -D /tmp/out_of_date >/tmp/delete
>> pkgdepgraph -R /tmp/out_of_date >/tmp/rebuild
>> pkg_delete `cat /tmp/delete`
>> sh /tmp/rebuild
>> 
>> The risk you take is that something won't rebuild...
>> 
>
>If there are work directories out there already, will this still "do the
>right thing" or should there be a pkgclean just before the rebuild?

I'd recommend starting with a clean tree.
>
>I'm trying to figure out how to keep a set of packages built in a single
>whack.  (Next would be how to stuff them onto an install disk...)
>

See pkg_comp, which will do builds in a chrooted environment.  But I've 
found it complex to set up.

		--Prof. Steven M. Bellovin, http://www.cs.columbia.edu/~smb