On 28/03/07 [EMAIL PROTECTED] said:
I am not sure you would want to do that, as
if it were to overlap with a normal portupgrade
the results may be interesting.
Yes, it's become plain to me that the pkgdb -L is working off of metadata that
was updated with the last cvsup, and not the packages
On 27/03/07 David J Brooks said:
Have you looked at 'man pkgdb'?
Yes.
I'm looking for how it works, not how to use it.
Mike
--
Michael P. Soulier [EMAIL PROTECTED]
Any intelligent fool can make things bigger and more complex... It
takes a touch of genius - and a lot of courage to move in the
On 27/03/07, Michael P. Soulier [EMAIL PROTECTED] wrote:
Hello,
I just upgraded portupgrade, and it recommended that I run pkgdb -L to look
for lost dependencies. This raised the question to me of what I should
regularly run in cron jobs to maintain the db.
Is it wise to put say, pkgdb -L into
Hello,
I just upgraded portupgrade, and it recommended that I run pkgdb -L to look
for lost dependencies. This raised the question to me of what I should
regularly run in cron jobs to maintain the db.
Is it wise to put say, pkgdb -L into a weekly cron? Anything else?
How are dependencies lost
On Tue, 27 Mar 2007, Michael P. Soulier wrote:
Hello,
I just upgraded portupgrade, and it recommended that I run pkgdb -L to look
for lost dependencies. This raised the question to me of what I should
regularly run in cron jobs to maintain the db.
Is it wise to put say, pkgdb -L into a weekly
On 27/03/07 [EMAIL PROTECTED] said:
I can't say I've used that option lately, but I'm pretty sure that what
you're experiencing occurs because stuff a) gets moved or b) gets removed.
Versioned port like lib/libnet10 for instance gets replaced by lib/libnet11
in the future for instance.
On Tuesday 27 March 2007 07:25:48 pm Michael P. Soulier wrote:
How are dependencies lost anyway? Beyond reading the source, is there a
document that tells me how pkgdb works?
Have you looked at 'man pkgdb'?
--
America is a melting pot. You know, where those on the bottom get burned,
and the
