On Thu, 4 Aug 2005, Lars Nordlund wrote:

> On Wed, 03 Aug 2005 20:51:39 +0200 (CEST)
> Havard Eidnes <he@uninett.no> wrote:
>
>>> Wouldn't pkg_chk do the work?
>>
>> Just to answer this, I tried it once, and was disappointed by the
>> result -- as I recall it ended up compiling several packages more
>> than once.
>
> Are you perhaps referring to the problem described at the end of the
> pkg_chk manual page?

 	That issue should be resolved in the more recent (last couple
 	of months) version of pkg_chk.

> I usually use pkg_chk like this when I want to update my system:
>
> pkg_chk -g    To generate an uptodate pkgchk.conf
> pkg_chk -r    Remove all packages not up to date and also packages
>              depending on them
> pkg_chk -ask  Add missing packages by building from source. Keep
>              going even though some package fails to build. I can
>              fix that later.
>
> (a bit unsure about the -ask flags. Perhaps an u should be there
> instead of the a (-usk). It has been a while since I last used pkg_chk,
> actually.)

 	That is spot on. The 'a' will add, the 'u' update.

 	You should also be able to run pkg_chk -usk and it will
 	generate a temporary pkg_chk.conf, then run the -r, and -ask
 	passes for you :)

-- 
 		David/absolute       -- www.NetBSD.org: No hype required --