OESF Portal | OESF Forum | OESF Wiki | LinuxPDA | #planetgemini chat on matrix.org | #gemini-pda chat on Freenode | #zaurus and #alarmz chat on Freenode | ELSI (coming soon) | Ibiblio


Welcome Guest ( Log In | Register )

Reply to this topicStart new topic
> A Quirky Way To Keep Ports Updated, by having two ports tree side by side?
post Sep 18 2007, 06:16 AM
Post #1

Group: Members
Posts: 1,998
Joined: 16-April 04
From: the Netherlands && /dev/null
Member No.: 2,882

Hi, these days i've been thinking of a relatively painless way to keep ports updated. I mean painless in two senses: it is easy to implement, and it does little harm to the system.

So here is a proposal. I'm gonna try it. But before that i'd love to hear how other folks think.

It sounds a bit complicated to newbies but i hope those who have experience with building understand what I am talking about. Please bear with me. Anyway here is the scenario:

Since I started porting hundreds of ports for 4.2 in the ports tree a few weeks ago, and I've seen ports being updated almost every day, on one hand I want those latest stuff in the ports tree, on the other hand I don't want to break compatibility of the existing setup and packages. And replacing the whole ports tree, which shouldn't not happen so frequently unless it's a wholesale system upgrade (say 4.2 to 4.3), may break a lot of existing packages, especially when it comes to essential stuff like gtk, qt, etc. What should I do?

Here is one possibility:
While keeping the existing ports tree where I've been porting stuff, create a new ports tree directory side by side.
So let's say, if the current one is /usr/ports, then I downloaded the latest snapshot ports.tar.gz and extract it to /usr/ports_latest.
Then when I see a particular port being updated and I feel like updating the existing package to that new version, I visit the new ports tree and locate the packages that I want to build.
To play safe, they should be basically individual programs but not those "very essential stuff". My bet is that updated packages *usually* don't really depend on the very latest version of the libraries (such as gtk and qt) but have a relatively flexible requirement (such as gtk2 2.8 UP but not necessarily the very latest version).
Then I can try building the new version in this latest ports tree.
If building is successful, I can replace the existing one with pkg_add -r.
This way I can test if this newer package will work or will break anything.
If this is just an ordinary program like file manager or window manager, I guess it should work right away.
If it does cause trouble, then I can simply fall back to the older one.
It seems in principle then I can use the latest ports safely with little risk.
The only tradeoff I see is the additional space taken by the extra ports tree.

What do you think? Or is there any misconception here?
Go to the top of the page
+Quote Post

Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:


RSS Lo-Fi Version Time is now: 18th January 2019 - 06:08 AM