A simple ports question...
How would you install a port that had dependencies that were older than identical items on your system? For example, you install portx that requires depend1.1 -- you have depend1.2 on your system. Running 'make install clean' will generate an error code stating that you have an OLDER version -- despite the fact that you actually have a newer version. I believe this is simply because version numbers don't match. 'FORCE_PACKAGE_REGISTER' will install and register the older version as well as the newer version. THis is less than desirable behavior. I looked through the ports man page to find a variable that would ignore dependencies. If such a variable exists would the port most likely still run (assuming all dependencies are present albeit newer versions)? Thanks, Mak. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A simple ports question...
On Thursday 20 October 2005 15:25, makisupa wrote: How would you install a port that had dependencies that were older than identical items on your system? For example, you install portx that requires depend1.1 -- you have depend1.2 on your system. This will happen if you have an out-of-date ports tree, and have installed packages built against a newer tree. Try bringing your tree up-to-date with cvsup or portsnap. See the handbook for details. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A simple ports question...
Thanks for the reply... My ports tree is up to date -- i believe the problem (if you want to call it that) is that I installed gnome 2.12 from package at marcuscom (on a 6.0 RC1 system -- i needed 6.0 for some HW issues). I therefore have newer versions of certain files than many of the ports in the current tree are expecting. Does this sound like a reasonable explanation? Your answer is the one everyone has been telling me for the last week. And i truly appreciate the response. I keep thinking i'm asking the question wrong :) I would understand this answer if the dependencies i had were OLDER than what the port was looking for...but I have a NEWER version. For example, while installing pan2 it needs glib-2.6.6. I have glib-2.8.3. How can i properly get this port installed? === Installing for glib-2.6.6 === glib-2.6.6 depends on file: /usr/local/bin/perl5.8.7 - found === glib-2.6.6 depends on executable: pkg-config - found === glib-2.6.6 depends on shared library: intl - found === Generating temporary packing list === Checking if devel/glib20 already installed === An older version of devel/glib20 is already installed (glib-2.8.3) You may wish to ``make deinstall'' and install this port again by ``make reinstall'' to upgrade it properly. If you really wish to overwrite the old port of devel/glib20 without deleting it first, set the variable FORCE_PKG_REGISTER in your environment or the make install command line. *** Error code 1 Stop in /usr/ports/devel/glib20. *** Error code 1 Thanks, I'm really not trying to beat a dead horse here. I have read all relevant sections of the handbook and man pages but the obvious seems to be escaping me. I truly appreciate the help mak. On Thu, 2005-10-20 at 16:06 +0100, RW wrote: On Thursday 20 October 2005 15:25, makisupa wrote: How would you install a port that had dependencies that were older than identical items on your system? For example, you install portx that requires depend1.1 -- you have depend1.2 on your system. This will happen if you have an out-of-date ports tree, and have installed packages built against a newer tree. Try bringing your tree up-to-date with cvsup or portsnap. See the handbook for details. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A simple ports question...
On Thursday 20 October 2005 16:35, makisupa wrote: Thanks for the reply... My ports tree is up to date -- i believe the problem (if you want to call it that) is that I installed gnome 2.12 from package at marcuscom (on a 6.0 RC1 system -- i needed 6.0 for some HW issues). I therefore have newer versions of certain files than many of the ports in the current tree are expecting. Does this sound like a reasonable explanation? Not entirely. FreeBSD releases all share the same ports tree, and neither gnome 2.12 nor glib-2.8.3 are in it. It sounds like you picked up a work-in-progress, development version of Gnome rather than simply the current version built against a 6.0 based system Your answer is the one everyone has been telling me for the last week. And i truly appreciate the response. I keep thinking i'm asking the question wrong :) I would understand this answer if the dependencies i had were OLDER than what the port was looking for...but I have a NEWER version. For example, while installing pan2 it needs glib-2.6.6. I have glib-2.8.3. How can i properly get this port installed? It really depend why you got packages for 2.12 rather than the current ports version. If gnome 2.10.2. is broken on 6.0-RC1, then it's going to be tricky. The fact that make install in the pan2 directory causes glib to build suggest that some port isn't compatible with glib-2.8.3. On the other hand if you simply got the 2.12 version because it was there, I would suggest removing it and installing 2.10.2 - presumably pointyhat has a compatible version. Alternately portmanager will probably be able to handle the reversion through the port system. You also have the options of waiting for 2.12 to hit the ports tree, or doing without gnome. Forcing the glib-2.6.6 registration will overwrite the glib-2.8.3 version which may break gnome. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
