Re: [FYI] Fwd: cvs commit: ports UPDATING ports/Mk bsd.python.mk
On 3/6/11, Rainer Hurling rhur...@gwdg.de wrote: On 06.03.2011 00:56 (UTC+1), b. f. wrote: Does it rebuild all depending packages? And waht is the difference between make upgrade-site-packages and portupgrade -r python? As I explained earlier on freebsd-python@, unlike 'portupgrade -r python', the upgrade-site-packages target just rebuilds ports that have files in the library directories belonging to non-default versions of python, and ports that in turn depend upon them, not necessarily every port that lists python as a dependency. upgrade-site-packages is for your convenience, to rebuild a (probably) smaller collection of ports that are most likely to need rebuilding after a change in default python versions. Thanks for the explanation. In principle the script works as aspected. As far as I can see there remain some ports like graphics/qgis without upgrading. QGIS defines USE_PYTHON=yes in its Makefile, but is not upgraded. Other examples from my installations are multimedia/xbmc, irc/xchat, editors/openoffice.org-3. pkg_libchk from sysutils/bsdadminscripts identifies most (all?) of them. Sure, there are a number of ways to identify which ports actually depend upon python. pkg_libchk will get you most, but maybe not all, of them. (One might be configured in a way that depends upon the specific version of python used, but not actually link to a python shared library, for example.) Since rebuilding lots of ports can consume time and resources, and some ports depend upon python only to the extent of containing portable scripts with a /usr/local/bin/python shebang in them, and hence don't really need to be updated, the upgrade-site-packages target was created as a reasonable compromise, to update only those ports that probably need to be updated when the default version of python is changed. update-site-packages may update a few that don't need to be updated (a port that really needs and is set up to use a non-default version of python, for example), and it may miss others that ought to be updated (a port that doesn't install files in a python library directory, but nevertheless depends in an important way upon the specific version of python used). If you want to be thorough, then don't use upgrade-site-packages, but rather recursively update all ports that depend directly or indirectly upon python. b. ___ 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: [FYI] Fwd: cvs commit: ports UPDATING ports/Mk bsd.python.mk
On 06.03.2011 09:09 (UTC+1), b. f. wrote: On 3/6/11, Rainer Hurlingrhur...@gwdg.de wrote: On 06.03.2011 00:56 (UTC+1), b. f. wrote: Does it rebuild all depending packages? And waht is the difference between make upgrade-site-packages and portupgrade -r python? As I explained earlier on freebsd-python@, unlike 'portupgrade -r python', the upgrade-site-packages target just rebuilds ports that have files in the library directories belonging to non-default versions of python, and ports that in turn depend upon them, not necessarily every port that lists python as a dependency. upgrade-site-packages is for your convenience, to rebuild a (probably) smaller collection of ports that are most likely to need rebuilding after a change in default python versions. Thanks for the explanation. In principle the script works as aspected. As far as I can see there remain some ports like graphics/qgis without upgrading. QGIS defines USE_PYTHON=yes in its Makefile, but is not upgraded. Other examples from my installations are multimedia/xbmc, irc/xchat, editors/openoffice.org-3. pkg_libchk from sysutils/bsdadminscripts identifies most (all?) of them. Sure, there are a number of ways to identify which ports actually depend upon python. pkg_libchk will get you most, but maybe not all, of them. (One might be configured in a way that depends upon the specific version of python used, but not actually link to a python shared library, for example.) Since rebuilding lots of ports can consume time and resources, and some ports depend upon python only to the extent of containing portable scripts with a /usr/local/bin/python shebang in them, and hence don't really need to be updated, the upgrade-site-packages target was created as a reasonable compromise, to update only those ports that probably need to be updated when the default version of python is changed. update-site-packages may update a few that don't need to be updated (a port that really needs and is set up to use a non-default version of python, for example), and it may miss others that ought to be updated (a port that doesn't install files in a python library directory, but nevertheless depends in an important way upon the specific version of python used). If you want to be thorough, then don't use upgrade-site-packages, but rather recursively update all ports that depend directly or indirectly upon python. Now it is more clear to me that this upgrading process depends from the specific installation. Perhaps it should be mentioned in ports/UPDATING, that eventually this upgrading is not complete? I think for me it was ok to first use the upgrade-site-packages target and after that identifying the few remaining ports with pkg_libchk, which should also be updated. I did that with several machines. All seems to work fine so far. Thanks again for this detailed answer, Rainer ___ 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: [FYI] Fwd: cvs commit: ports UPDATING ports/Mk bsd.python.mk
b. f. bf1...@googlemail.com wrote: Does it rebuild all depending packages? And waht is the difference between make upgrade-site-packages and portupgrade -r python? As I explained earlier on freebsd-python@, unlike 'portupgrade -r python', the upgrade-site-packages target just rebuilds ports that have files in the library directories belonging to non-default versions of python, and ports that in turn depend upon them, not necessarily every port that lists python as a dependency. upgrade-site-packages is for your convenience, to rebuild a (probably) smaller collection of ports that are most likely to need rebuilding after a change in default python versions. Thanks! can you tell me if libreoffice is in the list to recompile? Heino ___ 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: [FYI] Fwd: cvs commit: ports UPDATING ports/Mk bsd.python.mk
On 3/6/11, Rainer Hurling rhur...@gwdg.de wrote: On 06.03.2011 09:09 (UTC+1), b. f. wrote: On 3/6/11, Rainer Hurlingrhur...@gwdg.de wrote: On 06.03.2011 00:56 (UTC+1), b. f. wrote: Now it is more clear to me that this upgrading process depends from the specific installation. Perhaps it should be mentioned in ports/UPDATING, that eventually this upgrading is not complete? May not be complete. I think a brief note to that effect would have been useful, judging from the comments of some people on the mailing lists. b. ___ 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: FreeBSD Port: transmission-2.22
On 06/03/2011 07:21, Ruslan Mahmatkhanov wrote: 06.03.2011 05:18, Alex V. Petrov пишет: FreeBSD alex.super 8.2-STABLE FreeBSD 8.2-STABLE #116: Thu Mar 3 21:55:50 KRAT 2011 alex@alex.super:/usr/obj/usr/src/sys/ALEX amd64 transmission-2.13 needs updating (port has 2.22) transmission-cli-2.13 needs updating (port has 2.22) transmission-daemon-2.13 needs updating (port has 2.22) transmission-gtk2-2.13 needs updating (port has 2.22) #portmaster -aD [skip] ../libtransmission/libtransmission.a(handshake.o) (.text+0x16d9):/usr/ports/net-p2p/transmission- cli/work/transmission-2.22/libtransmission/handshake.c:610: undefined reference to `evbuffer_get_length' ../libtransmission/libtransmission.a(handshake.o) (.text+0x1714):/usr/ports/net-p2p/transmission- cli/work/transmission-2.22/libtransmission/handshake.c:759: more undefined references to `evbuffer_get_length' follow gmake[1]: *** [transmission-create] Ошибка 1 gmake[1]: Leaving directory `/usr/ports/net-p2p/transmission- cli/work/transmission-2.22/utils' gmake: *** [all-recursive] Ошибка 1 *** Error code 1 Stop in /usr/ports/net-p2p/transmission-cli. === make failed for net-p2p/transmission-cli === Aborting update === Update for net-p2p/transmission-cli failed === Aborting update - Alex V. Petrov You should deinstall libevent first. Why this is not in ports/UPDATING then? :-( -- David Demelier ___ 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: [FYI] Fwd: cvs commit: ports UPDATING ports/Mk bsd.python.mk
On 06/03/2011 05:47, b. f. wrote: On 3/5/11, b. f.bf1...@googlemail.com wrote: Does it rebuild all depending packages? And waht is the difference between make upgrade-site-packages and portupgrade -r python? As I explained earlier on freebsd-python@, unlike 'portupgrade -r python', the upgrade-site-packages target just rebuilds ports that have files in the library directories belonging to non-default versions of python, and ports that in turn depend upon them, not necessarily every port that lists python as a dependency. Sorry, I should clarify this. Above, I meant to write: ... and _not_ necessarily ports that in turn depend upon them, or every port that lists python as a dependency. upgrade-site-packages is for your convenience, to rebuild a (probably) smaller collection of ports that are most likely to need rebuilding after a change in default python versions. b. ___ 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 vim was not in the to recompile list and I need to rebuild it by hand. /libexec/ld-elf.so.1: Shared object libpython2.6.so not found, required by vim a (portmaster|portupgrade) -r lang/python in /usr/ports/UPDATING may be useful. Cheers, -- David Demelier ___ 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: FreeBSD Port: transmission-2.22
On 03/06/2011 12:55, David Demelier wrote: On 06/03/2011 07:21, Ruslan Mahmatkhanov wrote: 06.03.2011 05:18, Alex V. Petrov пишет: FreeBSD alex.super 8.2-STABLE FreeBSD 8.2-STABLE #116: Thu Mar 3 21:55:50 KRAT 2011 alex@alex.super:/usr/obj/usr/src/sys/ALEX amd64 transmission-2.13 needs updating (port has 2.22) transmission-cli-2.13 needs updating (port has 2.22) transmission-daemon-2.13 needs updating (port has 2.22) transmission-gtk2-2.13 needs updating (port has 2.22) #portmaster -aD [skip] ../libtransmission/libtransmission.a(handshake.o) (.text+0x16d9):/usr/ports/net-p2p/transmission- cli/work/transmission-2.22/libtransmission/handshake.c:610: undefined reference to `evbuffer_get_length' ../libtransmission/libtransmission.a(handshake.o) (.text+0x1714):/usr/ports/net-p2p/transmission- cli/work/transmission-2.22/libtransmission/handshake.c:759: more undefined references to `evbuffer_get_length' follow gmake[1]: *** [transmission-create] Ошибка 1 gmake[1]: Leaving directory `/usr/ports/net-p2p/transmission- cli/work/transmission-2.22/utils' gmake: *** [all-recursive] Ошибка 1 *** Error code 1 Stop in /usr/ports/net-p2p/transmission-cli. === make failed for net-p2p/transmission-cli === Aborting update === Update for net-p2p/transmission-cli failed === Aborting update - Alex V. Petrov You should deinstall libevent first. Why this is not in ports/UPDATING then? :-( Because, probably it's not a good solution. I'm useing memcached witch need libevent to work. So removing libevent, will broke memcached :-( ___ 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
FreeBSD Port: transmission-2.22
Because, probably it's not a good solution. I'm useing memcached witch need libevent to work. So removing libevent, will broke memcached :-( Either wait for a fix or remove libevent+deps-install libevent2+transmission- install libevent+deps From the gnome ml: http://lists.freebsd.org/pipermail/freebsd-gnome/2011-March/025663.html ___ 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
FreeBSD Port: py27-feedparser-4.1_2
Hello, It looks like there have been several new releases of the Universal Feed Parser in the past few months. Are there any plans to update the port to the latest version? Thanks! -- Douglas William Thrift doug...@douglasthrift.net http://douglasthrift.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
FreeBSD needs fresh Blood!
I read last post Martin Wilke's blog called FreeBSD needs fresh Blood! First of all, I think it's difficult to testing ports. I'm using testing release of VirtualBox, but for build this port I must download patches, apply its on my own tree and merge its with official ports using portshaker. It's possible to build testing ports outside tree, but I must build every port separately, since `Make` don't known how to track dependencies. Another possibility is replace ports in disk, but after upgrade tree eg. with portsnap I lose my changes, and portmaster want to rebuild these ports to stable release. If testing will be simpler, I think more people will do this. Maybe we must create two trees, eg: ports-stable and ports-current First we publish changes to current tree and after week or two without pr, we publish updates to stable tree too. Merging trees is another huge problem. Portshaker do this very well, but after merge I must rebuild INDEX file, which takes long time. This should be faster or even shouldn't be required (hard to do). ___ 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: Adding a PAM config option to net-im/ejabberd
Lawrence Stewart writes: On 01/31/11 13:09, Ashish SHUKLA wrote: Lawrence Stewart writes: On 01/31/11 00:45, Ashish SHUKLA wrote: Hi Lawrence, Lawrence Stewart writes: Hi Ashish, What do you think about applying the attached patch to the ejabberd port? It installs some parts required to allow ejabberd to auth against PAM and is working great for me. Sure, I can apply it, once ports freeze is over. I also need to update ejabberd. I'll do both together. Sounds good, thanks. One question: in order to get PAM auth working, you have to set uid root on the epam bits and chown them appropriately in order to allow things to work. Should the port installation process do these steps as well or should we leave them to the user? I would be inclined to have the port do them so that upgrading the port doesn't break PAM auth after the upgrade. We would want to print a big warning at the end of the port install about the set uid security aspects though. Thanks for the mention, I suggest adding mention of setuid bit in the description of the OPTION. And ofcourse port is going to set the setuid bit during installation. And `security-check' target in bsd.port.mk will catch the setuid bit set on the installed executable, and will inform the user as well. So, adding a warning about setuid bit be redundant, IMHO. Updated patch attached. Feel like committing it for me? Sure. I'm doing an update to 2.1.6 this week, and will include your diff. Thanks -- Ashish SHUKLA | GPG: F682 CDCC 39DC 0FEA E116 20B6 C746 CFA9 E74F A4B0 freebsd.org!ashish | http://people.freebsd.org/~ashish/ Avoid Success At All Costs !! pgpgbgrX8nSwe.pgp Description: PGP signature
Re: Firefox 4 - Beta
Beat Gaetzi b...@freebsd.org wrote: On 05.03.2011 12:48, Heino Tiedemann wrote: Hi, is there someone who likes to go for the Firefox 4 in ports? maybe into www/firefox-devel? Firefox 4 is in the State beta 12 - what means it is the release candidate. Firefox 4 is available for FreeBSD for a long time in our development repository. Please have a look at this page for more information about the freebsd-gecko repository: https://trillian.chruetertee.ch/freebsd-gecko/ Firefox 4 lives at: https://trillian.chruetertee.ch/svn/freebsd-gecko/branches/experimental/www/firefox-devel/ We are not going to commit a Firefox 4 Beta or RC to the ports tree. If you like to test Firefox 4 use the one from the development repository at your own risk. Cool. Any manpage or howto how I can gat this on my computer? Do I need SVN for that Heino ___ 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: Thunar startup
2011/3/5 Warren Block wbl...@wonkity.com: The last issue with the new xfce 4.8 is Thunar. From the command line: % thunar (thunar:71482): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GPhoto2VolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildExited: Process /usr/local/libexec/gvfs-gphoto2-volume-monitor exited with status 1 After about twenty seconds, the Thunar window opens. Another twenty seconds later, another one opens (this may be due to hal misidentifying hard drives as removable). gvfs is built with only the AVAHI option enabled, and gphoto is not installed. Building Thunar with default config options or all PLUG_* options disabled doesn't affect it, nor does the presence or absence of the thunar-vfs port. Thunar's options are independents, (except trash panel applet, which depends of gvfs). thunar-vfs is only necessary for thunar plugins which are not yet ported to « 4.8 branch », you can run Xfce without it. Once open, Thunar seems to work fine. ___ 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 -- olivier ___ 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: xfce4.8 icons/menus/panel
For me everything works well but I still do not have the Keyboard icons (was already the same in 4.6) As you can see here : http://files.malikania.fr/settings.png It appears with every icons themes I try. Cheers, -- Demelier David ___ 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: xfce4.8 icons/menus/panel
Install misc/gnome-icon-theme - go into Appearance (Icons tab), choose GNOME if you prefer Tango (like me), re-click on Tango, and keyboard icon will appear. 2011/3/6 David DEMELIER demelier.da...@gmail.com: For me everything works well but I still do not have the Keyboard icons (was already the same in 4.6) As you can see here : http://files.malikania.fr/settings.png It appears with every icons themes I try. Cheers, -- Demelier David ___ 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 -- olivier ___ 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: FreeBSD needs fresh Blood!
I read last post Martin Wilke's blog called FreeBSD needs fresh Blood! First of all, I think it's difficult to testing ports. I'm using testing release of VirtualBox, but for build this port I must download patches, apply its on my own tree and merge its with official ports using portshaker. It's possible to build testing ports outside tree, but I must build every port separately, since `Make` don't known how to track dependencies. There is always going to be some added work involved in testing. Have you considered using multiple trees, if you have sufficient disk space? Or using a version control system? Another possibility is replace ports in disk, but after upgrade tree eg. with portsnap I lose my changes, and portmaster want to rebuild these ports to stable release. It sounds like you are using the wrong tools. Although portsnap (which is not best suited for this purpose) has path arguments and an -l flag that can be used to add or preserve local changes, and both portmaster and portupgrade have options to ignore certain ports or to substitute alternative dependencies, you shouldn't have to make use of them. Instead, you should probably be using CVS (or another version control system that can import CVS), which will make merging and reverting changes easier. And naturally you shouldn't run updating tools until you've modified your tree. If testing will be simpler, I think more people will do this. Maybe we must create two trees, eg: ports-stable and ports-current First we publish changes to current tree and after week or two without pr, we publish updates to stable tree too. This has often been proposed, but since it would require more work from the already-overstretched committers, and the benefits are questionable, I don't think it is likely to happen soon. Merging trees is another huge problem. Portshaker do this very well, but after merge I must rebuild INDEX file, which takes long time. This should be faster or even shouldn't be required (hard to do). Do you really need to rebuild the INDEX? You can often avoid using it. If you do need to modify it, you can use some improved method, like http://www.lpthe.jussieu.fr/~talon/build_index.py or modify it incrementally, with something like ports-mgmt/p5-FreeBSD-Portindex, http://www.lpthe.jussieu.fr/~talon/portindex-18_1.tgz , or your own script. b. ___ 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: FreeBSD Port: transmission-2.22
On Sun, Mar 6, 2011 at 6:22 AM, Grzegorz Blach ma...@roorback.net wrote: On 03/06/2011 12:55, David Demelier wrote: On 06/03/2011 07:21, Ruslan Mahmatkhanov wrote: 06.03.2011 05:18, Alex V. Petrov пишет: FreeBSD alex.super 8.2-STABLE FreeBSD 8.2-STABLE #116: Thu Mar 3 21:55:50 KRAT 2011 alex@alex.super:/usr/obj/usr/src/sys/ALEX amd64 transmission-2.13 needs updating (port has 2.22) transmission-cli-2.13 needs updating (port has 2.22) transmission-daemon-2.13 needs updating (port has 2.22) transmission-gtk2-2.13 needs updating (port has 2.22) #portmaster -aD [skip] ../libtransmission/libtransmission.a(handshake.o) (.text+0x16d9):/usr/ports/net-p2p/transmission- cli/work/transmission-2.22/libtransmission/handshake.c:610: undefined reference to `evbuffer_get_length' ../libtransmission/libtransmission.a(handshake.o) (.text+0x1714):/usr/ports/net-p2p/transmission- cli/work/transmission-2.22/libtransmission/handshake.c:759: more undefined references to `evbuffer_get_length' follow gmake[1]: *** [transmission-create] Ошибка 1 gmake[1]: Leaving directory `/usr/ports/net-p2p/transmission- cli/work/transmission-2.22/utils' gmake: *** [all-recursive] Ошибка 1 *** Error code 1 Stop in /usr/ports/net-p2p/transmission-cli. === make failed for net-p2p/transmission-cli === Aborting update === Update for net-p2p/transmission-cli failed === Aborting update - Alex V. Petrov You should deinstall libevent first. Why this is not in ports/UPDATING then? :-( Because, probably it's not a good solution. Correct. There is bug in libevent2's libevent*.pc. I have submitted a patch in PR to fix it. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155315 Cheers, Mezz I'm useing memcached witch need libevent to work. So removing libevent, will broke memcached :-( -- mezz.free...@gmail.com - m...@freebsd.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gn...@freebsd.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
Re: net-p2p/transmission-gtk2 fails to build
On Sat, Mar 5, 2011 at 10:03 AM, Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:
05.03.2011 17:29, Anonymous пишет:
Ruslan Mahmatkhanovcvs-...@yandex.ru writes:
Hi!
I'm trying to update transmission 2.13 - 2.22 on 8-stable.
Errors like this:
../libtransmission/libtransmission.a(handshake.o)(.text+0x167d): In
function `canRead':
/usr/ports/net-p2p/transmission-gtk2/work/transmission-2.22/libtransmission/handshake.c:789:
undefined reference to `evbuffer_search'
../libtransmission/libtransmission.a(handshake.o)(.text+0x16d4):/usr/ports/net-p2p/transmission-gtk2/work/transmission-2.22/libtransmission/handshake.c:761:
undefined reference to `evbuffer_get_length'
Full build log is here:
http://pastebin.com/k0ZWLj3J
Probably a remnant from before libevent used PKG_CHECK_MODULES().
-L${LOCALBASE}/lib precedes -L${LOCALBASE}/lib/event2 during linking,
build with V=1 or -Wl,--verbose to see.
%%
Index: net-p2p/transmission-cli/Makefile
===
RCS file: /a/.cvsup/ports/net-p2p/transmission-cli/Makefile,v
retrieving revision 1.74
diff -u -p -r1.74 Makefile
--- net-p2p/transmission-cli/Makefile 5 Mar 2011 04:17:28 -
1.74
+++ net-p2p/transmission-cli/Makefile 5 Mar 2011 14:09:06 -
@@ -28,8 +28,6 @@ USE_GMAKE= yes
USE_GNOME?= pkgconfig
USE_OPENSSL= yes
GNU_CONFIGURE= yes
-CPPFLAGS= -I${LOCALBASE}/include
-LDFLAGS= -L${LOCALBASE}/lib
CONFIGURE_ENV= CPPFLAGS=${CPPFLAGS}
CONFIGURE_ARGS=--with-zlib=/usr \
--disable-libappindicator \
%%
No, this patch doesn't help. But removing libevent-1.4.14b_2 does, while
keeping libevent2-2.0.10.
There is bug in libevent2's libevent*.pc. I have submitted a patch in
PR to fix it.
http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155315
Cheers,
Mezz
There is also discussion about that in gnome@. Thanks.
--
Regards,
Ruslan
--
mezz.free...@gmail.com - m...@freebsd.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/ - gn...@freebsd.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
Re: FreeBSD needs fresh Blood!
On 3/6/11, b. f. bf1...@googlemail.com wrote: ... First of all, I think it's difficult to testing ports. ... Another possibility is replace ports in disk, but after upgrade tree eg. with portsnap I lose my changes, and portmaster want to rebuild these ports to stable release. ... It sounds like you are using the wrong tools. Although portsnap (which is not best suited for this purpose) has path arguments and an -l flag that can be used to add or preserve local changes, and both portmaster and portupgrade have options to ignore certain ports or to substitute alternative dependencies, you shouldn't have to make use of them. ... Merging trees is another huge problem. Portshaker do this very well, but after merge I must rebuild INDEX file, which takes long time. This should be faster or even shouldn't be required (hard to do). I should mention, too, that despite the awkwardness of these tools in this context, others who prefer to use them have found methods to overcome some of the problems that you mention. See, for example: http://lists.freebsd.org/pipermail/freebsd-ports/2007-April/040366.html b. ___ 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 4 - Beta
On 06.03.2011 19:17, Heino Tiedemann wrote: is there someone who likes to go for the Firefox 4 in ports? maybe into www/firefox-devel? Firefox 4 is in the State beta 12 - what means it is the release candidate. Firefox 4 is available for FreeBSD for a long time in our development repository. Please have a look at this page for more information about the freebsd-gecko repository: https://trillian.chruetertee.ch/freebsd-gecko/ Firefox 4 lives at: https://trillian.chruetertee.ch/svn/freebsd-gecko/branches/experimental/www/firefox-devel/ We are not going to commit a Firefox 4 Beta or RC to the ports tree. If you like to test Firefox 4 use the one from the development repository at your own risk. Cool. Any manpage or howto how I can gat this on my computer? Do I need SVN for that 1. cd /usr/ports/devel/subversion; make install clean 2. cd /usr/ports/www 3. svn co https://trillian.chruetertee.ch/svn/freebsd-gecko/branches/experimental/www/firefox-devel 4. cd firefox-devel 5. make install clean The performance of Firefox 4 is impressive, sometimes it's even working faster than Chromium. ___ 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: FreeBSD needs fresh Blood!
On Sunday 06 March 2011 18:35:10 b. f. wrote: It sounds like you are using the wrong tools. Although portsnap (which is not best suited for this purpose) has path arguments and an -l flag that can be used to add or preserve local changes, and both portmaster and portupgrade have options to ignore certain ports or to substitute alternative dependencies, you shouldn't have to make use of them. Instead, you should probably be using CVS (or another version control system that can import CVS), which will make merging and reverting changes easier. And naturally you shouldn't run updating tools until you've modified your tree. zfs should be mentioned as well. a tank/ports dataset with snapshots and clones can make switching tree, rolling back and merging test ports quite comfortable -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla Nasrudin walked into a teahouse and declaimed, The moon is more useful than the sun. Why?, he was asked. Because at night we need the light more. signature.asc Description: This is a digitally signed message part.
Re: FreeBSD needs fresh Blood!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/06/2011 18:35, b. f. wrote: I read last post Martin Wilke's blog called FreeBSD needs fresh Blood! First of all, I think it's difficult to testing ports. I'm using testing release of VirtualBox, but for build this port I must download patches, apply its on my own tree and merge its with official ports using portshaker. It's possible to build testing ports outside tree, but I must build every port separately, since `Make` don't known how to track dependencies. There is always going to be some added work involved in testing. Have you considered using multiple trees, if you have sufficient disk space? Or using a version control system? Multiple trees don't help me a lot, portmaster became fools. There is no significant difference if I use version control system or portshaker to merge trees. Another possibility is replace ports in disk, but after upgrade tree eg. with portsnap I lose my changes, and portmaster want to rebuild these ports to stable release. It sounds like you are using the wrong tools. Although portsnap (which is not best suited for this purpose) has path arguments and an -l flag that can be used to add or preserve local changes, and both portmaster and portupgrade have options to ignore certain ports or to substitute alternative dependencies, you shouldn't have to make use of them. Instead, you should probably be using CVS (or another version control system that can import CVS), which will make merging and reverting changes easier. And naturally you shouldn't run updating tools until you've modified your tree. But I won't resign from use updating tools, even when I use merged tree. Because I use merged tree all the time. If testing will be simpler, I think more people will do this. Maybe we must create two trees, eg: ports-stable and ports-current First we publish changes to current tree and after week or two without pr, we publish updates to stable tree too. This has often been proposed, but since it would require more work from the already-overstretched committers, and the benefits are questionable, I don't think it is likely to happen soon. Merging trees is another huge problem. Portshaker do this very well, but after merge I must rebuild INDEX file, which takes long time. This should be faster or even shouldn't be required (hard to do). Do you really need to rebuild the INDEX? You can often avoid using it. If you do need to modify it, you can use some improved method, like http://www.lpthe.jussieu.fr/~talon/build_index.py or modify it incrementally, with something like ports-mgmt/p5-FreeBSD-Portindex, http://www.lpthe.jussieu.fr/~talon/portindex-18_1.tgz , or your own script. b. I known that are many different ways to merge ports from different sources, but none of them are simple and fast to use it for first time. Look at last calls for testers: http://lists.freebsd.org/pipermail/freebsd-ports/2011-February/065884.html http://lists.freebsd.org/pipermail/freebsd-ports/2011-February/065983.html There are only links to tarballs, without address to repository. I must download tarballs, commit ports to my tree and merge it with official ports. Another CFT: http://lists.freebsd.org/pipermail/freebsd-ports/2011-February/066007.html There is address for repository, but I still need merging trees and rebuild index for portmaster. I thing if testing ports will be simpler, more people can do this, and want to do this. I proposed stable and current trees, but maybe one official merge tool, which is easy to setup will be better, or something completely different. -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.17 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJNc9RkAAoJEFCzIDMxqoILknMH/2ewFVhIWz02xCXFzp7vNtPO wkcJmzIUjF9LxKQ1mTdsZbBboIWzchihLZoCa8GDhZYmFgGnzhl7UDeDzjJ4/+fL DKcAkmixOR2TbFKoZf8C52wIv4bE9WuuuUlibVyctK4/3rXB3NOpq4xXi1dT5G3q ZzdpWdBi3p6Ec9bnRuWl/aqMhIbHq9NweX50pB4TF5Wldv3fWAGGL/kLOHnAEzCr 8vVRRz6QfnKbrxY830fs5wodgRJGCEWzfat33Y0jV5UWKQwW01f2CxRm9tzbuIJJ X/Nr0QLdi0L7OXEpqaak4OCIUl1M3UCKM2lYovlRt5lXb/0PrAdeZzgzHWMNH9s= =Kl87 -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
FreeBSD Port: sabnzbdplus-0.5.6_2 Installs Cherrypy-3.2
Hi Daniel, thanks for mainting the SABnzbdplus port. Just did a clean install of the port on a clean install of FreeBSD 8.2 (amd64) and run into the following: The port installs cherrypy version 3.2 but when I start the SABnzbd.py it says it wants Cherrypy version 3.1 I went into the SABnzbd.py and altered the test for version 3.1 into 3.2 as a quick and dirty workaround Any input is welcome. Regards, Huib Netherlands___ 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: KDE3?
On Wednesday 02 March 2011 17:26:20 Heino Tiedemann wrote: is KDE3 out? - misc/kdeutils3 (marked as IGNORE) or will it be compilable soon? it is fixed now -- Alberto Villa, FreeBSD committer avi...@freebsd.org http://people.FreeBSD.org/~avilla Waste not, get your budget cut next year. signature.asc Description: This is a digitally signed message part.
Re: FreeBSD Port: sabnzbdplus-0.5.6_2 Installs Cherrypy-3.2
Hi Huib, Noticed that my sabnzbd failed after upgrading cherrypy 3.1.2 to 3.2 from ports. Hadn't seen the knob for the version check, mine started failing on the Cheetah check was my impression. In general sabnzbd comes with its own cherrypy version included, the FreeBSD version uses cherrypy from ports making it vulnerable to breakages like this. Kind regards, Spil On Sun, Mar 6, 2011 at 7:37 PM, Huib Smeets h...@huibsmeets.com wrote: Hi Daniel, thanks for mainting the SABnzbdplus port. Just did a clean install of the port on a clean install of FreeBSD 8.2 (amd64) and run into the following: The port installs cherrypy version 3.2 but when I start the SABnzbd.py it says it wants Cherrypy version 3.1 I went into the SABnzbd.py and altered the test for version 3.1 into 3.2 as a quick and dirty workaround Any input is welcome. Regards, Huib Netherlands___ 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 ___ 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: FreeBSD Port: py27-feedparser-4.1_2
06.03.2011 16:52, Douglas Thrift пишет: Hello, It looks like there have been several new releases of the Universal Feed Parser in the past few months. Are there any plans to update the port to the latest version? Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/155322 -- Regards, Ruslan ___ 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
curses update
It seems a lot of dependant packages need to be rebuilt: # pkg_libchk aalib-1.4.r5_5: /usr/local/bin/aafire misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aafire misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aainfo misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aainfo misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aasavefont misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aasavefont misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aatest misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/bin/aatest misses libncurses.so.5.7 aalib-1.4.r5_5: /usr/local/lib/libaa.so.1 misses libncurses.so.5.7 ... This is my personal rebuild list: # pkg_libchk -q aalib-1.4.r5_5 aspell-0.60.6_5 eclipse-3.6.1_1 gegl-0.1.6 gettext-0.18.1.1 gimp-app-2.6.11_2,1 gnuplot-4.4.0 gutenprint-base-5.2.4_2 input-wacom-40.0.8.2.2_6 irssi-0.8.15_2 libcaca-0.99.b17_3 libcdio-0.82_1 mencoder-1.0.r20101106_1 mjpegtools-1.9.0_2 mplayer-1.0.r20101106_1 octave-3.2.4_4 opera-11.01 pinentry-gtk2-0.8.1 python26-2.6.6 rtorrent-0.8.7 ruby-1.8.7.302,1 samba34-3.4.9_2 sdl-1.2.14_2,2 sdl_gfx-2.0.21_1 sdl_image-1.2.10_2 sdl_mixer-1.2.11_2 sdl_sound-1.0.3_4 smpeg-0.4.4_8 xmlrpc-c-devel-1.25.3 Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: curses update
On 06/03/2011 21:17, Dominic Fandrey wrote: It seems a lot of dependant packages need to be rebuilt: This is my personal rebuild list: # pkg_libchk -q aalib-1.4.r5_5 aspell-0.60.6_5 eclipse-3.6.1_1 Sorry about getting eclipse in there. It showed up because it's linked against libjawt.so and that is not in the library path. Regards -- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? ___ 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: FreeBSD needs fresh Blood!
On 3/6/11, Grzegorz Blach ma...@roorback.net wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 03/06/2011 18:35, b. f. wrote: ... First of all, I think it's difficult to testing ports. ... Multiple trees don't help me a lot, portmaster became fools. There is no significant difference if I use version control system or portshaker to merge trees. I'm not so sure. But in any event, maybe you can elaborate on what you mean by portmaster becoming a fool? ... Another possibility is replace ports in disk, but after upgrade tree eg. with portsnap I lose my changes, and portmaster want to rebuild these ports to stable release. ... system that can import CVS), which will make merging and reverting changes easier. And naturally you shouldn't run updating tools until you've modified your tree. But I won't resign from use updating tools, even when I use merged tree. Because I use merged tree all the time. No one is asking you to. But obviously you'll have to use the tools at the right time, and in the right manner, if you are going to be experimenting with different sets of ports. It doesn't sound as if you are doing that now, based on your reports. If you really want to use portmaster, and you don't want to be troubled with rebuilding the index, then maybe you could ask the portmaster maintainer to implement an option that ignores the index, and relies solely on the ports tree, if there isn't such an option already. Or examine the various incremental update methods I cited earlier. ... I known that are many different ways to merge ports from different sources, but none of them are simple and fast to use it for first time. Look at last calls for testers: http://lists.freebsd.org/pipermail/freebsd-ports/2011-February/065884.html http://lists.freebsd.org/pipermail/freebsd-ports/2011-February/065983.html There are only links to tarballs, without address to repository. I must download tarballs, commit ports to my tree and merge it with official ports. Another CFT: http://lists.freebsd.org/pipermail/freebsd-ports/2011-February/066007.html There is address for repository, but I still need merging trees and rebuild index for portmaster. I thing if testing ports will be simpler, more people can do this, and want to do this. I proposed stable and current trees, but maybe one official merge tool, which is easy to setup will be better, or something completely different. Okay, so we could make a webpage that contains some recommendations and instructions for those interested in testing. And we could make a central repository using a version control system that has efficient branching, where committers could be asked to add major changes in separate branches, so that it would be easier to test them. (I'm not saying one unstable branch, because I think it would be difficult to isolate and solve problems when mixing lots of different changesets.) Those are reasonable suggestions. But of course, these suggestions would require more work from committers, and won't make testing completely painless. They would be roughly equivalent to the case you mention above, where there was a repository -- yet you still seemed reluctant to test in that case. b. ___ 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 4 - Beta
Sergey Nikolenko s...@swa.org.ru wrote: On 06.03.2011 19:17, Heino Tiedemann wrote: Any manpage or howto how I can gat this on my computer? Do I need SVN for that 1. cd /usr/ports/devel/subversion; make install clean 2. cd /usr/ports/www 3. svn co https://trillian.chruetertee.ch/svn/freebsd-gecko/branches/experimental/www/firefox-devel 4. cd firefox-devel 5. make install clean Thaks a lot! Cool Stuff. FF4 is running now. By The Way, I never heard about this project freebsd-gecko. Where was the place I did not look carefully? Heino ___ 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
xfce 4.8 upgrade errors
How do I create a app menu, I'm getting an error when trying to load the menu menus/applications.menu not found. Recompile sysutils/garcon to resolve this error. I hope this helps someone else... Regards, Mark ___ 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: FreeBSD needs fresh Blood!
On 03/06/2011 10:37, Grzegorz Blach wrote: On 03/06/2011 18:35, b. f. wrote: I read last post Martin Wilke's blog called FreeBSD needs fresh Blood! First of all, I think it's difficult to testing ports No argument there, it can be hard work. I'm using testing release of VirtualBox, but for build this port I must download patches, apply its on my own tree and merge its with official ports using portshaker. You could also maintain completely separate trees, or subtrees with CVS. It's possible to build testing ports outside tree, but I must build every port separately, since `Make` don't known how to track dependencies. Setting PORTSDIR for your builds may help. Read ports/Mk/bsd.port.mk for more information about that. There is always going to be some added work involved in testing. Have you considered using multiple trees, if you have sufficient disk space? Or using a version control system? Multiple trees don't help me a lot, portmaster became fools. Not sure what you mean by that, but portmaster respects PORTSDIR as well. There is address for repository, but I still need merging trees and rebuild index for portmaster. portmaster does not require the INDEX unless you tell it to. If you have a ports tree to operate against portmaster doesn't need the INDEX at all. hope this helps, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: [FYI] Fwd: cvs commit: ports UPDATING ports/Mk bsd.python.mk
Heino Tiedemann wrote: Does it rebuild all depending packages? And waht is the difference between make upgrade-site-packages and portupgrade -r python? ... can you tell me if libreoffice is in the list to recompile? I don't know, I don't have it on my machine. If you do, then see if it installs files in a python library directory, via pkg_info -Lx libreoffice | grep -e '/lib/python[0-9]' or some alternative method. Or look at the packing list of a libreoffice package. If it does install files in such a directory, then it will be rebuilt by upgrade-site-packages. If it doesn't install files there, then it should not be rebuilt, unless you issue non-default PORTUPGRADE_ARGS. b. ___ 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: FreeBSD needs fresh Blood!
On Sun, Mar 6, 2011 at 23:25, Doug Barton do...@freebsd.org wrote: On 03/06/2011 10:37, Grzegorz Blach wrote: On 03/06/2011 18:35, b. f. wrote: I read last post Martin Wilke's blog called FreeBSD needs fresh Blood! First of all, I think it's difficult to testing ports No argument there, it can be hard work. I'm using testing release of VirtualBox, but for build this port I must download patches, apply its on my own tree and merge its with official ports using portshaker. You could also maintain completely separate trees, or subtrees with CVS. It's possible to build testing ports outside tree, but I must build every port separately, since `Make` don't known how to track dependencies. Setting PORTSDIR for your builds may help. Read ports/Mk/bsd.port.mk for more information about that. There is always going to be some added work involved in testing. Have you considered using multiple trees, if you have sufficient disk space? Or using a version control system? Multiple trees don't help me a lot, portmaster became fools. Not sure what you mean by that, but portmaster respects PORTSDIR as well. There is address for repository, but I still need merging trees and rebuild index for portmaster. portmaster does not require the INDEX unless you tell it to. If you have a ports tree to operate against portmaster doesn't need the INDEX at all. hope this helps, Doug My mistake, sorry. I'll rebuild INDEX after every merges, but not for portmaster, but for pver. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: FreeBSD needs fresh Blood!
2011/3/6 Grzegorz Blach ma...@roorback.net: On Sun, Mar 6, 2011 at 23:25, Doug Barton do...@freebsd.org wrote: On 03/06/2011 10:37, Grzegorz Blach wrote: On 03/06/2011 18:35, b. f. wrote: I read last post Martin Wilke's blog called FreeBSD needs fresh Blood! First of all, I think it's difficult to testing ports No argument there, it can be hard work. I'm using testing release of VirtualBox, but for build this port I must download patches, apply its on my own tree and merge its with official ports using portshaker. You could also maintain completely separate trees, or subtrees with CVS. It's possible to build testing ports outside tree, but I must build every port separately, since `Make` don't known how to track dependencies. Setting PORTSDIR for your builds may help. Read ports/Mk/bsd.port.mk for more information about that. There is always going to be some added work involved in testing. Have you considered using multiple trees, if you have sufficient disk space? Or using a version control system? Multiple trees don't help me a lot, portmaster became fools. Not sure what you mean by that, but portmaster respects PORTSDIR as well. There is address for repository, but I still need merging trees and rebuild index for portmaster. portmaster does not require the INDEX unless you tell it to. If you have a ports tree to operate against portmaster doesn't need the INDEX at all. hope this helps, Doug My mistake, sorry. I'll rebuild INDEX after every merges, but not for portmaster, but for pver. Could you use pkg_version -vL = for your purpose ? It's a base system tool and doesn't need INDEX. -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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 -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org - against HTML email vCards X www: http://www.gid0.org - against proprietary attachments / \ Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas. ___ 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: FreeBSD needs fresh Blood!
On 03/06/2011 16:40, Olivier Smedts wrote: Could you use pkg_version -vL = for your purpose ? It's a base system tool and doesn't need INDEX. If all you want to know is what ports need updating, portmaster has an option for that. There is also an alias to abbreviate the output in the man page. hth, Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: FreeBSD needs fresh Blood!
On Sun, 6 Mar 2011, Doug Barton wrote: On 03/06/2011 16:40, Olivier Smedts wrote: Could you use pkg_version -vL = for your purpose ? It's a base system tool and doesn't need INDEX. If all you want to know is what ports need updating, portmaster has an option for that. There is also an alias to abbreviate the output in the man page. pkg_version is somewhat faster. On my system (seconds): portmaster -L | filters: 32.53 pkg_version -vl'': 23.99 And, for a malus versus citrus comparison with hidden overhead: portversion -vl'': 7.32 ___ 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: FreeBSD needs fresh Blood!
On 03/06/2011 17:59, Warren Block wrote: On Sun, 6 Mar 2011, Doug Barton wrote: On 03/06/2011 16:40, Olivier Smedts wrote: Could you use pkg_version -vL = for your purpose ? It's a base system tool and doesn't need INDEX. If all you want to know is what ports need updating, portmaster has an option for that. There is also an alias to abbreviate the output in the man page. pkg_version is somewhat faster. True, but 'portmaster -L' (with a ports tree) gives you more information. Such as when ports you have installed have been DEPRECATED or MOVED. :) 'portmaster -L --index-only' is very competitive in terms of wall clock time with any other method. Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/ ___ 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: FreeBSD needs fresh Blood!
On Sun, 6 Mar 2011, Doug Barton wrote: On 03/06/2011 17:59, Warren Block wrote: pkg_version is somewhat faster. True, but 'portmaster -L' (with a ports tree) gives you more information. Such as when ports you have installed have been DEPRECATED or MOVED. :) 'portmaster -L --index-only' is very competitive in terms of wall clock time with any other method. It continues to amaze me how much you have in there. Oh, and my times earlier were probably user time rather than wall time, for which I'll shiftily blame the difference between csh's time builtin and /usr/bin/time. Redoing that: portmaster -L | filterfu: 43.6 pkg_version -vl'':30.5 portversion -vl'': 3.6 portmaster -L --index-only: 2.5 As a bonus, the last one is not only the fastest but provides more useful information. Off to change my update script... ___ 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
