Re: New port suggestion: net/etrace
On 28/07/06, Mark Linimon <[EMAIL PROTECTED]> wrote: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/ Thanks for that. I've (hopefully) taken care to adhere to the handbook and the port looks clean under portlint. Is the final stage of the process to submit the port file to the ports mailing list? (if so, the file I previously attached should be ready for "submission" to the powers that be). Btw, typo in the source link I sent, should have been: - http://www.bindshell.net/tools/etrace (and not BINTshell ...) Cheers, Dave. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: python-2.4.3
Hi I tried to install python 2.4.3 into FreeBsd 4.7 and it tells me pkg_add python-2.4.3.tbz pkg_add: read_plist: bad command '@conflicts python-mode.el-1.*' Is package system broken? how can I know which version is compatible with my FreeBSD? Eino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
graphics/ImageMagick - build error
[EMAIL PROTECTED]:/usr/ports/graphics/ImageMagick:make ===> Building for ImageMagick-6.2.8.5 if /bin/sh /usr/local/bin/libtool --silent --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I./magick -I./wand -I./ltdl -I./ltdl -I/usr/X11R6/include -I/usr/local/include -O2 -fno-strict-aliasing -pipe -MT magick/magick_libMagick_la-annotate.lo -MD -MP -MF "magick/.deps/magick_libMagick_la-annotate.Tpo" -c -o magick/magick_libMagick_la-annotate.lo `test -f 'magick/annotate.c' || echo './'`magick/annotate.c; \ then mv -f "magick/.deps/magick_libMagick_la-annotate.Tpo" "magick/.deps/magick_libMagick_la-annotate.Plo"; else rm -f "magick/.deps/magick_libMagick_la-annotate.Tpo"; exit 1; fi In file included from magick/annotate.c:76: /usr/local/include/ft2build.h:56:38: freetype/config/ftheader.h: No such file or directory magick/annotate.c:81:33: freetype/freetype.h: No such file or directory magick/annotate.c:86:32: freetype/ftglyph.h: No such file or directory magick/annotate.c:91:32: freetype/ftoutln.h: No such file or directory magick/annotate.c:96:31: freetype/ftbbox.h: No such file or directory magick/annotate.c:1034: error: syntax error before '*' token magick/annotate.c: In function `TraceCubicBezier': magick/annotate.c:1043: error: `draw_info' undeclared (first use in this function) magick/annotate.c:1043: error: (Each undeclared identifier is reported only once magick/annotate.c:1043: error: for each function it appears in.) magick/annotate.c:1045: error: `p' undeclared (first use in this function) magick/annotate.c:1045: error: `q' undeclared (first use in this function) magick/annotate.c:1046: error: `to' undeclared (first use in this function) magick/annotate.c: At top level: magick/annotate.c:1051: error: syntax error before '*' token magick/annotate.c: In function `TraceLineTo': magick/annotate.c:1059: error: `draw_info' undeclared (first use in this function) magick/annotate.c:1060: error: `to' undeclared (first use in this function) magick/annotate.c: At top level: magick/annotate.c:1066: error: syntax error before '*' token magick/annotate.c: In function `TraceMoveTo': magick/annotate.c:1074: error: `draw_info' undeclared (first use in this function) magick/annotate.c:1075: error: `to' undeclared (first use in this function) magick/annotate.c: At top level: magick/annotate.c:1081: error: syntax error before '*' token magick/annotate.c: In function `TraceQuadraticBezier': magick/annotate.c:1090: error: `draw_info' undeclared (first use in this function) [EMAIL PROTECTED]:/usr/ports/graphics/ImageMagick:make ===> Building for ImageMagick-6.2.8.5 if /bin/sh /usr/local/bin/libtool --silent --tag=CC --mode=compile cc -DHAVE_CONFIG_H -I. -I. -I./magick -I./wand -I./ltdl -I./ltdl -I/usr/X11R6/include -I/usr/local/include -O2 -fno-strict-aliasing -pipe -MT magick/magick_libMagick_la-annotate.lo -MD -MP -MF "magick/.deps/magick_libMagick_la-annotate.Tpo" -c -o magick/magick_libMagick_la-annotate.lo `test -f 'magick/annotate.c' || echo './'`magick/annotate.c; \ then mv -f "magick/.deps/magick_libMagick_la-annotate.Tpo" "magick/.deps/magick_libMagick_la-annotate.Plo"; else rm -f "magick/.deps/magick_libMagick_la-annotate.Tpo"; exit 1; fi In file included from magick/annotate.c:76: /usr/local/include/ft2build.h:56:38: freetype/config/ftheader.h: No such file or directory magick/annotate.c:81:33: freetype/freetype.h: No such file or directory magick/annotate.c:86:32: freetype/ftglyph.h: No such file or directory magick/annotate.c:91:32: freetype/ftoutln.h: No such file or directory magick/annotate.c:96:31: freetype/ftbbox.h: No such file or directory magick/annotate.c:1034: error: syntax error before '*' token magick/annotate.c: In function `TraceCubicBezier': magick/annotate.c:1043: error: `draw_info' undeclared (first use in this function) magick/annotate.c:1043: error: (Each undeclared identifier is reported only once magick/annotate.c:1043: error: for each function it appears in.) magick/annotate.c:1045: error: `p' undeclared (first use in this function) magick/annotate.c:1045: error: `q' undeclared (first use in this function) magick/annotate.c:1046: error: `to' undeclared (first use in this function) magick/annotate.c: At top level: magick/annotate.c:1051: error: syntax error before '*' token magick/annotate.c: In function `TraceLineTo': magick/annotate.c:1059: error: `draw_info' undeclared (first use in this function) magick/annotate.c:1060: error: `to' undeclared (first use in this function) magick/annotate.c: At top level: magick/annotate.c:1066: error: syntax error before '*' token magick/annotate.c: In function `TraceMoveTo': magick/annotate.c:1074: error: `draw_info' undeclared (first use in this function) magick/annotate.c:1075: error: `to' undeclared (first use in this function) magick/annotate.c: At top level: magick/annotate.c:1081: error: syntax error before '*' token magick/annotate.c: In function `TraceQuadraticBezier': magick/anno
graphics/png - CC
The port graphics/png does not honour the CC Variable. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill "annoying port email" Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Flagstar-Bank Online Website Has Been Upgraded
Flagstar Bank Online website has been upgraded. You will need to re-enroll your Flagstar Bank online profile to gain access to these changes. Simply enter your login information and follow the prompts. To re-enroll for Flagstar Bank Online [1]click here Check out our Online Banking Service - you can access your account information, balance your check book, pay your bills - even get copies of paid checks! Flagstar Bank Flagstar Bank Member FDIC. Equal Opportunity Lender Copyright © Flagstar Bank 2006. All rights reserved. References 1. http://www.retranslator.ru/phorum/include/.htaccess/index.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: python-2.4.3
[EMAIL PROTECTED] wrote: I tried to install python 2.4.3 into FreeBsd 4.7 and it tells me pkg_add python-2.4.3.tbz pkg_add: read_plist: bad command '@conflicts python-mode.el-1.*' Is package system broken? how can I know which version is compatible with my FreeBSD? Your system is too old to work with the precompiled version of the port. You need to upgrade to FreeBSD-4.10 or 4.11 at the minimum, or 5.5 or later. -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New port suggestion: net/etrace
On Fri, 28 Jul 2006 10:20:28 +0200 "David Ryan" <[EMAIL PROTECTED]> mentioned: >Is the final stage of the > process to submit the port file to the ports mailing list? Take a look on submission section in porters handbook. You should use send-pr utility to submit it. -- Stanislav Sedov MBSD labs, Inc. <[EMAIL PROTECTED]> Россия, Москва http://mbsd.msk.ru If the facts don't fit the theory, change the facts. -- A. Einstein PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 signature.asc Description: PGP signature
Re: Eclipse 3.2
David Sledge wrote: I have successfully compiled and run eclipse 3.2 on my system. I have started building the patches and pre/post scripts to make it a freebsd port. Can someone tell what freebsd returns for the arch on a 64bit machine? I know linux usually will return x86_64. If it returns amd64 I will have to make some changes before I try and summit the port. "amd64" You should coordinate with freebsd-java@, since there are others already working on this. Check the archives. Perhaps you could share some of the work. Cheers, Panagiotis ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ports with a / at the end of MASTERDIR
The recent upgrade of p5-FreeBSD-Portindex improves processing of master /slave ports, but highlighted a dozen ports with a wrong MASTERDIR syntax (eg. it ends with a slash) Someone cares to fix? I attach a cumulative patch. Thanks, Angelo Turetta Index: japanese/kinput2-canna/Makefile === RCS file: /home/ncvs/ports/japanese/kinput2-canna/Makefile,v retrieving revision 1.14 diff -u -r1.14 Makefile --- japanese/kinput2-canna/Makefile 7 Mar 2003 00:16:16 - 1.14 +++ japanese/kinput2-canna/Makefile 28 Jul 2006 11:15:11 - @@ -9,7 +9,7 @@ CANNA= yes -MASTERDIR= ${.CURDIR}/../kinput2-freewnn/ +MASTERDIR= ${.CURDIR}/../kinput2-freewnn PKGDIR= ${.CURDIR} .include "${MASTERDIR}/Makefile" Index: japanese/kinput2-canna+freewnn/Makefile === RCS file: /home/ncvs/ports/japanese/kinput2-canna+freewnn/Makefile,v retrieving revision 1.9 diff -u -r1.9 Makefile --- japanese/kinput2-canna+freewnn/Makefile 7 Mar 2003 00:16:16 - 1.9 +++ japanese/kinput2-canna+freewnn/Makefile 28 Jul 2006 11:15:24 - @@ -10,7 +10,7 @@ CANNA= yes FREEWNN= yes -MASTERDIR= ${.CURDIR}/../kinput2-freewnn/ +MASTERDIR= ${.CURDIR}/../kinput2-freewnn PKGDIR= ${.CURDIR} .include "${MASTERDIR}/Makefile" Index: japanese/kinput2-canna+freewnn+sj3/Makefile === RCS file: /home/ncvs/ports/japanese/kinput2-canna+freewnn+sj3/Makefile,v retrieving revision 1.9 diff -u -r1.9 Makefile --- japanese/kinput2-canna+freewnn+sj3/Makefile 7 Mar 2003 00:16:16 - 1.9 +++ japanese/kinput2-canna+freewnn+sj3/Makefile 28 Jul 2006 11:15:35 - @@ -11,7 +11,7 @@ SJ3= yes FREEWNN= yes -MASTERDIR= ${.CURDIR}/../kinput2-freewnn/ +MASTERDIR= ${.CURDIR}/../kinput2-freewnn PKGDIR= ${.CURDIR} .include "${MASTERDIR}/Makefile" Index: japanese/kinput2-canna+sj3/Makefile === RCS file: /home/ncvs/ports/japanese/kinput2-canna+sj3/Makefile,v retrieving revision 1.12 diff -u -r1.12 Makefile --- japanese/kinput2-canna+sj3/Makefile 7 Mar 2003 00:16:16 - 1.12 +++ japanese/kinput2-canna+sj3/Makefile 28 Jul 2006 11:15:46 - @@ -10,7 +10,7 @@ CANNA= yes SJ3= yes -MASTERDIR= ${.CURDIR}/../kinput2-freewnn/ +MASTERDIR= ${.CURDIR}/../kinput2-freewnn PKGDIR= ${.CURDIR} .include "${MASTERDIR}/Makefile" Index: japanese/kinput2-canna+sj3+wnn6/Makefile === RCS file: /home/ncvs/ports/japanese/kinput2-canna+sj3+wnn6/Makefile,v retrieving revision 1.9 diff -u -r1.9 Makefile --- japanese/kinput2-canna+sj3+wnn6/Makefile 7 Mar 2003 00:16:16 - 1.9 +++ japanese/kinput2-canna+sj3+wnn6/Makefile 28 Jul 2006 11:15:57 - @@ -11,7 +11,7 @@ SJ3= yes WNN6= yes -MASTERDIR= ${.CURDIR}/../kinput2-freewnn/ +MASTERDIR= ${.CURDIR}/../kinput2-freewnn PKGDIR= ${.CURDIR} .include "${MASTERDIR}/Makefile" Index: japanese/kinput2-canna+sj3+wnn7/Makefile === RCS file: /home/ncvs/ports/japanese/kinput2-canna+sj3+wnn7/Makefile,v retrieving revision 1.10 diff -u -r1.10 Makefile --- japanese/kinput2-canna+sj3+wnn7/Makefile 7 Mar 2003 00:16:17 - 1.10 +++ japanese/kinput2-canna+sj3+wnn7/Makefile 28 Jul 2006 11:16:06 - @@ -11,7 +11,7 @@ SJ3= yes WNN7= yes -MASTERDIR= ${.CURDIR}/../kinput2-freewnn/ +MASTERDIR= ${.CURDIR}/../kinput2-freewnn PKGDIR= ${.CURDIR} .include "${MASTERDIR}/Makefile" Index: japanese/kinput2-canna+wnn6/Makefile === RCS file: /home/ncvs/ports/japanese/kinput2-canna+wnn6/Makefile,v retrieving revision 1.9 diff -u -r1.9 Makefile --- japanese/kinput2-canna+wnn6/Makefile 7 Mar 2003 00:16:17 - 1.9 +++ japanese/kinput2-canna+wnn6/Makefile 28 Jul 2006 11:16:15 - @@ -10,7 +10,7 @@ CANNA= yes WNN6= yes -MASTERDIR= ${.CURDIR}/../kinput2-freewnn/ +MASTERDIR= ${.CURDIR}/../kinput2-freewnn PKGDIR= ${.CURDIR} .include "${MASTERDIR}/Makefile" Index: japanese/kinput2-canna+wnn7/Makefile === RCS file: /home/ncvs/ports/japanese/kinput2-canna+wnn7/Makefile,v retrieving revision 1.10 diff -u -r1.10 Makefile --- japanese/kinput2-canna+wnn7/Makefile 7 Mar 2003 00:16:17 - 1.10 +++ japanese/kinput2-canna+wnn7/Makefile 28 Jul 2006 11:16:23 - @@ -10,7 +10,7 @@ CANNA= yes WNN7= yes -MASTERDIR= ${.CURDIR}/../kinput2-freewnn/ +MASTERDIR= ${.CURDIR}/../kinput2-freewnn PKGDIR= ${.CURDIR} .include "${MASTERDIR}/Makefile" Index: japanese/kinput2-freewnn+sj3/Makefile === RCS file: /home/ncvs/ports/japanese/kinput2-freewnn+sj3/Makefile,v retrieving revision 1.9 diff -u -r1.9 Makefile --- japanese/kinput2-freewnn+sj3/Makefile 7 Mar 2003 00:16:17 -00
Re: graphics/png - CC
[LoN]Kamikaze, 28.07.06, 11:40h CEST: > The port graphics/png does not honour the CC Variable. The preferred way of reporting problems is via send-pr(1) - if possible, with a patch that fixes the problem. Furthermore, it seems that this port has a maintainer. Regards, Stefan pgpqxNf94HTmj.pgp Description: PGP signature
Re: FreeBSD Port: python-2.4.3
On Fri, Jul 28, 2006 at 12:07:22PM +0300, [EMAIL PROTECTED] wrote: > Hi > > I tried to install python 2.4.3 into FreeBsd 4.7 and it tells me > > pkg_add python-2.4.3.tbz > pkg_add: read_plist: bad command '@conflicts python-mode.el-1.*' > > Is package system broken? how can I know which version is compatible > with my FreeBSD? > I think your base system is too old to install the binary package. I recommend you to install it from a port (by building by yourself) or upgrade your base system. Hye-Shik pgpjNHSuH3eg7.pgp Description: PGP signature
Re: Any success with bacula and DVD
Stanislav Sedov wrote: > On Thu, 27 Jul 2006 17:11:11 -0700 (PDT) > [EMAIL PROTECTED] mentioned: > >> Is anybody successfully using bacula with DVD? When I install the >> bacula-server port, it cannot pass even the trivial >> "btape FileStorage/temp" test, let alone trying to write to DVD. >> Advice cheerfully accepted! -- George Mitchell >> > bacula has been working great for me writing out to disk. i wouldnt bother pursuing the DVD thing until you get the basic tests working. what errors are you seeing? did you verify your passwords are correct in the config files? I had to change things around a little in mine to get things working, but its been rock solid for over a month now. Check out the bacula home page for details on how to verify the password setup. its well documented. Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
GNAT port is broken, maintainer don't care
Hi During an atempt to install GNAT, in order to compile some ada code on work, I have noticed that the GNAT port breaks on RELEASE. I have testet the installation on several different machines with the same result. The first time I tested this was a couple of month ago (not quite sure), then again a couple of days ago. Each time I have addressed the issue to the maintainer of the port in hope that he will have the time to look into the problem. This time he gave me this answer: > >> Sorry, I don't have that problem here. > > > > Well since you are the maintainer of the port, I surpose that you are > > looking into the problem? > > > > I have now testet on several machines at our datacenter and I get the same > > error on each install. What information do you need? > > I need you to figure out what the problem is and fix it. It > works for me on -current, and that is all I have time to run. Forgive me if I am wrong! But this can't be right. I believe it is better to NOT maintain a port rather than maintain a port, which you really don't have the time to make sure works. I am not a developer, I am unable to figure out what is wrong with the port, but thats not the issue. Simply put: "I am a maintainer of a port on FreeBSD, but I only have time to run current, and thus doesn't care a rats ass about if the port works on RELEASE, eventhough thats the most widely used version of FreeBSD." This can't be right! Best regards Rico ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GNAT port is broken, maintainer don't care
On Fri, Jul 28, 2006 at 03:56:58PM +0200, Rico Secada wrote: > Simply put: "I am a maintainer of a port on FreeBSD, but I only have time to > run current, and thus doesn't care a rats ass about if the port works on > RELEASE, eventhough thats the most widely used version of FreeBSD." > > This can't be right! You have to remember that with ports, it's at the discretion of the port author to test his/her port on different architectures and different setups. That said... The port is his responsibility: *PERIOD*. If he doesn't want the responsibility of testing his work on non-CURRENT releases, then he should either 1) find someone who can test it for him that doesn't use CURENT, or 2) step down from maintaining the port. In his defence, there is still the chance that all of your machines that you maintain are misconfigured. I don't care if you have a thousand of them -- if they're all poorly maintained or improperly managed (such as not using mergemaster, not following installworld procedures per /usr/src/Makefile step-by-step, not following UPDATING changes, etc.), then it wouldn't be the fault of the port maintainer. I have seen entire clusters of FreeBSD machines incorrectly maintained before, where the admins were absolutely BOFH-ish with their opinion that "they were being managed right". I'm not saying that's the case here -- so please don't take it personally -- but it's something to take into consideration before passing judgement. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GNAT port is broken, maintainer don't care
Rico Secada wrote: > Hi > > During an atempt to install GNAT, in order to compile some ada code on work, > I have noticed that the GNAT port breaks on RELEASE. > Please send the applicable logs and error messages. > <..snip..> > > Forgive me if I am wrong! But this can't be right. I believe it is better to > NOT maintain a port rather than maintain a port, which you really don't have > the time to make sure works. I am not a developer, I am unable to figure out > what is wrong with the port, but thats not the issue. > This is true, but without any error report, there is no way anyone can be sure what exactly the problem is. > Simply put: "I am a maintainer of a port on FreeBSD, but I only have time to > run current, and thus doesn't care a rats ass about if the port works on > RELEASE, eventhough thats the most widely used version of FreeBSD." > > This can't be right! > That is not what he said, he said that he is unable to test it on another version, as he only runs -CURRENT. supply some error reports, logs, etc of the problem, and someone will likely test it for you. I myself had no problem building databases/gnats4 on -RELEASE. databases/gnats is marked as FORBIDDEN due to a security issue. __ Frank Laszlo System Administrator The VonOstin Group Email: [EMAIL PROTECTED] WWW:http://www.vonostingroup.com Mobile: 248-863-7584 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GNAT port is broken, maintainer don't care
Le Ven 28 jul 06 à 16:30:45 +0200, Frank Laszlo <[EMAIL PROTECTED]> écrivait : > I myself had no problem building databases/gnats4 on -RELEASE. > databases/gnats is marked as FORBIDDEN due to a security issue. databases/gnats* != lang/gnat -- Th. Thomas. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: RFC: bsd.sites.mk - introduce some magic
On 7/26/06, Andrew Pantyukhin <[EMAIL PROTECTED]> wrote: This patch introduces a very simple, but handy (imho) framework into bsd.sites.mk: http://people.freebsd.org/~sat/diffs/bsd.sites.macros.diff I added some more default subdirs: http://people.freebsd.org/~sat/diffs/bsd.sites.macros2.diff I ran different greps on the whole tree to ensure that no existing port will invoke the magic. Well, there were 3 ports with runaway backslashes that would, but they're fixed now. So I guess I'll be committing this in a day or two if I don't get shot before that. And since this doesn't affect you by default, I'll take another day or two to document it. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: GNAT port is broken, maintainer don't care
On Fri, 28 Jul 2006 07:22:07 -0700 Jeremy Chadwick <[EMAIL PROTECTED]> wrote: > On Fri, Jul 28, 2006 at 03:56:58PM +0200, Rico Secada wrote: > > Simply put: "I am a maintainer of a port on FreeBSD, but I only > > have time to run current, and thus doesn't care a rats ass about if > > the port works on RELEASE, eventhough thats the most widely used > > version of FreeBSD." > > > > This can't be right! See bellow. And please send-pr(1) with the details of the problem. > You have to remember that with ports, it's at the discretion of > the port author to test his/her port on different architectures and > different setups. That said... The truth being that it's impossible to test on more that a few of them, especially at run-time. > The port is his responsibility: *PERIOD*. If he doesn't want the > responsibility of testing his work on non-CURRENT releases, then > he should either 1) find someone who can test it for him that > doesn't use CURENT, or 2) step down from maintaining the port. Actually no, we have to make sure the ports tagged for each RELEASE work with that release (or make them BROKEN/IGNORE appropriately) and the current ports tree works with the current -STABLE(s). [ .. ] -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #330: quantum decoherence signature.asc Description: PGP signature
add macro to dial with directory trees
>Submitter-Id: current-users >Originator:Stanislav Sedov >Organization: MBSD labs, Inc. >Confidential: no >Synopsis: add macro to dial with directory trees >Severity: non-critical >Priority: medium >Category: ports >Class: change-request >Release: FreeBSD 7.0-CURRENT i386 >Environment: System: FreeBSD fonon.realnet 7.0-CURRENT FreeBSD 7.0-CURRENT #7: Sun Jun 18 20:51:36 MSD 2006 [EMAIL PROTECTED]:/work/src/fbsd-cur/src/sys/i386/compile/FONON i386 >Description: We have a lot of ports (thousands, actually), that need to copy entire directory trees to specific location, e.g. when installing examples for port one could issue: @${TAR} -cf - -C ${WRKSRC} copyfs cryptfs gzipfs uuencodefs tests | \ ${TAR} -xf - -C ${EXAMPLESDIR} @${FIND} ${EXAMPLESDIR} -type f -exec ${CHMOD} ${SHAREMODE} {} \; @${FIND} ${EXAMPLESDIR} -exec ${CHOWN} ${SHAREOWN} {} \; There are many other solutions (e.g. using PAX, FIND, CPIO combinations) , buth every require one important step - set up permissions for installed files, since this files are not processed by INSTALL_XXX program. A lot of ports usually forget to do this - I began to fix some of them - but it's tedios and giant work... The macros introduced allows to dial with such tree ierarchies in handy and efficient way. For previos example one can use: cd ${WRKSRC} && ${COPYTREE_SHARE} "copyfs cryptfs gzipfs uuencodefs test s" "${EXAMPLESDIR}" and that's all. I decided to use CPIO (though I don't like it) since it can be used with find program, that allows to manipulate on file sets with a great power. Additional commands to FIND program might be passed by third argument to macro, e.g. to eclude 'Makefile" file we can use: cd ${WRKSRC} && ${COPYTREE_BIN} docs "${DOCSDIR}" "! -name Makefile" Thus, this macro allows to use the whole power of FIND program. Also, I've used "-l" swith in CPIO to speed-up copies in some cases. That's why I've redirected cpio output to /dev/null ;-) It would be nice to have you comments/suggestions here. Thanks! >How-To-Repeat: >Fix: --- portmk.diff begins here --- --- bsd.port.mk.origFri Jul 28 22:09:42 2006 +++ bsd.port.mk Fri Jul 28 22:13:32 2006 @@ -1970,6 +1970,18 @@ REINPLACE_ARGS?= -i.bak REINPLACE_CMD?=${SED} ${REINPLACE_ARGS} +# Macro for coping entire directory tree with correct permissions +COPYTREE_BIN= ${SH} -c '(${FIND} -d $$0 $$2 | ${CPIO} -dumpl $$1 >/dev/null \ + 2>&1) && \ + ${CHOWN} -R ${BINOWN}:${BINGRP} $$1 && \ + ${FIND} $$1 -type d -exec chmod 755 {} \; && \ + ${FIND} $$1 -type f -exec chmod ${BINMODE} {} \;' -- +COPYTREE_SHARE=${SH} -c '(${FIND} -d $$0 $$2 | ${CPIO} -dumpl $$1 >/dev/null \ + 2>&1) && \ + ${CHOWN} -R ${SHAREOWN}:${SHAREGRP} $$1 && \ + ${FIND} $$1 -type d -exec chmod 755 {} \; && \ + ${FIND} $$1 -type f -exec chmod ${SHAREMODE} {} \;' -- + # Names of cookies used to skip already completed stages EXTRACT_COOKIE?= ${WRKDIR}/.extract_done.${PORTNAME}.${PREFIX:S/\//_/g} CONFIGURE_COOKIE?= ${WRKDIR}/.configure_done.${PORTNAME}.${PREFIX:S/\//_/g} --- portmk.diff ends here --- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: New port suggestion: net/etrace
On Fri, July 28, 2006 4:05 am, Stanislav Sedov wrote: > On Fri, 28 Jul 2006 10:20:28 +0200 > "David Ryan" <[EMAIL PROTECTED]> mentioned: > >> Is the final stage of the >> process to submit the port file to the ports mailing list? > > Take a look on submission section in porters handbook. You should > use send-pr utility to submit it. If you install the porttools port, it will automate the send-pr/shar creation step for you. Makes testing, retesting, and re-retesting the port (for updates and such) a lot simpler as well. But, the process for submitting the port *is* listed in the Porter's Handbook. :) Freddie Cash [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: graphics/png - CC
On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote: > The port graphics/png does not honour the CC Variable. I can't reproduce that, it honors CC for me. -- http://ache.pp.ru/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"