DaemonForums  

Go Back   DaemonForums > OpenBSD > OpenBSD Packages and Ports

OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD.

Reply
 
Thread Tools Display Modes
  #1   (View Single Post)  
Old 21st August 2012
IdOp's Avatar
IdOp IdOp is offline
Too dumb for a smartphone
 
Join Date: May 2008
Location: twisting on the daemon's fork(2)
Posts: 1,027
Default finding package dependencies?

Quote:
Originally Posted by ocicat
... complete list of packages installed ...

... list of everything ...
I'm not trying to be overly argumentative , and it's certainly possible my understanding is lacking in experience, but I think the key words there are "complete" and "everything". Let me give an example first.

Suppose I already have 80 packages installed. Now I want to install another 5 packages. Due to dependencies let's suppose another 15 packages are also installed that way. So I installed 20 packages today for a total of 100 overall. And of those 20, I may at first only know what 5 of them are (or maybe a few more, but not all 20).

Now if I use pkg_info to get a complete list of everything, I can't really tell which are the new packages can I ? If I display the install messages for everything, then 4 out of 5 messages are likely to be ones I've already seen; not very efficient.

I could, of course, get a directory of /var/db/pkg, grep it for today's date, and sort things out that way. But that is getting into what I referred to as "doing it by hand", not using pkg_info.

Now one other thing to add. During a pkg_add, there can be errors, failures, etc. It's primarily for this reason that I like to do a large pkg_add inside of script. It gives me a record of all that happened and I can see exactly what went wrong, if anything. So, given that I have the typescript file there, an added benefit is being able to search it for the install messages from only the new packages that were added today.

Does that make sense or am I still missing something? Thank you for your critiques, they are welcome.

Last edited by IdOp; 21st August 2012 at 07:07 PM. Reason: spelling
Reply With Quote
  #2   (View Single Post)  
Old 21st August 2012
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Split from its parent thread. The original thread asked about displaying post-install messages. Discussion has morphed into focusing on identifying dependencies.
Quote:
Originally Posted by IdOp View Post
Now if I use pkg_info to get a complete list of everything, I can't really tell which are the new packages can I ?
If dependency information is important to you, pkg_info(1) may not be the best choice. To get information on dependencies, you may want to play with the print-build-depends & print-run-depends targets mentioned in ports(7).

Last edited by ocicat; 21st August 2012 at 06:15 PM. Reason: add clarity
Reply With Quote
  #3   (View Single Post)  
Old 21st August 2012
IdOp's Avatar
IdOp IdOp is offline
Too dumb for a smartphone
 
Join Date: May 2008
Location: twisting on the daemon's fork(2)
Posts: 1,027
Default

@ocicat: Thanks, it's good to know about that in general. However, I've never used ports, and my sense is that for my situation sticking with binary packages is the way to go. Given the reasoning in my last paragraph, the typescript file is a practical way for me to find targeted install messages without extra effort (until, of course, I delete the file )

@jggimi: I initially missed seeing your post in the parent thread. Thanks. I think my prior post in this thread replies to that as well.
Reply With Quote
  #4   (View Single Post)  
Old 21st August 2012
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by IdOp View Post
I've never used ports, and my sense is that for my situation sticking with binary packages is the way to go.
The targets only required the tree to be installed; no building is required.
Reply With Quote
  #5   (View Single Post)  
Old 21st August 2012
IdOp's Avatar
IdOp IdOp is offline
Too dumb for a smartphone
 
Join Date: May 2008
Location: twisting on the daemon's fork(2)
Posts: 1,027
Default

Quote:
Originally Posted by ocicat View Post
The targets only required the tree to be installed; no building is required.
Thanks, that sounds most useful in general. And I think the general situation is what is most important in this thread. For example, it is probably what applies to daemonfowl, who started the parent thread.

<digression>
Turning momentarily to my own situation, it turns out that in fact I do know what packages have been installed "today". That is because I've already downloaded the binary packages beforehand. (I do that as a result of slow Internet access.) So that explains why I wouldn't need to use ports for this. But again, most users' situations are probably quite different, and for them the ports tree may be a good way to go.
</digression>
Reply With Quote
  #6   (View Single Post)  
Old 23rd August 2012
backrow backrow is offline
Real Name: Anthony J. Bentley
Shell Scout
 
Join Date: Jul 2009
Location: Albuquerque, NM
Posts: 136
Default

Quote:
Originally Posted by IdOp View Post
Now if I use pkg_info to get a complete list of everything, I can't really tell which are the new packages can I ?

I could, of course, get a directory of /var/db/pkg, grep it for today's date, and sort things out that way. But that is getting into what I referred to as "doing it by hand", not using pkg_info.
/var/log/messages records which packages have been installed recently.

Code:
Aug 10 22:04:27 ponderosa pkg_delete: Removed mupen64plus-core-1.99.5
Aug 10 23:00:03 ponderosa pkg_add: Added mupen64plus-core-1.99.5
__________________
Many thanks to the forum regulars who put time and effort into helping others solve their problems.
Reply With Quote
  #7   (View Single Post)  
Old 23rd August 2012
IdOp's Avatar
IdOp IdOp is offline
Too dumb for a smartphone
 
Join Date: May 2008
Location: twisting on the daemon's fork(2)
Posts: 1,027
Default

Quote:
Originally Posted by backrow View Post
/var/log/messages records which packages have been installed recently.
Thank you! I didn't know about that, and it's good to know of "different roads to Rome", as they all have unique benefits and drawbacks, depending on the situation.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
K3B not finding writer. maxrussell FreeBSD General 5 7th February 2009 11:41 AM
finding files by uid carpman FreeBSD General 3 5th February 2009 07:51 PM
How to handle conflicting port dependencies? Aux FreeBSD Ports and Packages 2 29th September 2008 06:44 AM
how to check package dependencies? bsdnewbie999 OpenBSD Packages and Ports 5 31st July 2008 04:05 AM
hey, help finding something plz cheese11 FreeBSD General 3 20th June 2008 11:24 PM


All times are GMT. The time now is 07:23 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Content copyright © 2007-2010, the authors
Daemon image copyright ©1988, Marshall Kirk McKusick