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 15th August 2012
daemonfowl daemonfowl is offline
bsdstudent
 
Join Date: Jan 2012
Location: DaemonLand
Posts: 834
Default a question regarding post-install messages ..

Hi all !

Sometimes when installing packages I overlook post-install messages of importance .. is there a way to show them back by -for instance- pkg_name or something ?

Thanks.
Reply With Quote
  #2   (View Single Post)  
Old 15th August 2012
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,975
Default

$ man pkg_info

/message
Reply With Quote
  #3   (View Single Post)  
Old 15th August 2012
daemonfowl daemonfowl is offline
bsdstudent
 
Join Date: Jan 2012
Location: DaemonLand
Posts: 834
Default

Thank you jggimi !! Thank you Savior !!
How much do I owe you ?? :-)
Reply With Quote
  #4   (View Single Post)  
Old 15th 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

If you're installing a lot of packages, possibly in part as a result of recursive installs of dependencies, you may not know what all packages have been installed ... as they fly by. You could figure it out "by hand" but that could be tedious. In this kind of situation I like to do the installation inside of a script(1) session. That makes it easy to go back and look at everything that happened, including any messages displayed.
Reply With Quote
  #5   (View Single Post)  
Old 21st August 2012
daemonfowl daemonfowl is offline
bsdstudent
 
Join Date: Jan 2012
Location: DaemonLand
Posts: 834
Default

Thank you for the note , IdOp !
Reply With Quote
  #6   (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
If you're installing a lot of packages, possibly in part as a result of recursive installs of dependencies, you may not know what all packages have been installed ... as they fly by.
While script(1) is a very handy tool which can be used to determine what packages have been installed, pkg_info(1) provides the same information more succinctly; no need to sift through the reams of output collected by script(1)(1).
Reply With Quote
  #7   (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
While script(1) is a very handy tool which can be used to determine what packages have been installed, pkg_info(1) provides the same information more succinctly; no need to sift through the reams of output collected by script(1)(1).
I agree that pkg_info is the preferred and direct method for getting the info in question. But that does assume that you know what packages have been installed, doesn't it? The point I was trying to add is that sometimes a lot of stuff gets installed recursively as dependencies, and unless you're a speed reader with photographic memory you may not know all of which packages were installed on this occasion. script helps me deal with that. As a side-benefit the install messages are right there. Of course, you don't have to read them from the typescript, you could note which packages had messages and then read them with pkg_info, but that would be a bit too circuitous for me.

Last edited by IdOp; 21st August 2012 at 04:10 PM.
Reply With Quote
  #8   (View Single Post)  
Old 21st August 2012
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,975
Default

Even easier, IdOp - try "$ cd /var/db/pkg; pkg_info -M * | less"
Reply With Quote
  #9   (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 agree that pkg_info is the preferred and direct method for getting the info in question. But that does assume that you know what packages have been installed, doesn't it?
No, issuing pkg_info(1) with no arguments will display a complete list of packages installed in /var/db/pkg.
Quote:
The point I was trying to add is that sometimes a lot of stuff gets installed recursively as dependencies, and unless you're a speed reader with photographic memory you may not know all of which packages were installed on this occasion.
...& issuing pkg_info(1) with no arguments provides a list of everything which has been installed through pkg_add(1) -- either directly or indirectly as dependencies.

script(1) is a good friend. pkg_info(1) can be too.
Reply With Quote
Old 21st August 2012
daemonfowl daemonfowl is offline
bsdstudent
 
Join Date: Jan 2012
Location: DaemonLand
Posts: 834
Default

yet another cool friend : tee :-)
Reply With Quote
Old 22nd August 2012
LeFrettchen's Avatar
LeFrettchen LeFrettchen is offline
Marveled user
 
Join Date: Aug 2012
Location: France
Posts: 405
Default

Quote:
Originally Posted by IdOp View Post
But that does assume that you know what packages have been installed, doesn't it?
Nope.
You can do a listing of your packages :
Code:
# pkg_info | more
Reply With Quote
Old 22nd August 2012
daemonfowl daemonfowl is offline
bsdstudent
 
Join Date: Jan 2012
Location: DaemonLand
Posts: 834
Default

LeFrettchen , it's not about listing *installed* packages but *the_just_recently_installed* ones as dependencies to the package that was targeted with pkg_add ..
so Idop is RIGHT :-) and script helps here in case of errors or something not only because one needs to know a package dependencies (ocicat already made it clear how to)
Reply With Quote
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

@ LeFrettchen : Thanks for your input. It may be a bit confusing because, due to the changing direction of discussion in this thread, the issue on this point was split over to a new thread here. Hopefully that will clarify much.
Reply With Quote
Old 23rd August 2012
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by daemonfowl View Post
...it's not about listing *installed* packages but *the_just_recently_installed* ones as dependencies to the package that was targeted with pkg_add ..
Now wait a minute, daemonfowl. Your initial question in this thread was, & I quote verbatim:
Quote:
Sometimes when installing packages I overlook post-install messages of importance .. is there a way to show them back by -for instance- pkg_name or something ?
No where in that question is any mention of dependencies. You asked about getting post-install messages. pkg_info(1) addresses that question as has been pointed out by jggimi, myself, & LeFrettchen. What you are now parroting is the digression IdOp introduced which was the reason for splitting the thread.

The hijacking train was leaving the station, & you weren't going to let it get away without being on it?

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
Post install help wokko Other BSD and UNIX/UNIX-like 16 21st May 2010 09:47 AM
FreeBSD-8.0-BETA1 Install Question. MetalHead FreeBSD Installation and Upgrading 0 9th July 2009 06:23 PM
Newbie question about ajunta install Johnny2Bad Programming 3 8th June 2008 05:57 PM
post-install green text w/o shell standardFoo NetBSD Installation and Upgrading 5 2nd May 2008 11:12 PM
First Post.. Woot!! --- An obvious Makefile question..? roundkat OpenBSD Packages and Ports 2 2nd May 2008 03:05 PM


All times are GMT. The time now is 04:11 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