*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i use freebsd 5.3, but i'd like to have the binary packages available in freebsd 6.0 current, but i hate the old binaries for 5 and compiling firefox just produced one big bug and i'm sick of "rm firefox-bin.core" (although i'm not sayin that i expect less bugs with the 6.0 binaries)
I have read up on the whole thing, and i'd like some clarification, for someoen in my situation, who doesn't care to upgrading the system, but would like new *binaries* like firefox 1.0.7, do i still have to do cvsup using *-supfile? and buildworld and all that?
if i don't, great, please tell me how
if i do, is this the process:
use cvsup to get new src for the 6.0 system
make world and kerenl and install them with new src
i don't expect 6.0 to be any less buggy, just easier to get the newest binaries (for testing/using/etc).
if i get a binary say for firefox, i'll get the firefox 0.9.3 tbz when i do "pkg_add -r firefox". which i don't want.
now on freebsd.org/ports, there is a 1.0.7 tbz under the 6.0 current packages. i want my computer to automatically fetch that binary. and I wasn't clear on your "." comment, sorry. do i add that to a file?
I stand corrected about games/tank... whatever the problem was has been resolved and it does build now. But that is an example of how it sometimes matters to the ports tree which version of the system you are running. But usually it doesn't.
hmm, before, i just installed the freebsd 5.3 without ports, and then manually got ports.tar.gz to install to compile the firefox 1.0.7 i have now. i guess one has to cvsup the tree to get the pre-compiled binaries. thanks
The pkg_add program is going to try and get the version you have listed in INDEX-5 (or INDEX.db ... one or the other... they both contain the same data). If you upgraded your ports tree but see this problem you need to rebuild the INDEX file.
i can't find the config file to change this, and making PACKAGEROOT='ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-current/Latest/" does not help, the pkg_add will look inside "ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-current/Latest/pub/FreeBSD/ports/i386/packages-5.3-release/Latest/"
The environment variable PACKAGEROOT specifies an alternate location for
pkg_add to fetch from. The fetch URL is built using this environment
variable and the automatic directory logic that pkg_add uses when the -r
option is invoked. An example setting would be "ftp://ftp3.FreeBSD.org".
The environment variable PACKAGESITE specifies an alternate location for
pkg_add to fetch from. This variable subverts the automatic directory
logic that pkg_add uses when the -r option is invoked. Thus it should be
a complete URL to the remote package file(s).
From the manpage. set PACKAGESITE to "ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/i386/packages-current/Latest/"
If you read the manpage carefully you would see that PACKAGEROOT just changes the site itself "The fetch URL is built using this environment variable and the automatic directory logic that pkg_add uses..."
Confusingly enough... the PACKAGESITE variable "subverts the automatic directory
logic that pkg_add uses". Which is where your problem is coming into play.