Re: how remove old lib in portupgrade -fr libxcb
On Sat, 2009-01-31 at 16:55 -0600, Scot Hetzel wrote: On Sat, Jan 31, 2009 at 4:12 PM, Sebastien Chassot si...@fsfe.org wrote: hi, I've portupgrade my system and as said in UPDATING I launched the portupgrade -rf libxcb. I did it twice and my applications still are linked to libxcb.so.1 and libxcb.so.2 I found out that libxcb.so.1 is in /usr/local/lib/compat/pkg/ and libxcb.so.2 is in /usr/local/lib/ I don't know how remove this old lib and despite lot of portupgrade -f xxx it's still there. How can I solve this issue? Sounds like several of the libraries that your applications require are still linked to the old libxcb.so.1. Use this to find all libraries that are still depending on libxcb.so.1 (for i in /usr/local/lib/lib*.so ; do echo -n $i: ; ldd $i | grep libxcb.so.1 ; echo ; done) | grep libxcb libxcb.log Then rebuild all ports that contain these libraries. I didn't rebuild all ports listed by your command but even after a clean reinstall, portupgrade -f,... ports that I've rebuild remain linked to libxcb.so.1 and libxcb.so.2 Something stick somewhere... I don't know how compat work but are port looking for old lib in build process to stay compat and could cause this issue? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unhappy Xorg upgrade
I agree with all you say. This sort of thing is the achilles heel of ports. I'd like to see a beta port exist side by side with the old version, for massive ports like X, KDE, etc, until things stabilize. Alex Goncharov wrote: No -- a patch might (*should*, for this kind of a disruptive change) be put together: I'd install it on my systems, I'd try it and report problems, I'd revert back -- easily. This is for many Is willing to be the testers -- we'd repeat this again as many times as necessary, before the commit. -- James Bailie ji...@mammothcheese.ca http://www.mammothcheese.ca ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Blender 2.48 fails to build
Hi Marcus, graphics/blender fails to build: # make [...] gmake all in source/gameengine/GamePlayer/ghost Link /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/bin/blender c++ -DNDEBUG -O2 -fno-strict-aliasing -pipe -march=athlon-xp -I/usr/local/include -DBUILD_DATE='2009-02-01' -DBUILD_TIME='14:59:49' -DBUILD_REV='' -DBUILD_PLATFORM='freebsd-7.1-i386' -DBUILD_TYPE='dynamic' /usr/ports/graphics/blender/work/blender-2.48/source/creator/buildinfo.c -c -o /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/buildinfo.o -DNAN_BUILDINFO /usr/ports/graphics/blender/work/blender-2.48/source/creator/buildinfo.c:36: warning: deprecated conversion from string constant to 'char*' /usr/ports/graphics/blender/work/blender-2.48/source/creator/buildinfo.c:37: warning: deprecated conversion from string constant to 'char*' /usr/ports/graphics/blender/work/blender-2.48/source/creator/buildinfo.c:38: warning: deprecated conversion from string constant to 'char*' /usr/ports/graphics/blender/work/blender-2.48/source/creator/buildinfo.c:39: warning: deprecated conversion from string constant to 'char*' /usr/ports/graphics/blender/work/blender-2.48/source/creator/buildinfo.c:40: warning: deprecated conversion from string constant to 'char*' mkdir -p /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/bin c++ -o /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/bin/blender /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/buildinfo.o /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/creator/libcreator.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/src/libsrcpublisher.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/bsp/lib/libbsp.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/boolop/lib/libboolop.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/SoundSystem/lib/libSoundSystem.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/ghost/lib/libghost.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/string/lib/libstring.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/render/librender.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/radiosity/libradiosity.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/opennl/lib/libopennl.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/superlu/lib/libsuperlu.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/python/libpython.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/blenkernel/libblenkernel.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/decimation/lib/libdecimation.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/blenloader/libblenloader.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/blenpluginapi/libblenpluginapi.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/nodes_shd/libnodes_shd.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/nodes_cmp/libnodes_cmp.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/nodes/libnodes.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/imbuf/libimbuf.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/blenlib/libblenlib.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/iksolver/lib/libiksolver.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/opennl/lib/libopennl.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/superlu/lib/libsuperlu.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/avi/libavi.a /usr/local//lib/libjpeg.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/blender/gpu/libgpu.a /usr/local//lib/libGLEW.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/gameengine/bloutines/libbloutines.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/gameengine/blconverter/libblconverter.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/gameengine/blphys/common/libcommon.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/gameengine/ketsji/libketsji.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/gameengine/blconverter/libblconverter.a /usr/ports/graphics/blender/work/blender-2.48/obj/freebsd-7.1-i386/gameengine/blconverter/libblconverter.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/solid/lib/libsolid.a /usr/ports/graphics/blender/work/blender-2.48/../lib/freebsd-7.1-i386/solid/lib/libsolid_broad.a
Re: Unhappy Xorg upgrade
On Jan 31, 2009, at 2:43 PM, bf wrote: Alex: I can understand your frustration. The Xorg update, although it helps a lot of people, is inevitably going to cause problems for some, because it is run by so many people in different ways with a wide variety of hardware. It's comparable in some ways to updating the OS, and despite the hard work by the FreeBSD Xorg team (and they did put in a lot of work), there are bound to be some difficulties. But all is not lost, even though you will have to spend some time recovering: Yes, you can get the old versions of the ports: you can use cvs (in the base system) or the port ports-mgmt/portdowngrade (which is basically a wrapper for cvs) to checkout the old versions, which are still present in the cvs repository. You can resume your automatic port updates, and then just copy the old versions of the Xorg ports over the new ones (having saved them in some other directory tree where they won't be overwritten by csup), or just not checkout the newer versions in the first place (for example, place all of the xorg ports in your refuse file, or just use cvs to checkout a list of individual installed ports that are not part of Xorg, rather than using csup collections). Alternatively, you could download the entire cvs repository (both cvs and the latest versions of csup can do this) and checkout the versions you want from your local copy of the repository. If you write a script to do this, the whole process won't take much longer than a normal csup update. For more on this, read the cvs manual ( http://ximbiot.com/cvs/ manual/ ) or the relevant parts of the FreeBSD handbook ( http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ anoncvs.html ). In addition to the individual Xorg ports and metaports that you use, you will have to either use older versions of Mk/bsd.port.mk and Mk/bsd.xorg.mk, or use libmap.conf(5) to fool your ports into thinking that you have the new gl and xaw libraries installed. Remember also that one or two of the old ports have disappeared (xorg-protos, for example). For what it's worth, I used similar methods to use the new Xorg when it was still in Florent's git repository with the regular ports tree for several months. Also, for some time I used the old xorg-server (1.4.x) with the other new Xorg ports without any obvious problems. And if the Xorg nv(4x) driver is giving you problems, you can try the Xorg vesa(4x) driver, or the nvidia drivers from ports (x11/nvidia-driver). Good luck, b. FWIW, nvidia-driver in ports is relatively stable, but has a tendency to hardlock in certain situations (I can think of cases with dualhead Xinerama enabled displays running xscreensaver or finishing up a movie with mplayer with the xv driver, where stuff would livelock). The newest stable works extremely well, but the new libGL.so isn't ABI compatible with the one packaged by nvidia, so things like mesa-demos will fail to compile because -lpthread is now required at compile time for the compat5x + libGL.so junk. I've submitted a request on the nvidia-forums to finally update the driver to use at least compat-6x and to remove the GIANT lock from the driver, but the more voices voting for this the merrier :)! The link for the forum page is: http://forums.nvidia.com/index.php?showtopic=87932 . Thanks, -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Blender 2.48 fails to build
On, Sun Feb 01, 2009, Philipp Ost wrote: Hi Marcus, graphics/blender fails to build: [...] /usr/local//lib/libopenal.a(libopenal_la-x86_cpu_caps_prk.o)(.text+0x4e): In function `_alDetectCPUCaps': : undefined reference to `_alDetectx86CPUCaps' /usr/local//lib/libopenal.a(libopenal_la-mixaudio16_mmx_prk.o)(.text+0xf24e): In function `MixAudio16_MMX_1': : undefined reference to `_alMMXmemcpy' gmake[1]: *** This looks like your audio/openal library installation is broken and blender's failing due to some missing symbols within the openal library. Did you activate some OPTION knobs on installing audio/openal and if so, which were that? If some were enabled, try to reinstall audio/openal with all OPTION knobs disabled and then rebuild graphics/blender. Regards Marcus pgp6S7KzmzCZG.pgp Description: PGP signature
USB port
I am having problems printing to my USB port using the Fortran compiler. Printing to my parallel port works fine. What do I need? Thanks, Milton Laikin milton...@aol.com **Great Deals on Dell Laptops. Starting at $499. (http://pr.atwola.com/promoclk/10075x1217883258x1201191827/aol?redir=http://www.dell.com/co ntent/products/features.aspx/laptops_great_deals#63;c=us%26cs=19%26l=en%26s=d hs%26#126;ck=anavml) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
How to start KDM since recent xorg Updates?
Hi there, I've started kdm via /etc/ttys since years: [...] #ttyv8 /usr/X11R6/bin/xdm -nodaemon xterm on secure #ttyv8 /usr/local/bin/kdm -nodaemon xterm on secure ttyv8 /usr/local/bin/kdm-bin -nodaemon xterm on secure Since the recent xorg-updates I had to rebuild my xorg.conf and removed any keyboard and mouse since it is auto-detected by xorg. Starting X by startx works, keyboard and mouse will be auto-detected. KDM started by init comes up without any mouse and keyboard attached. Interestingly the Hotkeys like Ctrl+F1 still work but the X11 emergency brake Ctrl+Alt+Backspace doesn't. Hitting Num-Lock toggles the LED. Mouse doesn't move. I disabled moused as mouse will be detected by hald. hald is running. The emergency exit to the console works by hitting Ctrl+F1. Logging in as root and kill kdm-bin results in a restart of kdm-bin and X11 by init, as expected. After this kdm has mouse and keyboard support and I can log in. This works every time (when started via /etc/ttys). So I guess, kdm+x11 has to be started AFTER hald is running and after a console is logged in. I tried https://www.bsdwiki.de/KDM#Startskript_.28Mit_rc.conf.29 without success (added hald in the REQUIRE-Line) to get it up after hald. This messes everything up (no escape to console, no getty running etc), I have to recover via ssh. WHAT is the problem here and HOW do YOU startup kdm? Is this a general problem or just a problem with my setup? Regdards Raphael -- -- Raphael Becker r...@uugrn.org http://rabe.uugrn.org/ GnuPG:E7B2 1D66 3AF2 EDC7 9828 6D7A 9CDA 3E7B 10CA 9F2D .|.|.|.|.|.|.|.. pgpZR25GfDUDc.pgp Description: PGP signature
Re: missing tinderbox/scripts/sql/values.lp
On 2009-01-31 00:51:55, mahonm...@googlemail.com wrote: Creating package /var/ports/packages/All/tinderbox-3.1.2_2.tbz Registering depends: p5-DBD-Pg-2.10.7 postgresql-client-8.2.11 gettext-0.17_1 libiconv-1.11_1 p5-DBI-1.60.4 p5-Storable-2.18 p5-version-0.76 perl-5.8.9. Creating bzip'd tar ball in '/var/ports/packages/All/tinderbox-3.1.2_2.tbz' tar: tinderbox/scripts/sql/values.lp: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 *** Error code 1 Seriously, noone? The pkg-plist specifies this mysterious values.lp file but having downloaded and extraced the tarball manually from marcuscom.com, this file is nowhere to be seen. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unhappy Xorg upgrade
On Sat, 2009-01-31 at 16:25 -0500, Alex Goncharov wrote: ,--- You/vehemens (Sat, 31 Jan 2009 11:53:58 -0800) * | In general when upgrading, you take your chances. If a port upgrade | fails, you should fall back to what worked. So, a *fundamental* (practically an OS component) port is brought in -- and it disables my system. What is my way of action? Right -- install the old packages, taken from an FTP site (is there a way to get the previous source, that is all the ports/*/*/Makefile files? Csup can only go forward -- or can it go back?) When I install the old packages, I can no longer rebuild and install new (say `csup'ed on 2009-03-01) port components, as one whole -- I can only do it selectively, excluding from the upgrade most X-dependent things. That sucks and will lead to a problem earlier or later. Will combination of sysutils/portdowngrade and HOLD_PKGS variable in /usr/local/etc/pkgtools.conf accomplish what you are trying to accomplish? -- Alexandre Sunny Kovalenko ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unhappy Xorg upgrade
On Saturday 31 January 2009 04:20:26 pm Alex Goncharov wrote: ,--- You/vehemens (Sat, 31 Jan 2009 13:54:42 -0800) * | On Saturday 31 January 2009 01:25:21 pm Alex Goncharov wrote: | So, a *fundamental* (practically an OS component) port is brought in | -- and it disables my system. What is my way of action? Right -- | install the old packages, taken from an FTP site (is there a way to | get the previous source, that is all the ports/*/*/Makefile files? | Csup can only go forward -- or can it go back?) | | You ignored the first part of the email which is that the ports | system is flawed due to the lack of a stable versus current branch. The FreeBSD model as what it is and I, for one, prefer it to Linux distros' models. In other words what you call a flaw, I call a virtue. Your missing the point. This has nothing to do with Linux. The issue is that that while src has a stable versus current branch, there is no stable branch for ports. The result is major updates are almost always problematic. | It seems to me that you want to run a stable branch, while the ports | tree is effectively a current branch. If somebody tells me that running the new X on my computers will be better if I switch the base system from STABLE to CURRENT, I'll do it in a heartbeat. (In fact one of my other systems does run CURRENT, only I never installed X there -- I don't use that system as a front end.) The issue is with the ports approach, not the base system (aka src) approach. See above comments. | When I install the old packages, I can no longer rebuild and install | new (say `csup'ed on 2009-03-01) port components, as one whole -- I | can only do it selectively, excluding from the upgrade most | X-dependent things. That sucks and will lead to a problem earlier or | later. | | I never update /usr/ports directly. I have a separate csup ports | area. When I update, I save the old ports tree and replace it with | a new one. If a problem occurs, I can fall back to the old tree or | pieces of it. An interesting model -- but how would you be better off falling back to the old ports tree in case of a bad (for you) new X? Yes, you could rebuild and return to using the old X. Then what? Would you be able to keep up with ports upgrades. You wouldn't be able to keep other updates unless you manully patched the tree, but you would be able to use the system until it's fixed. You may assume that X is going to be fixed -- but what if not, in, say a year? Your kidding me right?? | Well, it depends on which ports you are updating. All. Your saying that you build every port including the language options and never had a problem in the last 18 months until the xorg update ?!?!? | If you only run X, then I would expect your statement to be correct. Not sure what you mean here: nobody runs only X. It's impossible. To be precise, it's the xorg port. So yes it's possible. | | And last, many of the video drivers have little if any support. If | | you have something other then ati/intel/nivdia, you should expect | | problems. Input drivers are in a similar state. | | Both my systems I've been reporting problems with are using the `nv' | driver: | |$ grep /modules/drivers /var/log/Xorg.0.log |(II) Loading /usr/local/lib/xorg/modules/drivers//nv_drv.so | | One system (Dell Latitude) could not be made operational with the new | X at all; the other has garbage in the windows and the captive mouse | pointer -- both issues new in the new X. | | See above :) Which point? :-) All of them. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unhappy Xorg upgrade
,--- Alexandre \ (Sun, 01 Feb 2009 12:03:06 -0500) * | When I install the old packages, I can no longer rebuild and install | new (say `csup'ed on 2009-03-01) port components, as one whole -- I | can only do it selectively, excluding from the upgrade most | X-dependent things. That sucks and will lead to a problem earlier or | later. | Will combination of sysutils/portdowngrade and HOLD_PKGS variable | in /usr/local/etc/pkgtools.conf accomplish what you are trying to | accomplish? `--* I'll try something of that nature (not today) with your and other people's advice. Thank you! -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unhappy Xorg upgrade
,--- You/vehemens (Sun, 01 Feb 2009 10:34:50 -0800) * | On Saturday 31 January 2009 04:20:26 pm Alex Goncharov wrote: | ,--- You/vehemens (Sat, 31 Jan 2009 13:54:42 -0800) * | | | On Saturday 31 January 2009 01:25:21 pm Alex Goncharov wrote: | | So, a *fundamental* (practically an OS component) port is brought in | | -- and it disables my system. What is my way of action? Right -- | | install the old packages, taken from an FTP site (is there a way to | | get the previous source, that is all the ports/*/*/Makefile files? | | Csup can only go forward -- or can it go back?) | | | | You ignored the first part of the email which is that the ports | | system is flawed due to the lack of a stable versus current branch. | | The FreeBSD model as what it is and I, for one, prefer it to Linux | distros' models. In other words what you call a flaw, I call a | virtue. | | Your missing the point. Oh well, my fault then. | This has nothing to do with Linux. The issue is that that while src | has a stable versus current branch, there is no stable branch for | ports. The result is major updates are almost always problematic. Any data points to support the last statement? | | It seems to me that you want to run a stable branch, while the ports | | tree is effectively a current branch. | | If somebody tells me that running the new X on my computers will be | better if I switch the base system from STABLE to CURRENT, I'll do it | in a heartbeat. (In fact one of my other systems does run CURRENT, | only I never installed X there -- I don't use that system as a front | end.) | | The issue is with the ports approach, not the base system (aka src) approach. | See above comments. I am missing the point here, again. | | When I install the old packages, I can no longer rebuild and install | | new (say `csup'ed on 2009-03-01) port components, as one whole -- I | | can only do it selectively, excluding from the upgrade most | | X-dependent things. That sucks and will lead to a problem earlier or | | later. | | | | I never update /usr/ports directly. I have a separate csup ports | | area. When I update, I save the old ports tree and replace it with | | a new one. If a problem occurs, I can fall back to the old tree or | | pieces of it. | | An interesting model -- but how would you be better off falling back | to the old ports tree in case of a bad (for you) new X? Yes, you | could rebuild and return to using the old X. Then what? Would you be | able to keep up with ports upgrades. | | You wouldn't be able to keep other updates unless you manully patched the | tree, but you would be able to use the system until it's fixed. What the ETA for the new X fix? | You may assume that X is going to be fixed -- but what if not, in, say | a year? | | Your kidding me right?? No. You *know* that it is going to be fixed in a year? If yes, what's the source of your knowledge? What resources are going to be dedicated to work on my three problems? | | Well, it depends on which ports you are updating. | | All. | | Your saying that you build every port including the language options and never | had a problem in the last 18 months until the xorg update ?!?!? Yes, I am saying exactly this. I happen not to run Gnome or KDE. | | If you only run X, then I would expect your statement to be correct. | | Not sure what you mean here: nobody runs only X. It's impossible. | | To be precise, it's the xorg port. So yes it's possible. Hm, let's see: Information for xorg-server-1.5.3_2,1: Depends on: ([ I exclude the X things ]): Dependency: expat-2.0.1 Dependency: openssl-0.9.8j Dependency: pciids-20081012 Dependency: e2fsprogs-libuuid-1.41.3_1 Dependency: python25-2.5.2_3 Dependency: pkg-config-0.23_1 Dependency: libpthread-stubs-0.1 Dependency: libiconv-1.11_1 Dependency: gettext-0.17_1 Plenty of non-xorg things are needed for xorg, right? And if I build from the sources, I also need gmake, bison, autoconf etc. | | | And last, many of the video drivers have little if any support. If | | | you have something other then ati/intel/nivdia, you should expect | | | problems. Input drivers are in a similar state. | | | | Both my systems I've been reporting problems with are using the `nv' | | driver: | | | |$ grep /modules/drivers /var/log/Xorg.0.log | |(II) Loading /usr/local/lib/xorg/modules/drivers//nv_drv.so | | | | One system (Dell Latitude) could not be made operational with the new | | X at all; the other has garbage in the windows and the captive mouse | | pointer -- both issues new in the new X. | | | | See above :) | | Which point? :-) | | All of them. Ah, I got you now. -- Alex -- goncharov.a...@gmail.com -- ___ freebsd-ports@freebsd.org mailing list
Call for Testing KDE 4.2 for FreeBSD
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Howdy Guys, The KDE FreeBSD team is happy to announce the first public Call for Testing for KDE 4.2. Over the past weeks we have focused on the complex and very time consuming task to get KDE 4.2 running. What is new: Where KDE 4.1 was, according to the development team, aimed at casual users, KDE 4.2 is billed as a compelling offering for the majority of end users. There have been further enhancements to the plasma desktop with new applets allowing better desktop customisation. The configuration options for the desktop have also been expanded and the revamped system tray shows reports from every conceivable process, from system messages to the status of large downloads. The KWin window manager has learned a couple of new tricks. By default, it now switches on 3D and compositing effects automatically, on suitable hardware and manages these effects autonomously, without the aid of Compiz. With the help of the new Kephal library, the window manager now offers additional options for running multiple monitors. The Dolphin file manager has been partly revised, and should now be easier to use. As part of the Google Summer of Code, KMail has been redesigned, resulting in both a better appearance and better IMAP support. The KDE browser Konqueror also includes several new features. New supported languages include Arabic, Icelandic, Basque, Hebrew, Romanian, Tajik and several Indian languages (Bengali India, Gujarati, Kannada, Maithili, Marathi) indicating a rise in popularity in this part of Asia. Some note: The CFT is now without FreeBSD 6.4 support. We will see what we can do over the week now but I do not promise that we can get this fixed. If you want to help us, your patches are welcome. We suggest that you exit from KDE4 before you update, backup your ~/.kde4 configuration dir and start with a clean config. New Ports: arabic/kde4 l10n misc/kde4-l10n-eu hebrew/kde4-l10n misc/kde4-l10n-is misc/kde4-l10n-ro misc/kde4-l10n-tg Please read UPDATING-area51 before you start your update. To get KDE 4.2: try svn co https://kf.athame.co.uk/kde-freebsd/trunk/area51/ /path/to/area51 More info here: https://kf.athame.co.uk/access.php Here few screenshots: http://miwi.bsdcrew.de/screens/kde42/ I'd like to say thanks to all helpers and submitters on the kde-freebsd@ mailinglist. That's all for the moment. Happy Testing! - - Martin (on behalf of the KDE FreeBSD team) - -- +---+---+ | PGP: 0x05682353 | Jabber : miwi(at)BSDCrew.de | | ICQ: 169139903 | Mail : miwi(at)FreeBSD.org | +---+---+ | Mess with the Best, Die like the Rest! | +---+---+ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkmGDeMACgkQFwpycAVoI1PKVACfSuwnKyQYuPT3Kobd2bwa8rTq KlcAoIaUm74uxBXse5+yL+wWP1Gc8tbg =U6x9 -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unhappy Xorg upgrade
,--- You/Matthew (Sun, 1 Feb 2009 14:48:15 -0600) * | On Sat, Jan 31, 2009 at 04:25:21PM -0500 I heard the voice of | Alex Goncharov, and lo! it spake thus: | Csup can only go forward -- or can it go back?) | | You can specify a date in a supfile since, like, ever. `-* Yes, other people have already pointed this out and I just got the code as of 2009.01.23.12.00.00 -- four hours before the first submission of the new X. Now I just need to think through my next steps :-) Thank you! -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: how remove old lib in portupgrade -fr libxcb
On Sun, Feb 01, 2009 at 09:02:17PM +0100, Sebastien Chassot wrote: On Sat, 2009-01-31 at 16:55 -0600, Scot Hetzel wrote: Sounds like several of the libraries that your applications require are still linked to the old libxcb.so.1. Use this to find all libraries that are still depending on libxcb.so.1 (for i in /usr/local/lib/lib*.so ; do echo -n $i: ; ldd $i | grep libxcb.so.1 ; echo ; done) | grep libxcb libxcb.log Then rebuild all ports that contain these libraries. I did another try portupgrade -frP libxcb and I stop it after few hours. I maybe shouldn't but I did cos everything seems still linked to libxcb.so.1 (?) ... I'm really lost... ;( nothing work anymore and I don't know what to do. Just an idea: your command is 'portupgrade -frP', so what packages are you installing? Is it possible that some of your packages are built against the old libxcb? If that is the case, then reinstalling them will not change their link to the old version. -- greg byshenk - gbysh...@byshenk.net - Leiden, NL ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unhappy Xorg upgrade
On Sat, Jan 31, 2009 at 04:25:21PM -0500 I heard the voice of Alex Goncharov, and lo! it spake thus: Csup can only go forward -- or can it go back?) You can specify a date in a supfile since, like, ever. -- Matthew Fuller (MF4839) | fulle...@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ On the Internet, nobody can hear you scream. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: how remove old lib in portupgrade -fr libxcb
On Sat, 2009-01-31 at 16:55 -0600, Scot Hetzel wrote: Sounds like several of the libraries that your applications require are still linked to the old libxcb.so.1. Use this to find all libraries that are still depending on libxcb.so.1 (for i in /usr/local/lib/lib*.so ; do echo -n $i: ; ldd $i | grep libxcb.so.1 ; echo ; done) | grep libxcb libxcb.log Then rebuild all ports that contain these libraries. I did another try portupgrade -frP libxcb and I stop it after few hours. I maybe shouldn't but I did cos everything seems still linked to libxcb.so.1 (?) ... I'm really lost... ;( nothing work anymore and I don't know what to do. --- libxcb-before.log 2009-02-01 20:25:33.0 +0100 +++ libxcb-after.log2009-02-01 20:25:33.0 +0100 (...) -/usr/local/lib/libgdkmm-2.4.so:libxcb.so.1 = /usr/local/lib/compat/pkg/libxcb.so.1 (0x28e2c000) +/usr/local/lib/libgdkmm-2.4.so: libxcb.so.1 = /usr/local/lib/compat/pkg/libxcb.so.1 (0x28e2d000) -/usr/local/lib/libgtkmm-2.4.so:libxcb.so.1 = /usr/local/lib/compat/pkg/libxcb.so.1 (0x29205000) +/usr/local/lib/libgtkmm-2.4.so:libxcb.so.1 = /usr/local/lib/compat/pkg/libxcb.so.1 (0x29206000) -/usr/local/lib/libpangomm-1.4.so: libxcb.so.1 = /usr/local/lib/compat/pkg/libxcb.so.1 (0x28723000) +/usr/local/lib/libpangomm-1.4.so: libxcb.so.1 = /usr/local/lib/compat/pkg/libxcb.so.1 (0x28724000) (...) I discovered the utility libchk -v and my system is in this state ... Binaries that are linked with: /usr/local/lib/libxcb.so.2 /usr/X11R6/bin/gsynaptics /usr/X11R6/bin/gsynaptics-init /usr/X11R6/bin/syndaemon /usr/X11R6/bin/xglyph /usr/X11R6/bin/xorgconfig /usr/X11R6/bin/xrx /usr/X11R6/libexec/totem-plugin-viewer /usr/local/bin/gsynaptics /usr/local/bin/gsynaptics-init /usr/local/bin/syndaemon /usr/local/bin/xglyph /usr/local/bin/xorgconfig /usr/local/bin/xrx /usr/local/lib/browser_plugins/totem/libtotem-basic-plugin.so /usr/local/lib/browser_plugins/totem/libtotem-complex-plugin.so /usr/local/lib/browser_plugins/totem/libtotem-cone-plugin.so /usr/local/lib/browser_plugins/totem/libtotem-gmp-plugin.so /usr/local/lib/browser_plugins/totem/libtotem-mully-plugin.so /usr/local/lib/browser_plugins/totem/libtotem-narrowspace-plugin.so /usr/local/lib/libGL.so.1 /usr/local/lib/libX11.so.6 /usr/local/lib/libwebkit-1.0.so.1 /usr/local/lib/libxcb-atom.so.1 /usr/local/lib/libxcb-aux.so.0 /usr/local/lib/libxcb-composite.so.0 /usr/local/lib/libxcb-damage.so.0 /usr/local/lib/libxcb-dpms.so.0 /usr/local/lib/libxcb-event.so.1 /usr/local/lib/libxcb-glx.so.0 /usr/local/lib/libxcb-icccm.so.1 /usr/local/lib/libxcb-image.so.0 /usr/local/lib/libxcb-keysyms.so.0 /usr/local/lib/libxcb-property.so.1 /usr/local/lib/libxcb-randr.so.0 /usr/local/lib/libxcb-record.so.0 /usr/local/lib/libxcb-render-util.so.0 /usr/local/lib/libxcb-render.so.0 /usr/local/lib/libxcb-reply.so.1 /usr/local/lib/libxcb-res.so.0 /usr/local/lib/libxcb-screensaver.so.0 /usr/local/lib/libxcb-shape.so.0 /usr/local/lib/libxcb-shm.so.0 /usr/local/lib/libxcb-sync.so.0 /usr/local/lib/libxcb-wm.so.0 /usr/local/lib/libxcb-xevie.so.0 /usr/local/lib/libxcb-xf86dri.so.0 /usr/local/lib/libxcb-xfixes.so.0 /usr/local/lib/libxcb-xinerama.so.0 /usr/local/lib/libxcb-xprint.so.0 /usr/local/lib/libxcb-xtest.so.0 /usr/local/lib/libxcb-xv.so.0 /usr/local/lib/libxcb-xvmc.so.0 /usr/local/lib/xine/plugins/1.24/xineplug_vo_out_xcbshm.so /usr/local/lib/xine/plugins/1.24/xineplug_vo_out_xcbxv.so /usr/local/libexec/totem-plugin-viewer (...) Binaries that are linked with: /usr/local/lib/compat/pkg/libxcb.so.1 /usr/X11R6/bin/baobab /usr/X11R6/bin/bonobo-browser /usr/X11R6/bin/bug-buddy /usr/X11R6/bin/canberra-gtk-play /usr/X11R6/bin/dasher /usr/X11R6/bin/eog /usr/X11R6/bin/evince /usr/X11R6/bin/evince-thumbnailer /usr/X11R6/bin/evolution /usr/X11R6/bin/file-roller /usr/X11R6/bin/gcalctool /usr/X11R6/bin/gconf-editor /usr/X11R6/bin/gdm-screenshot /usr/X11R6/bin/gdmflexiserver /usr/X11R6/bin/gedit /usr/X11R6/bin/gegl /usr/X11R6/bin/gimp-2.6 /usr/X11R6/bin/gimp-console-2.6 /usr/X11R6/bin/gimptool-2.0 /usr/X11R6/bin/gkbd-indicator-plugins-capplet /usr/X11R6/bin/gnome-about-me
Re: Unhappy Xorg upgrade
On Sunday 01 February 2009 11:22:52 am Alex Goncharov wrote: | This has nothing to do with Linux. The issue is that that while src | has a stable versus current branch, there is no stable branch for | ports. The result is major updates are almost always problematic. Any data points to support the last statement? How about the last two xorg updates. Gnome has similar problems. | You wouldn't be able to keep other updates unless you manully patched the | tree, but you would be able to use the system until it's fixed. What the ETA for the new X fix? Not a clue. | You may assume that X is going to be fixed -- but what if not, in, say | a year? | | Your kidding me right?? No. You *know* that it is going to be fixed in a year? If yes, what's the source of your knowledge? What resources are going to be dedicated to work on my three problems? Not a clue. | | Well, it depends on which ports you are updating. | | All. | | Your saying that you build every port including the language options and | never had a problem in the last 18 months until the xorg update ?!?!? Yes, I am saying exactly this. I happen not to run Gnome or KDE. | | If you only run X, then I would expect your statement to be correct. | | Not sure what you mean here: nobody runs only X. It's impossible. | | To be precise, it's the xorg port. So yes it's possible. Hm, let's see: Information for xorg-server-1.5.3_2,1: Depends on: ([ I exclude the X things ]): Dependency: expat-2.0.1 Dependency: openssl-0.9.8j Dependency: pciids-20081012 Dependency: e2fsprogs-libuuid-1.41.3_1 Dependency: python25-2.5.2_3 Dependency: pkg-config-0.23_1 Dependency: libpthread-stubs-0.1 Dependency: libiconv-1.11_1 Dependency: gettext-0.17_1 Plenty of non-xorg things are needed for xorg, right? And if I build from the sources, I also need gmake, bison, autoconf etc. Your kidding me again right?? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: firefox[2,3] will not start after recent ports upgrade
From: Cezary Morga c...@therek.net ... Is it only Firefox or maybe other GTK2 apps are also affected? I've run into similar problem after January 14th Gnome/GTK+ update, which was acutally my fault, as I haven't upgraded it properly. Recompiling Firefox along with the ports it depends on did the trick: portupgrade -Rf firefox On one of my machines I did as you suggested and both firefox2,3 work now. But I am not sure which library was faulty... From: Daniel Roethlisberger dan...@roe.ch ... Could it be the case that firefox-bin hangs in umtxn state? you're right! (Check using ps -laux instead of -aux) http://daemon.nanophys.kth.se/~kono/ktrace_ff2.txt http://daemon.nanophys.kth.se/~kono/ktrace_ff3.txt These trace the wrong process: the wrapper shell script (sh). The actual hanging process would be firefox-bin, not sh. Try ktracing with child processes (-i). ktrace -i showed last line: firefox-bin CALL _umtx_op(0x65f8e0,0x8,0x1,0x65f8c0,0) http://daemon.nanophys.kth.se/~kono/ktrace_ff3_ktrace-i.txt Do you know which port/lib causing this hang on _umtx_op? Anyway, seem that on my second machine I have to force update all dependencies... Thanks for your help guys! /Alexander Konovalenko ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Unhappy Xorg upgrade
,--- You/vehemens (Sun, 01 Feb 2009 14:36:04 -0800) * | On Sunday 01 February 2009 11:22:52 am Alex Goncharov wrote: | | Any data points to support the last statement? | | How about the last two xorg updates. Gnome has similar problems. Last two -- when (or what numbers)? | | You wouldn't be able to keep other updates unless you manully patched the | | tree, but you would be able to use the system until it's fixed. | | What the ETA for the new X fix? | | Not a clue. | | You may assume that X is going to be fixed -- but what if not, in, say | | a year? | | | | Your kidding me right?? | | No. You *know* that it is going to be fixed in a year? If yes, | what's the source of your knowledge? What resources are going to be | dedicated to work on my three problems? | | Not a clue. So why do you ask me if I am kidding you? | | | Well, it depends on which ports you are updating. | | | | All. | | | | Your saying that you build every port including the language options and | | never had a problem in the last 18 months until the xorg update ?!?!? | | Yes, I am saying exactly this. I happen not to run Gnome or KDE. | | | | If you only run X, then I would expect your statement to be correct. | | | | Not sure what you mean here: nobody runs only X. It's impossible. | | | | To be precise, it's the xorg port. So yes it's possible. | | Hm, let's see: | | | Information for xorg-server-1.5.3_2,1: | | Depends on: ([ I exclude the X things ]): | Dependency: expat-2.0.1 | Dependency: openssl-0.9.8j | Dependency: pciids-20081012 | Dependency: e2fsprogs-libuuid-1.41.3_1 | Dependency: python25-2.5.2_3 | Dependency: pkg-config-0.23_1 | Dependency: libpthread-stubs-0.1 | Dependency: libiconv-1.11_1 | Dependency: gettext-0.17_1 | | | Plenty of non-xorg things are needed for xorg, right? | | And if I build from the sources, I also need gmake, bison, autoconf | etc. | | Your kidding me again right?? Cute. Thanks for your contribution and have a good day now. -- Alex -- alex-goncha...@comcast.net -- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Contact for assistance
On Fri, Jan 30, 2009 at 06:56:17PM -0500, V. M. Tame-Reyes wrote:
Hello,
I live in a place where the internet connection is
very, very slow, and i feel very enthusiastic about
freeBSD (i'm currently using Linux), therefore i
had a friend download about 16 GB of ports from
the official ports site, and i have them now in my
local network.
We are working on projects related to molecular
dynamics, and other physics related topics, so we
kind need trustworthy, robust servers to do the
calculations, and we decided to try this OS,
could you provide some info/howto create a ports
server for my intranet, so i can move some servers
devoted to do calculations to this OS ?
On the machine which will serve ports' distfiles you enable the ftp server
with ports' distfiles directory. This is done with this lines in /etc/rc.conf:
ftpd_enable=YES
ftpd_flags=-Ar
and adding user ftp (via adduser command). Home directory of ftp user
should be /usr/ports/distfiles and nologin shell. The entry in /etc/passwd
should look like:
ftp:*:1002:14:FTP anonymous user:/usr/ports/distfiles:/usr/sbin/nologin
On the machines which will build (and download) ports you put the following
in /etc/make.conf:
MASTER_SITE_OVERRIDE+=ftp://your_ports_sevrer/${DIST_SUBDIR}/
If you populate /usr/ports/distfiles on the ftp server with actual
tarballs you should be able to build ports on clients as usual with
cd /usr/ports/category/portname ; make install clean.
Of course, this is only one of the possible methods...
I apologize if this is the wrong contact to reach
while looking for the assistance i need, but actually
was one that i found.
Thanks in advance,
Good luck,
Alexey.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Using shared-mime-info in a port
Hi all, I'm trying to create a port of a python app and have a couple of questions on using various gnome utils. Using `port test` I found that I should be using update-mime-info and update-desktop-database. So I added the appropriate post-install line and exec/unexec to pkg-plist. However, when I run `port test` it complains that several share/mime files are still present: === Extra files and directories check share/mime/subclasses share/mime/globs share/mime/globs2 share/mime/magic share/mime/XMLnamespaces share/mime/aliases share/mime/types share/mime/generic-icons share/mime/icons share/mime/treemagic share/mime/mime.cache Is it ok to leave these and let misc/shared-mime-info take care of them or is my unexec not cleaning up properly? I've tried to test other ports that use shared-mime-info and they don't seem to leave these stragglers. The lines I have in pkg-plist are: @exec %%LOCALBASE%%/bin/update-desktop-database /dev/null || /usr/bin/true @unexec %%LOCALBASE%%/bin/update-desktop-database /dev/null || /usr/bin/true @exec %%LOCALBASE%%/bin/update-mime-database %D/share/mime @unexec %%LOCALBASE%%/bin/update-mime-database %D/share/mime Another question I have is about the python setup.py file. It actually runs update-mime-database, update-desktop-database, gtk-update-icon-cache, and scrollkeeper-update. Should I be removing these via REINPLACE and having the port do it, or not worry about it? Thanks, Zach ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: unreasonable amount of memory used in openoffice build
From: Greg Rivers gcr+freebsd-po...@tharned.org Subject: Re: unreasonable amount of memory used in openoffice build Date: Sat, 31 Jan 2009 19:16:16 -0600 (CST) On Thu, 27 Nov 2008, Maho NAKATA wrote: Sorry for delay. Please try attached patch. If it works for you, I'll commit it. Will this patch be committed soon? I can confirm that with this patch it builds on i386. Without this patch, it will not build for me on any i386 system no matter how much RAM and/or swap is available. Thanks for your fine work on this port. Hello Greg Rivers, Thanks for your ping. Just now I raised as an issue and committed. http://www.openoffice.org/issues/show_bug.cgi?id=98714 Best, -- Nakata Maho http://accc.riken.jp/maho/ , http://ja.openoffice.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
INDEX build failed for 6.x
INDEX build failed with errors: Generating INDEX-6 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: php4-mcve-4.4.9: no entry for /usr/ports/devel/libmcve make_index: php4-mcve-4.4.9: no entry for /usr/ports/devel/libmcve make_index: pecl-mcve-7.0.1: no entry for /usr/ports/devel/libmcve make_index: pecl-mcve-7.0.1: no entry for /usr/ports/devel/libmcve Committers on the hook: chinsan kuriyama lx pav Most recent CVS update was: U MOVED U audio/timidity++/Makefile U devel/Makefile U devel/libmaa/Makefile U devel/libmaa/distinfo U devel/libmaa/pkg-descr U devel/libmonetra/Makefile U devel/libmonetra/distinfo U devel/libmonetra/pkg-descr U devel/libmonetra/pkg-plist U devel/p5-Params-Util/Makefile U devel/p5-Params-Util/distinfo U japanese/samba3/Makefile U japanese/samba3/distinfo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
installed ports dependency tree?
Suppose I have installed ports A..Z. Some of these are standakone; some depend on others on the list; others depend on installed ports not on the list. Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? I though portupgrade could to this, but apparently not. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
INDEX now builds successfully on 6.x
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
WIP - editors/emacs-devel update to 23.0.90
Hi freebsd-ports, I'm updating editors/emacs-devel to the first pretest tarball of 23.X announced earlier at: http://lists.gnu.org/archive/html/emacs-devel/2009-02/msg00051.html The update is almost done. I'm just checking for plist bugs and if the package installs correctly in the default built, WITHOUT_X11, WITHOUT_GTK on i386 and amd64, and I will file a PR with the patch to the port soon-ish. So if you are interested in emacs-devel/23.0.90 please wait a bit before working on any patches for 23.0.90. It might save you a bit of work duplication in a few minutes :) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: installed ports dependency tree?
On Sun, Feb 1, 2009 at 9:48 PM, Robert Huff roberth...@rcn.com wrote: Suppose I have installed ports A..Z. Some of these are standakone; some depend on others on the list; others depend on installed ports not on the list. Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? I though portupgrade could to this, but apparently not. Portmaster sets PM_UPGRADE_DONE_FLAG in /var/db/pkg/pkgname for all ports that it has finished upgrading to prevent multiple rebuilds of a port during the upgrade run. Scot ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
The KDE FreeBSD team is happy to announce the first public Call for Testing for KDE 4.2. Over the past weeks we have focused on the complex and very time consuming task to get KDE 4.2 running. Here are some random notes of mine. Some are tips, some are problems, some are just observations. * I am getting the vista-effect as my older 2.8Gz P4 / Radeon 9000 aren't up to the task of KDE4. I have desktop effects turned off. I've heard some rumours that Qt 4.5 may improve things, but I really do need to get a new computer. The days of refurbishing older hardware by installing *Nix may be drawing to an end... * Any hints or tips on slimming down KDE? * The default font was sans serif, which is not aliased (I'm not sure what it's aliased to). Changing this to bitstream vera sans solved the problem. * I was getting nepomuk cores, so I turned off nepomuk in the Desktop Search configuration page. This isn't used much in KDE4, so it's safe to turn off. * Konsole does not have a title in the title bar, only a :. This is configurable in the Tabs Titles page, but it isn't working. * All my KDE3 apps are showing up in my menus. I've even set XDG_DATA_DIRS, to no effect. Does anyone know of an easy way to segregate them out into their own menu? * The main menu is very slow, whether it's kickoff or classic. Opening up a submenu may take ten to fifteen seconds, with some noticeable disk activity. Very annoying. * Setting the folderview as a desktop activity crashes plasma. Using a normal folderview is okay. -- David Johnson ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
