|
OpenBSD Packages and Ports Installation and upgrading of packages and ports on OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
porting Firefox 3.5.15 to OpenBSD 4.8
I'm interested in trying to build firefox 3.5.15 on a just installed 4.8 amd64 system.
I am familiar with basic compiling and Slackware build scripts but the OpenBSD system looks to be more complex. I'm thinking about renaming the firefox35 port to a backup and reconstructing an updated port using the cvs makefile, patches, files etc and using pkg_create. Although there has been mention of reviving binary updates I have yet to find any so I am assuming you need to compile I found http://www.openbsd101.com/updating.html#u6. It looks like I would need to update the base system then proceed with ports. At this time there are no patches for 4.8 so a full cvs update doesn't seem necessary - do I need maintain the same revision? Is this a good approach? Any pointers appreciated Last edited by shep; 3rd November 2010 at 07:54 PM. Reason: added openbsd101 link |
|
|||
While indeed backporting newer versions of Firefox is tempting, it is not something that should be done by a novice.. you will run into dependency issues eventually, and if you're unwilling to resolve them yourself you'll be unable to continue.
If bleeding edge packages are your primary concern, consider following snapshots as an alternative.. binary packages are made available on several mirrors. One major problem with this is eventually packages will not work for an older snapshot, usually this happens when base libraries are bumped (..API/ABI change in libc) and you'll need to upgrade/reinstall a newer snapshot. A lot of this is in the FAQ, and you can decide what more fits your usage requirements.. if maintaining stable backports is something you wish to do, then that is your prerogative. |
|
|||
I took a crack at it and did accomplish an update of the 4_8 patch branch with the following out of date ports
Quote:
Also I notice that the Firefox35 update has not made it yet into the patch branch. If there is a single command to do the lot of them I will probably hold off until the firefox35 update shows up - how long does it typically take? |
|
|||
Hijacked discussion moved to its own thread.
When you have the urge to change topics within a thread, please create a new thread. Hijacking is so uncool. |
|
|||
Sorry, it was not my intent to hijack the thread and actually the original post was on "Firefox and stable ports" and the link you posted in your reply actually pointed to the Makefile that I understand was tagged with Revision 1.40.2.1.
Quote:
Quote:
I appreciate trying to make searches more efficient but the new thread is still about updating firefox35 while staying in stable/patch branch. Just because I responded to some advice to used a less complex port does that make it an uncool hijack of a thread? |
|
|||
Yes, this is why your change in discussion topic warranted splitting the thread.
Your question, while valid, went in a different direction & most likely discussion was going to continue to diverge from that of the OP. If discussion were to get further mired into building details, the OP might give up thinking everything is way too complicated, where building was not really part of his question at this point. Yes, my decision was based in part on where I anticipated discussion was likely to go, & I wanted to minimize any growing confusion already taking place. Perhaps you (or others) don't agree with my action. That's fine. Let us then agree to disagree. |
|
|||
I am always impressed with how quickly the daemonformums administrators/moderators respond to posts and realize that they read and process large quantities of text on a daily basis. Again, I appreciate your efforts and will restate it was not my intent to hijack the thread.
|
|
||||
Quote:
Quote:
As I see it, you have four choices: a) While waiting, attempt to backport the -current port yourself. If you are successful, you can contact $MAINTAINER and let him, her, or they know you've got a working backport, and ask them to review what you have done and make recommendations and corrections so that your work can be commited to the patch branch. b) Send an Email to $MAINTAINER and demand they drop whatever they are doing and get this done, because for you, it is the most critical thing in the world. c) Wait patiently, in the hopes that $MAINTAINER will get around to it before the next set of security fixes for Firefox are published. d) Use the version of FF available to you, and don't worry be happy. ---- I recommend a,c, or d. Option b is considered rude. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
OpenBSD on laptop using Firefox | gpatrick | OpenBSD General | 3 | 22nd December 2009 04:41 PM |
Switch linuxbase for porting software | indiocolifa | FreeBSD Ports and Packages | 6 | 28th March 2009 07:05 PM |
Upgrading firefox to firefox 3 -keeping plugins+bookmarks | kasse | FreeBSD Ports and Packages | 11 | 5th July 2008 01:34 PM |
porting gnome got samba error. | bsdnewbie999 | OpenBSD General | 2 | 19th June 2008 02:06 AM |
Porting Firefox to qt - progress? | caesius | FreeBSD Ports and Packages | 9 | 5th June 2008 11:13 PM |