Date: Thu, 23 Feb 2006 08:15:46 -0600 From: "Donald J. O'Neill" <donaldjoneill@gmail.com> To: freebsd-questions@freebsd.org Cc: Ow Mun Heng <Ow.Mun.Heng@wdc.com> Subject: Re: Newbie Alert : pkg_add and packages Q (do not want to compile) Message-ID: <200602230815.46972.donaldjoneill@gmail.com> In-Reply-To: <1140667149.4762.30.camel@neuromancer.home.net> References: <1140659905.1984.20.camel@neuromancer.home.net> <200602222136.22120.donaldjoneill@gmail.com> <1140667149.4762.30.camel@neuromancer.home.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday 22 February 2006 21:59, Ow Mun Heng wrote: > On Wed, 2006-02-22 at 21:36 -0600, Donald J. O'Neill wrote: > > On Wednesday 22 February 2006 20:59, Ow Mun Heng wrote: > > > what about the dependency then? Ignore it? What if there are > > > "files" needed by xorg-clients? eg: libXX.so.Y and which is not > > > present in the new xterm? > > > > Since you want to replace it with a newer version, why are you > > worried about the dependencies. The newer version will take care of > > that. Of course, if you delete xterm and don't replace it, then you > > will have to handle the dependencies. > > So, I do pkg_del -f xterm and then a pkg_add -vr xterm-206_1 and it > will upgrade xorg-clients if needed? If yes, then Good. > No. It would only upgrade xterm. Xterm isn't dependent on xorg-clients. It's required by xorg-clients. So, that brings up a question. Are you really trying to upgrade xorg and xterm was the example you used? If that's the case, my advice would have been different. > > > > What you are trying to do is update using downloaded packages > > > > and that is going to work for you. You need to upgrade those > > > > packages using the ports system. > > > > > > IS or is not? > > > > Is or is not what? I don't understand what you're asking here. You > > need to use more than a 4 word question, of which 2 of the words > > are the same. It tends to be confusing. > > Sorry but You're confusing me too. Read your sentence "update using > downloaded packages and that is (?NOT?) going to work for you" > OK, I see what happened. I didn't put "not" in the sentence, as you pointed out. Since "not" is what I meant, I refused to see that it wasn't there, in fact my brain expected it to be there, and so when I looked at what you were asking, I saw it. Sorry. > > > Again, I don't want to compile it. I want the binary package. > > > It's available on the mirrors. > > > > No It's not. The port is available on the mirrors. So compile it, > > or leave the old one in place. > > lftp ftp.tw.frebsd.org > lftp ftp.tw.freebsd.org:/pub/FreeBSD/ports/i386/packages-6-stable/x11 > ls -l | grep xterm > lrwxr-xr-x Nov 28 09:12 xterm-206_1.tbz -> ../All/xterm-206_1.tbz > get xterm-206_1.tbz > quit > tar -v -t -f xterm-206_1.tar > -rw-r--r-- root/wheel 1560 2006-02-07 15:20:18 +CONTENTS > -rw-r--r-- root/wheel 42 2006-02-07 15:20:18 +COMMENT > -rw-r--r-- root/wheel 479 2006-02-07 15:20:18 +DESC > -r--r--r-- root/wheel 8654 2006-02-07 15:20:18 +MTREE_DIRS > -r--r--r-- root/wheel 1313 2006-02-07 15:19:55 > man/man1/resize.1.gz -r--r--r-- root/wheel 41772 2006-02-07 > 15:19:55 man/man1/xterm.1.gz -rwxr-xr-x root/wheel 10104 > 2006-02-07 15:19:54 bin/resize -rwxr-xr-x root/wheel 2118 > 2006-02-07 15:19:54 bin/uxterm -rws--x--x root/wheel 252996 > 2006-02-07 15:19:54 bin/xterm -r--r--r-- root/wheel 1527 > 2006-02-07 15:19:55 > lib/X11/app-defaults/UXTerm > -r--r--r-- root/wheel 6551 2006-02-07 15:19:55 > lib/X11/app-defaults/XTerm > -r--r--r-- root/wheel 4232 2006-02-07 15:19:55 > lib/X11/app-defaults/XTerm-color > > > > I'm proficient with the CLI, and being a long time Linux person, > > > I'm sad to say that FreeBSD ports/packages is really confusing to > > > me. > > > > Use Windows instead. All that takes is money. > > Why the sarcasm? > At that moment, I had a lapse of brain power. My fingers took control of the keyboard without interference from the part of my brain which says "DON'T do this. It's wrong to say something like that." And then they hit the send button and it was too late to retract it. I believe: once something is said or done, it cannot be unsaid or undone, it may be fixed, forgiven, but not forgotten. I'm sorry for the sarcasm. > > > > Available packages are not as up to date as the ports system > > > > is. > > > > > > Again, the package _is_ available and I've verified it. > > > Thanks > > > > I'm sorry. You've verified the port was available. The package is > > not. I just checked. > > See above. I too do my own verification before shooting emails out to > mail lists > OK, I see where you were looking. I looked in the wrong place. When you look in the right place, yes, it's there. > > At this point, I'm going to close my ears eyes to you. You've been > > given advice by me and others > > and I thank you and them for it. > > Thanks again. I hope that by this time, you've received enough information to do what you wanted to do. One thought just occurred to me. What is the output from 'uname -a', mine is: FreeBSD pres1750.mylan.net 6.1-PRERELEASE FreeBSD 6.1-PRERELEASE #0: Wed Feb 8 08:20:10 CST 2006 root@pres1750.mylan.net:/usr/obj/usr/src/sys/PRES1750-i386 i386 You'll see that it has "FreeBSD 6.1-PRERELEASE" in it. If yours has "FreeBSD 6.0-RELEASE" in it. Then you can't install a package using "pkg_add -r 'some package'" for a package built for "FreeBSD 6.0-STABLE". You need to have 6.0-STABLE in order to install packages built for 6.0-STABLE. Don
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602230815.46972.donaldjoneill>