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 11th May 2012
daemonfowl daemonfowl is offline
bsdstudent
 
Join Date: Jan 2012
Location: DaemonLand
Posts: 834
Default could mixing packages and ports problematize system integrity in this case ?

Hi everybody !

Could mixing packages and ports problematize system intergrity/stability when upgrading the OS and a few packages while still keeping compiled ports comparatively older (ie, ports tree) ?
(Please correct me if my question is *false* or ill-founded or .... )
Reply With Quote
  #2   (View Single Post)  
Old 11th May 2012
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by daemonfowl View Post
Could mixing packages and ports problematize system intergrity/stability when upgrading the OS and a few packages while still keeping compiled ports comparatively older (ie, ports tree) ?
What does Section 15 of the FAQ say about the differences between ports & packages?
Reply With Quote
  #3   (View Single Post)  
Old 12th May 2012
daemonfowl daemonfowl is offline
bsdstudent
 
Join Date: Jan 2012
Location: DaemonLand
Posts: 834
Default

I guess I was missing the anoncvs faq
Now the view is less smoggier .. truly the FAQ are the best healer.
Reply With Quote
  #4   (View Single Post)  
Old 12th May 2012
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by daemonfowl View Post
I guess I was missing the anoncvs faq
Now the view is less smoggier .. truly the FAQ are the best healer.
I don't know what this response says, nor do I understand what relevance it has on the original question.
Reply With Quote
  #5   (View Single Post)  
Old 12th May 2012
daemonfowl daemonfowl is offline
bsdstudent
 
Join Date: Jan 2012
Location: DaemonLand
Posts: 834
Default

I mean after all , the more I miss , the more I ask wrong questions ..
I was thinking what to do with those *compiled packages* and how to upgrade them etc when I upgrade then update all *packages* .. have you ever seen an incarnation of foolishness ? well it's me ..
Reply With Quote
  #6   (View Single Post)  
Old 12th May 2012
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by daemonfowl View Post
what to do with those *compiled packages* and how to upgrade them etc...
Okay, you're going to get the same answer as before. What does Section 15 of the FAQ say about upgrading packages?
Reply With Quote
  #7   (View Single Post)  
Old 13th May 2012
daemonfowl daemonfowl is offline
bsdstudent
 
Join Date: Jan 2012
Location: DaemonLand
Posts: 834
Default

that I can update packages with pkg_add -u ..
yet aren't compiled packages different in that unless I upgrade the ports tree with cvs , packages built by the ports system remain untouched ..... or is this another silly point of mine?
Reply With Quote
  #8   (View Single Post)  
Old 13th May 2012
ocicat ocicat is offline
Administrator
 
Join Date: Apr 2008
Posts: 3,318
Default

Quote:
Originally Posted by daemonfowl View Post
I can update packages with pkg_add -u ..
Correct. pkg_add -u will update packages if newer packages are available on PKG_PATH. It does not matter whether the currently installed packages come from a mirror site or were compiled locally.

Look at the contents of the package system database in /var/db/pkg. You will find version information & dependency information. You will not find information as to where the package came from being tracked.

What pkg_add -u will do is update packages depending upon whether a newer version is found on PKG_PATH. Yes, this may mean that a package installed from a locally installed port may get replaced with a newer package found on a mirror.
Quote:
or is this another silly point of mine?
Somehow you are wanting to make locally compiled ports somehow different. They aren't. The result of building ports are packages -- the very same packages which are available on the mirrors.

Whether your point is silly is immaterial. What is more of concern is where you come up with these incorrect ideas. You can help yourself by confirming your knowledge through study of the documentation. Developing the discipline to read & study before posting will help you grow technically. Simply coming to this site & posting questions which you have thought about for less than five minutes only makes you dependent upon whatever we impart to you. This kind of dependency is never going to get you very far. Ever.

Last edited by ocicat; 13th May 2012 at 04:37 PM.
Reply With Quote
  #9   (View Single Post)  
Old 13th May 2012
daemonfowl daemonfowl is offline
bsdstudent
 
Join Date: Jan 2012
Location: DaemonLand
Posts: 834
Default

Thanks for clearifying points and sorry if I'm too dumb to ask again :
Are the once compiled opera & httrack -for instance- gonna be upgraded too, following a pkg_add -u charm ?
* opera : being part of the ports tree
* httrack : not being part of the ports tree
Or will there be no difference the time when httrack is hosted in /usr/ports/www and compiled as it becomes a member and so can be upgraded as well ?
( Anyway, I can see that Opera dwells in /var/db/pkg .. whereas httrack doesn't and both were compiled and I can use both.. )
Reply With Quote
Old 13th May 2012
jggimi's Avatar
jggimi jggimi is offline
More noise than signal
 
Join Date: May 2008
Location: USA
Posts: 7,977
Default

  1. The ports tree builds packages.
  2. You have manually built and installed "httrack". Therefore, "httrack" is not a package and will not be affected by any of the package tools.
  3. If, in the future, "httrack" is added to the ports tree, your personal version of "httrack" will not be affected.
  4. If, in that future, you attempt to install an "httrack" package, the pkg_add will likely fail due to collisions with your pre-existing files from your custom, outside-the-tree build and install of "httrack".
  5. In that future, you would have to manually de-install your custom "httrack" from your OpenBSD system in order to install this future "httrack" package.
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
Question about removing ports/packages Daffy OpenBSD Packages and Ports 2 16th October 2010 09:06 AM
packages vs ports zelut FreeBSD Ports and Packages 17 28th October 2009 08:19 AM
Packages vs. Ports guitarscn OpenBSD Packages and Ports 3 1st October 2008 04:43 AM
Upgrading and rebuilding ALL packages/ports chill FreeBSD Ports and Packages 8 16th June 2008 04:55 AM
FAQ: FreeBSD Ports and Packages Carpetsmoker FreeBSD Ports and Packages 0 1st May 2008 03:38 PM


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