Re: Overly restrictive checks in the make process
On Sat, Jul 21, 2007 at 06:20:53AM -0400, Bill Moran wrote: Kent Stewart [EMAIL PROTECTED] wrote: On Friday 20 July 2007, Mark Linimon wrote: On Fri, Jul 20, 2007 at 04:07:49PM -0400, Bill Moran wrote: Even better would be for make to realize that it's only doing the fetching, and do it anyway. That still doesn't help with the problem of a user who starts a 10MB download that won't work on his architecture or OS release. The code is all the same. This is the aggravation we are trying to prevent. That still doesn't address the concern or improve the system downtime that a pkg_delete, make install allows. If you can't run something, you don't have any downtime but to have to pkg_delete before you start the tarball fetch can be really long on some ports. It's certainly a tradeoff. Either way you do it, there are practical scenarios where a user is inconvenienced. Perhaps an environmental override is the best route. NO_IGNORE=yes or something similar? Yes, use the NO_IGNORE variable (which just passed its tenth birthday) to override IGNORE checks you disagree with. Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports upgrade
Doug Barton wrote: The other is to not use bash as your login shell, but rather to use sh, then have a .profile that starts bash if it's available: if [ -x /usr/local/bin/bash ]; then exec /usr/local/bin/bash --login fi Hrrm, my actual .profile entry is more complicated than that, and I just realized that I oversimplified it here. What you want to do is also test to make sure that the bash you can find will run: if [ -x /usr/local/bin/bash ]; then if /usr/local/bin/bash --version /dev/null 21; then exec /usr/local/bin/bash --login fi fi otherwise you're stuck in the same boat by exec'ing something that's going to fail because of the missing library. Sorry for the confusion, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: php5-5.2.3
i was wondering if it would be possible to make --enable-versioning an optional config parameter? zend platform will not install when php is compiled with it, and it looks like xdebug has problems as well. i looked for awhile for a way to bypass this option with a command line switch, but came empty -- apologies if i've missed something. thanks for a great port, chad ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keeping Ports and Packages Synchronized
--- Chuck Swiger [EMAIL PROTECTED] wrote: On Jul 26, 2007, at 4:14 PM, Kurt Abahar wrote: I'm trying to find a way to keep the ports tree synchronized with that from which the latest packages in packages-6-stable were built. Is there a way to accomplish this? Sure, you probably want something like portupgrade -P or portupgrade -PP options. Note that if you have reason to select non-default options, you're better off building the ports locally to suit your preferences... -- -Chuck Thank you for the quick response. I have tried the portupgrade way, but unfortunately the packages lag behind ports the majority of the time. This led me to think that keeping the ports tree a little behind HEAD would be a better solution. However, I don't know how to get a hold of this lag time. Is it a few days, a few weeks or ... ? Perhaps there is a better way? Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Keeping Ports and Packages Synchronized
Hi everyone, I'm trying to find a way to keep the ports tree synchronized with that from which the latest packages in packages-6-stable were built. Is there a way to accomplish this? Thank you Be a better Globetrotter. Get better travel answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=listsid=396545469 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xkeyboard-config-1.0 breaks modifiers?
Henrik Brix Andersen píše v čt 26. 07. 2007 v 19:56 +0200: It's not just you. I have posted the following patch to the ports/114876 PR [1], which fixes the issue: Could you test the fix from ports/114924 ? Looks like a cleaner fix to me. -- Pav Lucistnik [EMAIL PROTECTED] [EMAIL PROTECTED] XML is a giant step in no direction at all. -- Erik Naggum signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: samba 3.0.25b
Johan Hendriks wrote: Does anyone know when the latest samba will hit the ports tree? Dude, it just came out today. Try giving people a little bit of a chance to work on it first. Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports upgrade
Khaled Hussein wrote: Last week i upgraded our servers when there was vulnerability on php, clamav etc, but when i finished my upgrades i faced many problems, one of it was i cannot login to some of my servers, it was bash issue after upgrading gettext port, and i see in the UPDATING file that i have to run portupgrade -rf gettext and this solve the problem of bash , i used portmanager in upgrading the ports All of the problems you're facing are related to the fact that libintl (part of gettext) bumped it's major version number, and the programs you are having problems with are linked against the old version which you no longer have on your system. The portupgrade line above (or the equivalent 'portmaster -r gettext') would have rebuilt gettext first, then every port that depends on it to make sure that they would still work. This is usually only needed in a situation like this when a library bumps its major. For portmaster there is also an option (-w) to save old shared libs when you do an upgrade so that you can handle upgrading the rest of the dependent ports gracefully. There is an equivalent option in portupgrade, I just don't recall what it is. For the case of bash specifically, there are two ways to avoid this problem. The first is to build bash static by putting 'WITH_STATIC_BASH= yes' in make.conf, or ports.conf. The other is to not use bash as your login shell, but rather to use sh, then have a .profile that starts bash if it's available: if [ -x /usr/local/bin/bash ]; then exec /usr/local/bin/bash --login fi Personally I do both. :) after that i faced again many problems, one of them till now i cannot solve it, when i run vim editor i got [/libexec/ld-elf.so.1: Shared object libintl.so.6 not found, required by vim] and in my squirrelmail when i change my password also it fails with this error [ -- /libexec/ld-elf.so.1: Shared object libintl.so.6 not found, required by courierpassd ], also the same file missed, You need to force a rebuild of those two ports, assuming that you have the new gettext installed. any one can guide me please how to fix my problems, because i work in ISP and these services is used by our customers Well I hope that this helps you, and your customers. :) my OS is Freebsd 6.1 and 6.0 I know that in-place upgrades are always hard, but you might want to consider at least upgrading the OS on the 6.0 box. Lots and lots of bug fixes and performance improvements have been added to the RELENG_6 branch since that one came out. Regards, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xkeyboard-config-1.0 breaks modifiers?
On Wed, Jul 25, 2007 at 07:18:37PM -0500, Craig Boston wrote:
Is anyone else seeing broken modifier keys (specifically the Win key)
with the new xkeyboard-config in ports, or is it just me?
It's not just you. I have posted the following patch to the
ports/114876 PR [1], which fixes the issue:
diff -urp /usr/ports/x11/xkeyboard-config/Makefile x11/xkeyboard-config/Makefile
--- /usr/ports/x11/xkeyboard-config/Makefile2007-07-24 16:11:49.0
+0200
+++ x11/xkeyboard-config/Makefile 2007-07-26 15:19:29.0 +0200
@@ -7,6 +7,7 @@
PORTNAME= xkeyboard-config
PORTVERSION= 1.0
+PORTREVISION= 1
CATEGORIES=x11
MASTER_SITES= http://xlibs.freedesktop.org/xkbdesc/
DISTNAME= xkeyboard-config-${PORTVERSION}
@@ -31,5 +32,6 @@ CONFIGURE_ARGS+= --with-xkb-base=${PREFI
post-install:
${MKDIR} /var/lib/xkb
+ ${MKDIR} ${PREFIX}/share/X11/xkb/compiled
.include bsd.port.mk
diff -urp /usr/ports/x11/xkeyboard-config/pkg-plist
x11/xkeyboard-config/pkg-plist
--- /usr/ports/x11/xkeyboard-config/pkg-plist 2007-07-24 16:11:49.0
+0200
+++ x11/xkeyboard-config/pkg-plist 2007-07-26 15:28:57.0 +0200
@@ -289,7 +289,9 @@ share/X11/xkb/types/pc
share/X11/xkb/types/README
share/X11/xkb/xkbcomp
@exec mkdir -p /var/lib/xkb
[EMAIL PROTECTED] mkdir -p %D/share/X11/xkb/compiled
@dirrm share/X11/xkb/compat
[EMAIL PROTECTED] share/X11/xkb/compiled
@dirrm share/X11/xkb/geometry/digital_vndr
@dirrm share/X11/xkb/geometry/sgi_vndr
@dirrm share/X11/xkb/geometry
Regards,
Brix
[1]: http://www.freebsd.org/cgi/query-pr.cgi?pr=114876
--
Henrik Brix Andersen [EMAIL PROTECTED]
pgpZ7bsXapkek.pgp
Description: PGP signature
Re: Ports with version numbers going backwards: net-p2p/azureus2
On Thu, Jul 26, 2007 at 12:07:48PM -0400, Kris Kennaway wrote: On Sun, Jul 22, 2007 at 01:34:08AM +0800, Rong-En Fan wrote: On Sat, Jul 21, 2007 at 05:31:49PM +, [EMAIL PROTECTED] wrote: ** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. As I noted in commit log, this port is just repocopied and not connected to build. The is intentional. If it is not connected to the build then how is it showing up here? I thought the script used INDEX builds for comparison. It does it's own thing by default, but it looks like it can be made to use INDEX instead. I'll try to polay with this when I find some time, the code is a bit of a maze though. -erwin Kris Regards, Rong-En Fan The ports tree was updated at Sat Jul 21 2007 16:32:01 UTC. - *net-p2p/azureus2* [EMAIL PROTECTED]: azureus2-2.5.0.4 azureus-3.0.1.6 | revision 1.46 | date: 2007/07/21 03:12:36; author: rafan; state: Exp; lines: +4 -5 | - Downgrade to 2.5.0.4. No PORTEPOCH is required since this port was just | copied from net-p2p/azureus and it's not connected to build yet. | | PR: ports/114486 | Submitted by:Robert Noland rnoland at 2hip.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] -- Erwin Lansing http://droso.org Security is like an onion. (o_ _o) It's made up of several layers \\\_\ /_/// And it makes you cry.) ([EMAIL PROTECTED] pgpzqyybZpnBQ.pgp Description: PGP signature
Re: Ports with version numbers going backwards: net-p2p/azureus2
On Sun, Jul 22, 2007 at 01:34:08AM +0800, Rong-En Fan wrote: On Sat, Jul 21, 2007 at 05:31:49PM +, [EMAIL PROTECTED] wrote: ** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. As I noted in commit log, this port is just repocopied and not connected to build. The is intentional. If it is not connected to the build then how is it showing up here? I thought the script used INDEX builds for comparison. Kris Regards, Rong-En Fan The ports tree was updated at Sat Jul 21 2007 16:32:01 UTC. - *net-p2p/azureus2* [EMAIL PROTECTED]: azureus2-2.5.0.4 azureus-3.0.1.6 | revision 1.46 | date: 2007/07/21 03:12:36; author: rafan; state: Exp; lines: +4 -5 | - Downgrade to 2.5.0.4. No PORTEPOCH is required since this port was just | copied from net-p2p/azureus and it's not connected to build yet. | | PR:ports/114486 | Submitted by: Robert Noland rnoland at 2hip.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports with version numbers going backwards: games/linux-doom3
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. The ports tree was updated at Thu Jul 26 2007 14:52:48 UTC. - *games/linux-doom3* [EMAIL PROTECTED]: linux-doom3-1.3.1.1304 linux-doom3-1.3.1302_2 | revision 1.7 | date: 2007/07/25 14:39:58; author: alepulver; state: Exp; lines: +14 -10 | - Update to version 1.3.1.1304. | - Install Punk Buster (for playing on-line) and expansion patches. | - Add a note in pkg-message about the expansion. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/xterm-227 does not like FreeBSD
Hi, I didn't seem to notice any problems in 227, but did upgrade to 228. Having a cut/paste issue though, but not sure if its X, window manager, or xterm (Since I did the Xorg upgrade). What part of the whole system actually does cut/pastes? Thanks, Tuc I noticed this too but it was followed by an upgrade to 228 which seems to fix it On Wed, Jul 25, 2007 at 02:11:18PM -0700, Chris Timmons wrote: Greetings, When I upgraded to x11/xterm-227, I noticed that rows and columns as reported to the terminal device by xterm were set to 0: system:/home/cwt/xterm-227 stty all speed 38400 baud; 0 rows; 0 columns; Terminal applications would not properly recognize the window size until I re-sized the window manuall. After doing some research I found this in the xterm-228 release notes: # amend changes to handshake in patch #226 to accommodate Solaris, which relies on the extra setting of the terminal size after I/O initialization. Do this by adding new resource ptySttySize, which is false for Linux and MacOS X, i.e., true for for Solaris and other SVR4 platforms, as well as FreeBSD (reports by David Wood, Renato Botelho). You may want to hold off on that 'portupgrade -a' that you know wasn't a good idea to begin with until the port is upgraded :) -Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/xterm-227 does not like FreeBSD
I noticed this too but it was followed by an upgrade to 228 which seems to fix it On Wed, Jul 25, 2007 at 02:11:18PM -0700, Chris Timmons wrote: Greetings, When I upgraded to x11/xterm-227, I noticed that rows and columns as reported to the terminal device by xterm were set to 0: system:/home/cwt/xterm-227 stty all speed 38400 baud; 0 rows; 0 columns; Terminal applications would not properly recognize the window size until I re-sized the window manuall. After doing some research I found this in the xterm-228 release notes: # amend changes to handshake in patch #226 to accommodate Solaris, which relies on the extra setting of the terminal size after I/O initialization. Do this by adding new resource ptySttySize, which is false for Linux and MacOS X, i.e., true for for Solaris and other SVR4 platforms, as well as FreeBSD (reports by David Wood, Renato Botelho). You may want to hold off on that 'portupgrade -a' that you know wasn't a good idea to begin with until the port is upgraded :) -Chris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports with version numbers going backwards: games/linux-doom3
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. The ports tree was updated at Thu Jul 26 2007 11:49:35 UTC. - *games/linux-doom3* [EMAIL PROTECTED]: linux-doom3-1.3.1.1304 linux-doom3-1.3.1302_2 | revision 1.7 | date: 2007/07/25 14:39:58; author: alepulver; state: Exp; lines: +14 -10 | - Update to version 1.3.1.1304. | - Install Punk Buster (for playing on-line) and expansion patches. | - Add a note in pkg-message about the expansion. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
samba 3.0.25b
Does anyone know when the latest samba will hit the ports tree? Or is the maintainer busy with the samba, zfs issue on current. Just curious. Regards, Johan No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.476 / Virus Database: 269.10.19/918 - Release Date: 25-7-2007 14:55 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Call for testers for yet another ports upgrade program, ports+
Yoshihiro Ota wrote: To Whom Slowness of Portupgrade Concerns a Lot: As I got tired of long waiting of portupgrade trying to resolve dependencies, I came up with yet another tool for upgrading FreeBSD ports system. Unlink other tools, it tries to maximize existing resource to maximize its performance. This program attempts to wrap around with another 'make' and expand use of FreeBSD ports system. The heart of ports+ is parsing INDEX and +CONTENTS files. The rest is handed to GNU make. I think it comes to a point where I seek wider audiences to test with it. Some short summaries of ports+ * Magnitude quicker dependency resolving compare to portupgrade. * Dependencies are resolved only once for all upgrades where portupgrade does before each 'make deinstall and make install' of ports. * Commands to execute for each ports are very flexible. * Allow concurrent builds of ports with -j option. (yet experimental) Some dry runs comparisons with about 500 ports insalled on Mobile Intel(R) Celeron(R) CPU 2.40GHz. Note that programs were run twice in a row after rebooting for each program. That is to kill disk-cache effect from the other program. The first run takes longer to read disk; however, the second run only accessed via file-cache. # time portupgrade -n -a -O 60.901u 36.208s 2:30.08 64.6% 147+13408k 4840+59io 77pf+0w # time portupgrade -n -a -O 83.581u 47.805s 2:51.34 76.6% 155+13197k 547+33io 0pf+0w # time gmake -n all 4.784u 1.982s 0:22.06 30.6% 258+2485k 1528+126io 9pf+0w # time gmake -n all 1.551u 0.205s 0:01.85 94.5% 179+8540k 0+0io 0pf+0w Three advises before trying: 1. Read the description in GNUmakefile and set PORTS+_IGNORE ports+.conf for ones you don't want to upgrade. 2. At least, backup /var/db/pkg so that you can try again even with other tools. 3. Do not 'make clean' so that you can try installing again. Ports+ requires: 1. GNU make, gmake. 2. GNU awk, gawk. 3. Up to date INDEX file. Known Issues: 1. Concurrent build with -j is still experimental although I always use it myself. There is a race condition when more than two ports updating the same +CONTENTS files at the same time. This could result +CONTENTS file out of sync. However, you could try at your risk, too. 2. If OPTIONS changes dependences of a port, ports+ won't handle it at this moment. 3. I don't know if I have to maintain any other file other than +CONTENTS. For these who want to read the description in the archive without getting one, it is copied and available at: http://uyota.asablo.jp/blog/2007/07/26/1681765 For these who want to give a shot wihtout reading further. Try these commands below. These two gmake examples are dry runs and won't harm your system. You can try with 'gmake -n' and once you are confident, you can take -n option out. # fetch http://www.ne.jp/asahi/export/uyota/src/ports+-1.59.tar.bz2 # tar xvf ports+-1.59.tar.bz2 # cd ports+1.59 # gmake test # gmake -n all Any feed backs are welcome including it works. I will applicate bug reports, suggestions on anything or specially solving +CONTENTS file race condition on parallel builds. I am indeed wondering if there is a way to queue or batch commands to run at even high load. Thanks, Hiro Hiro, You're correct when you say that reading INDEX* does take a long time for portupgrade, but the problem is partly with how portupgrade formats its version of the INDEX database in BDB format, as well as how it doesn't buffer up proper information (pkg database information for instance), and guesses at port dependencies (origins, deporigins, etc). 1. Can your solution be made bsdmake and bsd awk compatible? 2. Does your solution account for cases when you're trying to install package a, which depends on package b, but because you built package b while trying to build a, and are at an intermediate package c (between a and b), the dependencies for a are only partially complete. Thus when you try to install direct or indirect dependences, the install fails? 3. How is this different from pkg_version combined with similar scripts? ちゃんと 説明するのを頑張ってね、ほろさん ;)・・ -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports with version numbers going backwards: games/linux-doom3
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. The ports tree was updated at Thu Jul 26 2007 5:12:53 UTC. - *games/linux-doom3* [EMAIL PROTECTED]: linux-doom3-1.3.1.1304 linux-doom3-1.3.1302_2 | revision 1.7 | date: 2007/07/25 14:39:58; author: alepulver; state: Exp; lines: +14 -10 | - Update to version 1.3.1.1304. | - Install Punk Buster (for playing on-line) and expansion patches. | - Add a note in pkg-message about the expansion. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keeping Ports and Packages Synchronized
Kurt Abahar wrote: --- Doug Barton [EMAIL PROTECTED] wrote: Maybe you can describe in more detail what you're trying to accomplish. Leave out potential solutions, just describe what your goal is. I have a lot of ports installed and it takes a lot of time to compile them. Therefore, I'm trying to use packages as much as possible. After updating the ports tree using portsnap, portupgrade looks for packages that don't exist yet. Basically, my goal is to avoid this and have the ports tree update to a state for which packages have already been built. Ok, that's what I was afraid you were asking for. No such facility exists, and I don't imagine anyone creating one any time soon because it would be VERY hard to accomplish for a large number of reasons. I apologize if I can't explain it very clearly, English isn't my native language. Your description was perfect, it was my understanding of it that needed help. :) Regards, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keeping Ports and Packages Synchronized
Kurt Abahar wrote: I have tried the portupgrade way, but unfortunately the packages lag behind ports the majority of the time. It's actually 100% of the time, and always will be. This led me to think that keeping the ports tree a little behind HEAD would be a better solution. However, I don't know how to get a hold of this lag time. Is it a few days, a few weeks or ... ? Maybe you can describe in more detail what you're trying to accomplish. Leave out potential solutions, just describe what your goal is. hth, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keeping Ports and Packages Synchronized
On Jul 26, 2007, at 4:14 PM, Kurt Abahar wrote: I'm trying to find a way to keep the ports tree synchronized with that from which the latest packages in packages-6-stable were built. Is there a way to accomplish this? Sure, you probably want something like portupgrade -P or portupgrade -PP options. Note that if you have reason to select non-default options, you're better off building the ports locally to suit your preferences... -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: samba 3.0.25b
Doug Barton ha scritto: Johan Hendriks wrote: Does anyone know when the latest samba will hit the ports tree? Dude, it just came out today. Try giving people a little bit of a chance to work on it first. Nope. It came out on the 26 of *June*, exactly a month ago. (Not complaining, just being pedantic :-) bye av. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11/xterm-227 does not like FreeBSD
Yes - all fixed now. Thanks krion! On Thu, 26 Jul 2007, Adam McDougall wrote: I noticed this too but it was followed by an upgrade to 228 which seems to fix it ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Intel C v8.1 benchmark results for ruby interpreter
Hello, I use the Ruby language for work and pleasure and recently decided to test Intel C 8.1 as per the lang/icc port for the ruby interpreter, which has been shown to be quite sluggish sometimes. I have run a test on my workstation which showed a significant improvement which I wanted to share with you. The benchmark in question is a small one which generates a mandelbrot, you can find it here: http://www.timestretch.com/FractalBenchmark.html#346e82c069dbc3bc26fa841434a43ed5 1. Machine specs OS: FreeBSD 6.2-STABLE (Apr 29, 2007) i386 (32 bit) Kernel: SMP + cpu I686_CPU only + SCHED_ULE CPU: Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz (2383.99-MHz 686-class CPU) RAM: 2GB DDR1 @ 400 Motherboard: Asrock Chipset: i865 @ 1066 FSB (yes, I know) /etc/make.conf: CFLAGS=-Os COPTFLAGS=-Os CPUTYPE=prescott (One CPU core was 100% busy running some other stuff the whole time.) 2. Ruby compiled with in-built GCC gcc version 3.4.6 ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-freebsd6] Benchmark times (secs): 7.725779, 7.627775, 6.990523, 7.599726, 7.629552 Avg = 7.514671 3. Ruby compiled with ports/lang/icc 8.1 Compile options: -g -O2 ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-freebsd6.2] Benchmark times: 5.870923, 6.201353, 6.271936, 6.293150, 6.369043 Avg = 6.201281 Improvement = 17.5%! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
uppc kmod installation problem
It seems that installation action of uppc-kmod port (do-install target)
uses incorrect tool to put uppc.ko in its destination. It seems that the
tool (${INSTALL_PROGRAM}) corrupts the .ko, so that it is not a valid
kernel module anymore. If I put uppc.ko into /boot/kernel and do kldxref
then kldxref complains about missing symbol table in uppc.ko and dumps
core. If the module is loaded then it crashes my system.
On the other hand, if I simply copy uppc.ko from work directory then it
works ok.
Unfortunately I have not preserved the messages and the crash dumps but
it is very reproduce the problem without system crash using kldxref as
described above.
Current maintainer of the port seems to be ports@, so maybe I should
open a PR ?
Some system info:
FreeBSD 6.2-RELEASE-p3 amd64
uppc-kmod-0.8_1
ports tree was portsnapped last night
--
Andriy Gapon
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
FreeBSD Port: beacon-1.3
Hello Janos, I installed Multicast Beacon on FreeBSD 6.2, but after startup I've got something like this: beacon Getting configuration information from file /usr/local/etc/beacon.conf. /libexec/ld-elf.so.1: /usr/local/lib/perl5/site_perl/5.8.8/mach/auto/Net/Multicast/Beacon/Beacon.so: Undefined symbol beacon_init Do you have an idea what causes this problem? Regards Tomek ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
bug report:gnome-commander
Dear Sirs; Hello. When I tried to install gnome-commaner from /usr/ports/x11-fm/gnome-commander, instllation failed. But after installing /usr/ports/graphics/gdk-pixbuf manually, that was succeeded. Thank you. 川田昌弥 / Mr. Masaya Kawada [EMAIL PROTECTED] http://bakuretsu.atso-net.jp/bakuretsu/ Oyama, Tochigi, Japan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports with version numbers going backwards: games/linux-doom3
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. The ports tree was updated at Thu Jul 26 2007 7:32:49 UTC. - *games/linux-doom3* [EMAIL PROTECTED]: linux-doom3-1.3.1.1304 linux-doom3-1.3.1302_2 | revision 1.7 | date: 2007/07/25 14:39:58; author: alepulver; state: Exp; lines: +14 -10 | - Update to version 1.3.1.1304. | - Install Punk Buster (for playing on-line) and expansion patches. | - Add a note in pkg-message about the expansion. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerdot
On Wed, 25 Jul 2007 23:38:25 -0700
Predrag Punosevac [EMAIL PROTECTED] wrote:
Dear Victor,
Hi Predrag,
( My name is @ end of this email...the quote was from Victor Hugo :) )
I apologize if I offended anybody. I had best of intentions when I send
the first mail.
all good :)
I wish, I had knowledge to do the port myself. It never thought of that
but could you direct me to a documents from which I could learn how to
do ports
You can check the porters handbook :
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html
This document should also be available locally in your FreeBSD installation -
mine is in (EN version) /usr/share/doc/en_US.ISO8859-1/books/porters-handbook
If I understand correctly from the latest emails on the *tex ports, it seems
like it is a very big job. It may be a good idea to start with a smaller port
to get used to it first.
Best,
_
{Beto|Norberto|Numard} Meijome
The people have always some champion whom they set over them and nurse into
greatness...
This and no other is the root from which a tyrant springs; when he first
appears he is a protector.
Plato
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: samba-3.0.25a_1 - Problem following upgrade
On Wed, 25 Jul 2007, David Southwell wrote: On Wednesday 25 July 2007 08:34:47 David Southwell wrote: Following the recent upgrade I am getting errors with samba [EMAIL PROTECTED] /usr]# smbclient //localhost/test -U sambap Password: Domain=[DNS1] OS=[Unix] Server=[Samba 3.0.25a] tree connect failed: NT_STATUS_BAD_NETWORK_NAME I have tried googlling but to no avail. Can anyone point me in the right direction? Is your /usr/local/etc/smbpasswd empty? Uli. Peter Ulrich Kruppa Wuppertal Germany ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Ports upgrade
Last week i upgraded our servers when there was vulnerability on php, clamav etc, but when i finished my upgrades i faced many problems, one of it was i cannot login to some of my servers, it was bash issue after upgrading gettext port, and i see in the UPDATING file that i have to run portupgrade -rf gettext and this solve the problem of bash , i used portmanager in upgrading the ports after that i faced again many problems, one of them till now i cannot solve it, when i run vim editor i got [/libexec/ld-elf.so.1: Shared object libintl.so.6 not found, required by vim] and in my squirrelmail when i change my password also it fails with this error [ -- /libexec/ld-elf.so.1: Shared object libintl.so.6 not found, required by courierpassd ], also the same file missed, i run portupgrade on these servers but i did not solve the issue any one can guide me please how to fix my problems, because i work in ISP and these services is used by our customers my OS is Freebsd 6.1 and 6.0 thanks in advance ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: powerdot
Norberto Meijome wrote:
On Tue, 24 Jul 2007 22:05:52 -0700
Predrag Punosevac [EMAIL PROTECTED] wrote:
Well, I hope that they are aware but it seems that nobody is acting on
these issues(or at least not fast enough).
Predrag,
as good as your intentions seem to be, the results would be better if you provided help porting the apps you are interested in, or testing them, or helping.in the lists, or donating money to developers / ports / FreeBSD Foundation. Maybe you do already, and we thank you for that.
In the meantime, you and many of us will have to wait patiently for those that
are generous enough and have the time to provide the resources
(code/fixes/ports) for us to use FreeBSD for fun and profit.
Best regards,
_
{Beto|Norberto|Numard} Meijome
An invasion of armies can be resisted,
but not an idea whose time has come.
Victor Hugo
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
Dear Victor,
I apologize if I offended anybody. I had best of intentions when I send
the first mail.
I wish, I had knowledge to do the port myself. It never thought of that
but could you direct me to a documents from which I could learn how to
do ports.
Sincerely,
Predrag Punosevac
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: samba 3.0.25b
Johan Hendriks wrote: Johan Hendriks wrote: Does anyone know when the latest samba will hit the ports tree? Dude, it just came out today. Try giving people a little bit of a chance to work on it first. Doug Dude, it came out 26 of JUNE not July ;-) Umm, ok, that's a good point. In the immortal words of Emily Littela, never mind. Doug (who needs more caffeine, or less, or something) -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Overly restrictive checks in the make process
In response to Kris Kennaway [EMAIL PROTECTED]: On Sat, Jul 21, 2007 at 06:20:53AM -0400, Bill Moran wrote: Kent Stewart [EMAIL PROTECTED] wrote: On Friday 20 July 2007, Mark Linimon wrote: On Fri, Jul 20, 2007 at 04:07:49PM -0400, Bill Moran wrote: Even better would be for make to realize that it's only doing the fetching, and do it anyway. That still doesn't help with the problem of a user who starts a 10MB download that won't work on his architecture or OS release. The code is all the same. This is the aggravation we are trying to prevent. That still doesn't address the concern or improve the system downtime that a pkg_delete, make install allows. If you can't run something, you don't have any downtime but to have to pkg_delete before you start the tarball fetch can be really long on some ports. It's certainly a tradeoff. Either way you do it, there are practical scenarios where a user is inconvenienced. Perhaps an environmental override is the best route. NO_IGNORE=yes or something similar? Yes, use the NO_IGNORE variable (which just passed its tenth birthday) to override IGNORE checks you disagree with. Huh ... here I am bitching and that's been there all along ... -- Bill Moran Collaborative Fusion Inc. http://people.collaborativefusion.com/~wmoran/ [EMAIL PROTECTED] Phone: 412-422-3463x4023 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports with version numbers going backwards: net-p2p/azureus2
On Thu, Jul 26, 2007 at 12:07:48PM -0400, Kris Kennaway wrote: On Sun, Jul 22, 2007 at 01:34:08AM +0800, Rong-En Fan wrote: On Sat, Jul 21, 2007 at 05:31:49PM +, [EMAIL PROTECTED] wrote: ** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. As I noted in commit log, this port is just repocopied and not connected to build. The is intentional. If it is not connected to the build then how is it showing up here? I thought the script used INDEX builds for comparison. Honestly, I don't know. According to net-p2p/Makefile, this port is connected to build at Sat Jul 21 03:13:01 2007 UTC, i.e. 25 seconds after the commit below. Also, when I committed 2.5.0.4, the PORTNAME is changed to azureus2, so it should not be confused with azureus. Regards, Rong-En Fan Kris Regards, Rong-En Fan The ports tree was updated at Sat Jul 21 2007 16:32:01 UTC. - *net-p2p/azureus2* [EMAIL PROTECTED]: azureus2-2.5.0.4 azureus-3.0.1.6 | revision 1.46 | date: 2007/07/21 03:12:36; author: rafan; state: Exp; lines: +4 -5 | - Downgrade to 2.5.0.4. No PORTEPOCH is required since this port was just | copied from net-p2p/azureus and it's not connected to build yet. | | PR: ports/114486 | Submitted by:Robert Noland rnoland at 2hip.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] pgpVHOv3Uupgj.pgp Description: PGP signature
Re: Call for testers for yet another ports upgrade program, ports+
On Thu, 26 Jul 2007 02:17:50 -0700 Garrett Cooper [EMAIL PROTECTED] wrote: Yoshihiro Ota wrote: To Whom Slowness of Portupgrade Concerns a Lot: As I got tired of long waiting of portupgrade trying to resolve dependencies, I came up with yet another tool for upgrading FreeBSD ports system. Unlink other tools, it tries to maximize existing resource to maximize its performance. This program attempts to wrap around with another 'make' and expand use of FreeBSD ports system. The heart of ports+ is parsing INDEX and +CONTENTS files. The rest is handed to GNU make. I think it comes to a point where I seek wider audiences to test with it. Hiro, You're correct when you say that reading INDEX* does take a long time for portupgrade, but the problem is partly with how portupgrade formats its version of the INDEX database in BDB format, as well as how it doesn't buffer up proper information (pkg database information for instance), and guesses at port dependencies (origins, deporigins, etc). Portupgrade is not only slow reading INDEX file but also on dependency resolving and updating +CONTENTS files, too. I think portmaster is also one tries to read and do the same things but with shell script. I personally didn't have good luck with portmaster and haven't really used to evaluate. However, portmaster -a -n wasn't not fast, neither. By the way, it builds ports in background, doesn't it? 1. Can your solution be made bsdmake and bsd awk compatible? I am not as familiar in newer BSD awk and make extensions. I can point out what kinds of GNU extensions are being used so that someone can tell it is also available in BSD make/awk. For awk, this feature is required, quoted from man gawk. I am not sure if BSD awk implements this feature. The book indicates that command line variable assignment happens when awk would otherwise open the argument as a file, which is after the BEGIN block is executed. However, in earlier implementations, when such an assignment appeared before any file names, the assignment would happen before the BEGIN block was run. Applications came to depend on this feature. When awk was changed to match its documentation, the -v option for assigning variables before program execution was added to accommodate applications that depended upon the old behavior. (This feature was agreed upon by both the Bell Laboratories and the GNU developers.) For make, 1.1 and 1.2 below are in the same topic. I use GNU extension which keeps generating makefiles until dependency rule saticifies and use it part of the make rule. GNU extension reloads newer makefiles and reconstruct dependencies. I am not sure if it is possible in BSD make; however, this is not a heart of this program. We can work around with bootstrap script or something. 1.3 This is recursive expansion of variables. If you take a look, every port needs upgrade uses $(UPGRADE). $(UPGRADE) is expanded multiple times using the target variable, $@, such that it backups up correct old package names and so on. This is very important and unless this works in BSD make, my tool really needed full redesign from scratch. 1.4 is just how GNU make does shell invocations. It is available in most of Make tools. 1.5 is something I am not sure which makes support these. I don't think GUN make recommends using special characters as variable names. However, when I tried, it was too difficult to normalize to alphabets and underscore only. If we cannot use variable like PORTS+IGNORE as a variable name, it will be very difficult and personally I don't even think about trying that myself. If you take a look at compat.gmk which ports+ generates as a part of its build rule, you can find something like COMPAT_$(PKG_DIR)Hermes-1.3.3_2 = cp -f /usr/local/lib/libHermes.so.1 /usr/local/lib/compat/pkg being variable. 1.1 How makefiles get remade: http://uw713doc.sco.com/cgi-bin/info2html?(make.info)Remaking%2520Makefileslang=en 1.2 Including Other Makefiles: http://uw713doc.sco.com/cgi-bin/info2html?(make.info)Includelang=en 1.3 Computed Variable Names or recursive expandsion of variables: http://uw713doc.sco.com/cgi-bin/info2html?(make.info)Computed%2520Nameslang=en 1.4 The `shell' Function http://uw713doc.sco.com/cgi-bin/info2html?(make.info)Shell%2520Functionlang=en 1.5 Special characters in variable names such as dot, ., comma, ,, slash, /, and so on. 2. Does your solution account for cases when you're trying to install package a, which depends on package b, but because you built package b while trying to build a, and are at an intermediate package c (between a and b), the dependencies for a are only partially complete. Thus when you try to install direct or indirect dependences, the install fails? Some of answers are explain in the GNUmakefile. Anyway, ports+ categorizes all ports
RE: samba 3.0.25b
Johan Hendriks wrote: Does anyone know when the latest samba will hit the ports tree? Dude, it just came out today. Try giving people a little bit of a chance to work on it first. Doug Dude, it came out 26 of JUNE not July ;-) I just asked because most of the time it only takes a week or 3 and because of the issue with ZFS i was just asking. Johan ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: emacs22
Hi,
At Wed, 25 Jul 2007 01:56:01 +0900,
Hajimu UMEMOTO wrote:
Perhaps, the following patch fixes your problem. This patch changes
to obey default EMACS_PORT_NAME defined in bsd.emacs.mk, as well.
Index: databases/lsdb/Makefile
diff -u databases/lsdb/Makefile.orig databases/lsdb/Makefile
--- databases/lsdb/Makefile.orig Mon May 21 05:03:59 2007
+++ databases/lsdb/Makefile Wed Jul 25 01:48:39 2007
@@ -18,11 +18,13 @@
BUILD_DEPENDS=
${LOCALBASE}/share/flim/${FLIM_COOKIE}:${PORTSDIR}/editors/flim${DEPPORT_SUFFIX}
USE_EMACS= yes
-EMACS_PORT_NAME?=emacs21
-.if (${EMACS_PORT_NAME} == emacs21)
-DEPPORT_SUFFIX=
-.else
+
+.include bsd.port.pre.mk
+
+.if ${EMACS_PORT_NAME} == emacs20
DEPPORT_SUFFIX= -${EMACS_PORT_NAME}
+.else
+DEPPORT_SUFFIX=
.endif
SFJP_RELEASE_ID= 1494
@@ -40,4 +42,4 @@
${INSTALL_DATA} ${WRKSRC}/README ${DOCSDIR}
.endif
-.include bsd.port.mk
+.include bsd.port.post.mk
Seems fine. I've installed it into ports tree.
Best regards,
--
Yoichi NAKAYAMA
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keeping Ports and Packages Synchronized
--- Doug Barton [EMAIL PROTECTED] wrote: No such facility exists, and I don't imagine anyone creating one any time soon because it would be VERY hard to accomplish for a large number of reasons. If you don't mind, could you please elaborate on this? Side note: I'm asking because I would definitely be willing to contribute since this would make using ports and packages together much easier. I also think that such a configuration would be a better default for portsnap. Thank you Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games. http://sims.yahoo.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keeping Ports and Packages Synchronized
--- Doug Barton [EMAIL PROTECTED] wrote: Maybe you can describe in more detail what you're trying to accomplish. Leave out potential solutions, just describe what your goal is. I have a lot of ports installed and it takes a lot of time to compile them. Therefore, I'm trying to use packages as much as possible. After updating the ports tree using portsnap, portupgrade looks for packages that don't exist yet. Basically, my goal is to avoid this and have the ports tree update to a state for which packages have already been built. I apologize if I can't explain it very clearly, English isn't my native language. Thank you Yahoo! oneSearch: Finally, mobile search that gives answers, not web links. http://mobile.yahoo.com/mobileweb/onesearch?refer=1ONXIC ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Keeping Ports and Packages Synchronized
Le Ven 27 jul 07 à 3:44:32 +0200, Doug Barton [EMAIL PROTECTED] écrivait : Kurt Abahar wrote: I have a lot of ports installed and it takes a lot of time to compile them. Therefore, I'm trying to use packages as much as possible. After updating the ports tree using portsnap, portupgrade looks for packages that don't exist yet. Basically, my goal is to avoid this and have the ports tree update to a state for which packages have already been built. Ok, that's what I was afraid you were asking for. No such facility exists, and I don't imagine anyone creating one any time soon because it would be VERY hard to accomplish for a large number of reasons. Michel Talon's pkgupgrade attempt to solve this problem: see http://www.lpthe.jussieu.fr/~talon/freebsdports.html#htoc19. Regards, -- Th. Thomas. pgpfr6h9Ho93h.pgp Description: PGP signature
