macintoshzoom's questions regarding kdeutils

[macintoshzoom]

Thanks, will see all that tomorrow.

Mac

Josh Grosse wrote:
> Within one hour, "Mac" asked the same question three different ways, with
> three different subject lines, and in the third one, cc'ed the KDE list, which
> I have dropped from this reply, as this has nothing to do with KDE, rather,
> with port/package management on OpenBSD.
> 
> Question #1:
> 
> On Tue, 12 Aug 2008 09:44:23 -0600, macintoshzoom wrote
> 
>> Can't safely update to kdeutils-3.5.9p0 (use -F update to force it)
>> #
>>
>> How should I do "(use -F update to force it)" from my ports folder, 
>> there is no "make -f update" command?
> 
> Answer #1:  
> 
> Use pkg_add(8).  Note the "-F update" option in the man page.  Then, after
> remembering if you manually updated files in /usr/local for that particular
> package, use pkg_add to update the package.  You might use something like:
> 
> # env PKG_PATH=/usr/ports/packages/<arch>/all/ pkg_add -ri -F update kdeutils
> 
> Question #2:
> 
> On Tue, 12 Aug 2008 10:19:16 -0600, macintoshzoom wrote
> 
>> blah blah Can't safely update blah blah
>> #
>> does this means kdeutils-3.5.9p0 is already updated?
> 
> Answer #2:
> 
> No.  It means after building the package, make was unable to install it as
> there are install/deinstall scripts involved.  See Answer #1.
> 
> On Tue, 12 Aug 2008 10:42:35 -0600, macintoshzoom wrote
>> ...does this means kdeutils-3.5.9p0 is already updated?
> 
> No, see Answers #1 and #2.
> 
>> If so I don't need to execute /usr/local/bin/update-desktop-database,
>>  unless It can reset, clean or improve something, if I discover what.
>>
>> Does anyone knows what exactly it does this 
>> /usr/local/bin/update-desktop-database ?
> 
> You can find out which package the file belongs to by issuing:
> 
> $ pkg_info -E /usr/local/bin/update-desktop-database
> 
> Once you learn that, you can see the complete list of files associated with
> that package by issuing:
> 
> $ pkg_info -L <whatever the package is>
> 
> If you output that to a pager, such as more(1) or less(1), e.g.:
> 
> $ pkg_info -L <package> | less
> 
> You can then browse the files to see if there's a man page, an info file, or
> documentation that may lead you to discover what the file does.
> 
> I hope this helps.
>