unsubscribe
Renaud Baboin
rbaboin at mac.com
Thu Apr 22 11:19:26 PDT 2004
Le 22 avr. 04, à 19:36, freebsd-ports-request at freebsd.org a écrit :
> Send freebsd-ports mailing list submissions to
> freebsd-ports at freebsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> or, via email, send a message with subject or body 'help' to
> freebsd-ports-request at freebsd.org
>
> You can reach the person managing the list at
> freebsd-ports-owner at freebsd.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of freebsd-ports digest..."
>
>
> Today's Topics:
>
> 1. Bugfix to dvd+rw-tools... (Charles Swiger)
> 2. setting up a ports infrastructure outside of /usr/ports
> (Oliver Fischer)
> 3. Re: Ethereal (Jacob S. Barrett)
> 4. linux_mesa3 (Alex Ethan Kelly)
> 5. Re: Scribus-Port (Lee Harr)
> 6. Re: Scribus-Port (Kris Kennaway)
> 7. Re: Scribus-Port (Lee Harr)
> 8. FreeBSD Port: pppd23-2.3.11 (ZOleg)
> 9. Re: security/gringotts won't recompile after GNOME 2.6
> upgrade (Joe Marcus Clarke)
> 10. Re: ports/40699: [patch] allow exclude patterns in `make
> search` (Roman Neuhauser)
> 11. Re: setting up a ports infrastructure outside of /usr/ports
> (Michael C. Shultz)
> 12. FreeBSD Port: gxine-0.3.3 (Joe Zeiler)
> 13. Re: setting up a ports infrastructure outside of /usr/ports
> (Volker Stolz)
> 14. Re: setting up a ports infrastructure outside of /usr/ports
> (Matthew Seaman)
> 15. Re: setting up a ports infrastructure outside of /usr/ports
> (Matthew Seaman)
> 16. Re: FreeBSD Port: XFree86-libraries-4.3.0_7 (Ryan Merrick)
> 17. Re: FreeBSD Port: gxine-0.3.3 (Jeremy Messenger)
> 18. mutt change breaks vim syntax highlighting (Jean-Baptiste Quenot)
> 19. ports build && make -j<something> (Joerg Wunsch)
> 20. FreeBSD Port: ispell-3.2.06 (Tomas Levin)
> 21. Re: FreeBSD Port: ispell-3.2.06 (Kris Kennaway)
> 22. Re: FreeBSD Port: ispell-3.2.06 (Jean-Marc Zucconi)
> 23. Re: mutt change breaks vim syntax highlighting (Udo Schweigert)
> 24. FreeBSD Port: pgbash-7.3_1 (Dmitriy Shnayder)
> 25. Re: mutt change breaks vim syntax highlighting
> (Jean-Baptiste Quenot)
> 26. Re: setting up a ports infrastructure outside of /usr/ports
> (Dirk Meyer)
> 27. Re: FreeBSD Port: pgbash-7.3_1 (Michael Nottebrock)
> 28. Re: ports/63192: mutt change breaks vim syntax highlighting
> (Udo Schweigert)
> 29. Re: Bugfix to dvd+rw-tools... (Jim Hatfield)
> 30. Re: ports/63427: [lang/gcc33] Disabling the Java frontend at
> compile time (Gerald Pfeifer)
> 31. Re: Bugfix to dvd+rw-tools... (Chuck Swiger)
> 32. Re: FreeBSD Port: pgbash-7.3_1 (Sascha Holzleiter)
> 33. Re: [ports-i386 at bento.FreeBSD.org:
> pure-xemacs-devel-mule-0.6_1 failed on i386 4] (Yoichi NAKAYAMA)
> 34. Re: Ethereal (Roman Neuhauser)
> 35. gtar update: opinions sought (Christian Weisgerber)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Wed, 21 Apr 2004 17:30:52 -0400
> From: Charles Swiger <cswiger at mac.com>
> Subject: Bugfix to dvd+rw-tools...
> To: ports at FreeBSD.org
> Message-ID: <2A810C16-93DB-11D8-90F9-003065ABFD92 at mac.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi, all--
>
> A problem has been reported with the latest version of dvd+rw-tools:
>
> "IMPORTANT NOTE! A bug was introduced in version 5.19, which manifests
> itself by inability to finalize recording, it takes forever to "flush
> cache." Apply hotfix or download patched tar-ball. If you have suffered
> from this bug and have non-finalized DVD±R media, you can use this
> snippet to "revive" it. DVD+RW media can be finalized with
> dvd+rw-format -lead-out."
>
> The tool to fix unfinalized DVD±R disk is at:
>
> http://fy.chalmers.se/~appro/linux/DVD+RW/tools/close.cpp
>
> ...and ports/65861 contains the patch. If you've encountered the
> problem described above, please give 'em a try and let me know whether
> they help. Thanks,
>
> --
> -Chuck
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 22 Apr 2004 00:11:22 +0200
> From: Oliver Fischer <plexus at snafu.de>
> Subject: setting up a ports infrastructure outside of /usr/ports
> To: freebsd-ports at freebsd.org
> Message-ID: <4086F18A.8010100 at snafu.de>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Hello,
>
> I would like to ports some programs but before I will start, I would
> like to have a separate directory for it. So so my question is:
>
> Is it possible:
>
> 1. to have the ports directory in my home directory? I
> think yes.
>
> 2. to build and to install a port as normal user to
> a via PREFIX specified directory?
>
> 3. to use a different pkgdb directory than /var/db/pkg for
> the ports build in this manner?
>
>
> Regards,
> Oliver Fischer
>
> ------------------------------
>
> Message: 3
> Date: Wed, 21 Apr 2004 15:30:56 -0700
> From: "Jacob S. Barrett" <jbarrett at amduat.net>
> Subject: Re: Ethereal
> To: ports at freebsd.org
> Message-ID: <200404211530.56264.jbarrett at amduat.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Wednesday 21 April 2004 09:57 am, Roman Neuhauser
> <neuhauser at chello.cz>
> wrote:
>> # jbarrett at amduat.net / 2004-04-21 06:57:20 -0700:
>>> I have rebuilt and installed ethereal a dozen times from ports and
>>> every time it just installs tethereal and not ethereal. I have
>>> explicitly set the WITH_GTK2 and still nothing. What am I doing
>>> wrong?
>>
>> Anything suspicious in ${WRKSRC}/config.log ?
>
> checking for GTK+ - version >= 2.0.0... no
> *** Could not run GTK+ test program, checking why...
> *** The test program failed to compile or link. See the file
> config.log for
> the
> *** exact error that occured. This usually means GTK+ is incorrectly
> installed.
>
> configure:9102: checking for GTK+ - version >= 2.0.0
> configure:9247: result: no
> configure:9280: cc -o conftest -D_U_="__attribute__((unused))" -Wall
> -W -O
> -pipe -march=pentiumpro -I/usr/local/include -I/usr/local/include
> -L/usr/local/lib conftest.c >&5
> conftest.c:24:21: gtk/gtk.h: No such file or directory
> conftest.c: In function `main':
> conftest.c:30: error: `gtk_major_version' undeclared (first use in this
> function)
> conftest.c:30: error: (Each undeclared identifier is reported only once
> conftest.c:30: error: for each function it appears in.)
> conftest.c:30: error: `gtk_minor_version' undeclared (first use in this
> function)
> conftest.c:30: error: `gtk_micro_version' undeclared (first use in this
> function)
>
>
> --
> Jacob S. Barrett
> jbarrett at amduat.net
> www.amduat.net
>
> "I don't suffer from insanity, I enjoy every minute of it."
>
> ------------------------------
>
> Message: 4
> Date: Wed, 21 Apr 2004 18:59:30 -0400
> From: Alex Ethan Kelly <alexkelly at adelphia.net>
> Subject: linux_mesa3
> To: ports at freebsd.org
> Message-ID: <200404211859.30805.alexkelly at adelphia.net>
> Content-Type: text/plain; charset="us-ascii"
>
> While attempting a make install of linux_mesa3, all the links to
> XFree86-devel-4.1.0-49.i386.rpm were broken.
>
> Is this a broken port?
>
> Thanks,
> Alex
>
>
> ------------------------------
>
> Message: 5
> Date: Wed, 21 Apr 2004 23:46:14 +0000
> From: "Lee Harr" <missive at hotmail.com>
> Subject: Re: Scribus-Port
> To: freebsd-ports at freebsd.org
> Message-ID: <BAY2-F1087TMTS5X0xu00013ffd at hotmail.com>
> Content-Type: text/plain; format=flowed
>
>> Here is an update to version 1.1.6:
>>
>> http://people.freebsd.org/~markus/stuff/scribus.diff
>>
>
>
> I tried this (on a slightly dated -stable). It built, but does not
> start up...
>
>
>> scribus
> rcmdsh: unknown user: ĨuÄüj
> rcmdsh: unknown user: Ä FX
>
>
> The splash screen is showing "Reading Scrapbook" and I
> have to kill -9 the process to make it stop.
>
> _________________________________________________________________
> Add photos to your messages with MSN 8. Get 2 months FREE*.
> http://join.msn.com/?page=features/featuredemail
>
>
> ------------------------------
>
> Message: 6
> Date: Wed, 21 Apr 2004 16:50:19 -0700
> From: Kris Kennaway <kris at obsecurity.org>
> Subject: Re: Scribus-Port
> To: Lee Harr <missive at hotmail.com>
> Cc: freebsd-ports at freebsd.org
> Message-ID: <20040421235019.GA86880 at xor.obsecurity.org>
> Content-Type: text/plain; charset="us-ascii"
>
> On Wed, Apr 21, 2004 at 11:46:14PM +0000, Lee Harr wrote:
>>> Here is an update to version 1.1.6:
>>>
>>> http://people.freebsd.org/~markus/stuff/scribus.diff
>>>
>>
>>
>> I tried this (on a slightly dated -stable). It built, but does not
>> start up...
>>
>>
>>> scribus
>> rcmdsh: unknown user: ??u??j
>> rcmdsh: unknown user: ? FX
>>
>>
>> The splash screen is showing "Reading Scrapbook" and I
>> have to kill -9 the process to make it stop.
>
> Does the port link explicitly to libc during the build? Volker Stolz
> discovered that this can cause the error you're seeing. If so, try
> preventing the port from linking with -lc.
>
> Kris
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 187 bytes
> Desc: not available
> Url :
> http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040421/
> c3ce40e9/attachment-0001.bin
>
> ------------------------------
>
> Message: 7
> Date: Thu, 22 Apr 2004 01:48:29 +0000
> From: "Lee Harr" <missive at hotmail.com>
> Subject: Re: Scribus-Port
> To: freebsd-ports at freebsd.org
> Message-ID: <BAY2-F15931pHy82G4n000197b0 at hotmail.com>
> Content-Type: text/plain; format=flowed
>
>>>> Here is an update to version 1.1.6:
>>>>
>>>> http://people.freebsd.org/~markus/stuff/scribus.diff
>>>>
>>>
>>>
>>> I tried this (on a slightly dated -stable). It built, but does not
>>> start up...
>>>
>>>
>>>> scribus
>>> rcmdsh: unknown user: ??u??j
>>> rcmdsh: unknown user: ? FX
>>>
>>>
>>> The splash screen is showing "Reading Scrapbook" and I
>>> have to kill -9 the process to make it stop.
>>
>> Does the port link explicitly to libc during the build? Volker Stolz
>> discovered that this can cause the error you're seeing. If so, try
>> preventing the port from linking with -lc.
>>
>
>
> Yes, I re-ran the link step removing the -lc and now it starts up
> normally. I am not sure how to change the Makefile to do that
> automatically.
>
> _________________________________________________________________
> Help STOP SPAM with the new MSN 8 and get 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>
>
> ------------------------------
>
> Message: 8
> Date: Thu, 22 Apr 2004 11:25:36 +0900
> From: ZOleg <zoleg at buryatia.ru>
> Subject: FreeBSD Port: pppd23-2.3.11
> To: netch at netch.kiev.ua
> Cc: ports at FreeBSD.org
> Message-ID: <40872D20.8030306 at buryatia.ru>
> Content-Type: text/plain; charset="utf-8"
>
> Привет!
> ЗаÑылаю тебе патчик Ð´Ð»Ñ pppd-2.3.11 - без
> него демон не Ñтартует на
> Ñ„Ñ€ÑÑ
> е 5.2.1, на 4.Ñ
> не проверÑл.
> КÑтати, когда 2.4.2 портируешь?
>
> Удачи!!!
> Z. Oleg
>
>
> -------------- next part --------------
> diff -ruN ppp-2.3.11.orig/pppd/sys-bsd.c ppp-2.3.11/pppd/sys-bsd.c
> --- pppd/sys-bsd.c Tue Aug 24 14:25:54 1999
> +++ pppd/sys-bsd.c Thu Apr 22 10:40:42 2004
> @@ -180,22 +180,22 @@
> int
> ppp_available()
> {
> - int s, ok;
> - struct ifreq ifr;
> + const char *modname = "if_ppp";
> extern char *no_ppp_msg;
>
> - if ((s = socket(AF_INET, SOCK_DGRAM, 0)) < 0)
> - return 1; /* can't tell */
> + if (modfind(modname) != -1) {
> + return 1;
> + }
>
> - strlcpy(ifr.ifr_name, "ppp0", sizeof (ifr.ifr_name));
> - ok = ioctl(s, SIOCGIFFLAGS, (caddr_t) &ifr) >= 0;
> - close(s);
> + if (getuid() == 0 && kldload(modname) != -1)
> + return 1;
>
> no_ppp_msg = "\
> This system lacks kernel support for PPP. To include PPP support\n\
> -in the kernel, please follow the steps detailed in the README.bsd\n\
> -file in the ppp-2.2 distribution.\n";
> - return ok;
> +in the kernel, please add \"device ppp\" to your kernel config or \n\
> +load the if_ppp module.\n";
> +
> + return 0;
> }
>
> /*
>
> ------------------------------
>
> Message: 9
> Date: Wed, 21 Apr 2004 22:26:59 -0400
> From: Joe Marcus Clarke <marcus at marcuscom.com>
> Subject: Re: security/gringotts won't recompile after GNOME 2.6
> upgrade
> To: Jeremy Messenger <mezz7 at cox.net>
> Cc: ports at freebsd.org
> Message-ID: <1082600819.34974.25.camel at shumai.marcuscom.com>
> Content-Type: text/plain; charset="us-ascii"
>
> On Thu, 2004-04-15 at 13:13, Jeremy Messenger wrote:
>> On Thu, 15 Apr 2004 06:50:32 -0400, Adam McLaurin
>> <adam.mclaurin at gmx.net>
>> wrote:
>>
>>> On Wed, 14 Apr 2004 23:07:40 -0400
>>> Adam McLaurin <adam.mclaurin at gmx.net> wrote:
>>>
>>>> I've had no luck getting security/gringotts to recompile since the
>>>> GNOME
>>>> 2.6 upgrade. Using portupgrade, it tried reinstalling GTK, which
>>>> already
>>>> existed, so it failed. So I tried deinstalling it and reinstalling
>>>> from
>>>> scratch, and now I get this error:
>>>
>>>> From the gringott's author:
>>> From: Germano Rizzo <mano at pluto.it>
>>> To: Adam McLaurin <adam.mclaurin at gmx.net>
>>> Subject: Re: gringotts 1.2.7 will not recompile after GNOME 2.6
>>> upgrade
>>> Date: Thu, 15 Apr 2004 10:06:11 +0200
>>> Organization: Progetto PLUTO
>>> User-Agent: Mozilla Thunderbird 0.5a (Windows/20040120)
>>>
>>> Hi,
>>> actually, the problem is that gtk+ 2.6 has removed GTK_OPTION_MENU.
>>
>> There's no GTK 2.6, which it's GTK 2.4 and it doesn't remove
>> GTK_OPTION_MENU. Check in the /usr/ports/CHANGE under the '20040404'.
>> Attaching gringotts.diff to allow it builds.
>
> Committed, thanks!
>
> Joe
>
>>
>> Cheers,
>> Mezz
>>
>>> I'll release a fixed version as soon as I can (which is, I don't know
>>> exactly when :[ but soon). 1.2.8 won't fix the problem, at the time
>>> that
>>> wasn't present.
>>> Thanks,
>>> Germano
> --
> PGP Key : http://www.marcuscom.com/pgp.asc
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 187 bytes
> Desc: This is a digitally signed message part
> Url :
> http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040421/
> 39f54592/attachment-0001.bin
>
> ------------------------------
>
> Message: 10
> Date: Thu, 22 Apr 2004 04:39:31 +0200
> From: Roman Neuhauser <neuhauser at chello.cz>
> Subject: Re: ports/40699: [patch] allow exclude patterns in `make
> search`
> To: freebsd-gnats-submit at FreeBSD.org
> Cc: freebsd-ports <freebsd-ports at freebsd.org>
> Message-ID: <20040422023931.GA40791 at isis.wad.cz>
> Content-Type: text/plain; charset="us-ascii"
>
> This patch gives me all the functionality I've been missing in the
> search
> target in Mk/bsd.port.subdir.mk. Any and all feedback is welcome.
>
> The code is completely undocumented, but putting (a shorter version of)
> this text in Mk/bsd.port.subdir.mk could mitigate that.
>
> Besides the good old key and name variables, this patch adds support
> for
> path, info, maint, cat, bdeps, and rdeps, which match on the
> appropriate
> fields, plus their exclusion counterparts: xkey, xname, etc.
>
> Examples:
>
> Find all ports whose names contain "pear-" but not "html" or "http":
>
> make search name=pear- xname='ht(tp|ml)'
>
> Find ports whose names contain "pear-" and which don't have apache
> listed in build-time dependencies:
>
> make search name=pear- xbdeps=apache
>
> The positive variables (name, key, maint, etc) are AND-ed, their
> negative versions are OR-ed; in other words, matching any x- variable
> will cause the port to be skipped, mismatch on any non-x- variable
> will cause it to be skipped.
>
> Examples:
>
> Find ports that are both in the www category and maintained by
> Thierry Thomas:
>
> make search maint=thierry@ path=/www/
>
> Find ports in the archivers category that are either not orphaned or
> don't have "zip" in their names (contrived):
>
> make search cat=archivers xmaint=ports at freebsd xname=zip
>
> It is possible to select fields to display.
>
> Example:
>
> Find PEAR ports that don't build-depend on apache, displaying only
> Port:, Path:, and Info: lines:
>
> make search name=pear- xbdeps=apache display=name,path,info
>
> Case-sensitivity can now be turned of with icase=1.
>
> Example:
>
> Find ports with @freebsd.org maintainer addresses without the "proper"
> capitalization (@FreeBSD.org), display their paths and maintainer
> addresses:
>
> make search maint=@freebsd\\.org icase=0 display=maint,path
>
> The key and xkey variables can be limited in scope to displayed fields
> by setting keylim to 1.
>
> Example:
>
> Find ports that contain "apache" in either of the name, path, info
> fields, ignore the rest of the record (dependencies, maintainer
> address, etc):
>
> make search key=apache display=name,path,info keylim=1
>
> --
> If you cc me or remove the list(s) completely I'll most likely ignore
> your message. see http://www.eyrie.org./~eagle/faqs/questions.html
> -------------- next part --------------
> Index: Mk/bsd.port.subdir.mk
> ===================================================================
> RCS file: /home/ncvs/ports/Mk/bsd.port.subdir.mk,v
> retrieving revision 1.53
> diff -u -u -r1.53 bsd.port.subdir.mk
> --- Mk/bsd.port.subdir.mk 2 Apr 2004 07:25:23 -0000 1.53
> +++ Mk/bsd.port.subdir.mk 22 Apr 2004 02:17:18 -0000
> @@ -315,19 +315,86 @@
> PKGINSTALLVER="${PKGINSTALLVER:S/"/"'"'"/g:S/\$/\$\$/g:S/\\/\\\\/g}"
> .endif
>
> -
> +PORTSEARCH_DISPLAY_FIELDS?=name,path,info,maint,index,bdeps,rdeps
>
> search: ${PORTSDIR}/${INDEXFILE}
> @here=`pwd`; \
> cd ${PORTSDIR}; \
> - top=`pwd -P`; \
> - there=`echo "$$here/" | sed s%$$top%${PORTSDIR}%`; \
> - if [ -n "$$key" ]; then \
> - grep $$there ${PORTSDIR}/${INDEXFILE} | grep -i "${key}" | awk
> -F\| '{
> printf("Port:\t%s\nPath:\t%s\nInfo:\t%s\nMaint:\t%s\nIndex:\t%s\nB-
> deps:\t%s\nR-deps:\t%s\n\n", $$1, $$2, $$4, $$6, $$7, $$8, $$9); }'; \
> - elif [ $$name ]; then \
> - grep $$there ${PORTSDIR}/${INDEXFILE} | grep -i
> "^[^|]*${name}[^|]*|" | awk -F\| '{
> printf("Port:\t%s\nPath:\t%s\nInfo:\t%s\nMaint:\t%s\nIndex:\t%s\nB-
> deps:\t%s\nR-deps:\t%s\n\n", $$1, $$2, $$4, $$6, $$7, $$8, $$9); }'; \
> - else \
> + if [ -z "$$key" -a -z "$$xkey" -a \
> + -z "$$name" -a -z "$$xname" -a \
> + -z "$$path" -a -z "$$xpath" -a \
> + -z "$$info" -a -z "$$xinfo" -a \
> + -z "$$maint" -a -z "$$xmaint" -a \
> + -z "$$bdeps" -a -z "$$xbdeps" -a \
> + -z "$$rdeps" -a -z "$$xrdeps" ]; \
> + then \
> echo "The search target requires a keyword parameter or name
> parameter,"; \
> echo "e.g.: \"make search key=somekeyword\""; \
> echo "or \"make search name=somekeyword\""; \
> - fi;
> + exit; \
> + fi; \
> + awk -F\| -v there="$$here/" -v top="$$(pwd -P)" \
> + -v icase="$${icase:-1}" -v keylim="$${keylim:-0}" \
> + -v key="$$key" -v xkey="$$xkey" \
> + -v name="$$name" -v xname="$$xname" \
> + -v path="$$path" -v xpath="$$xpath" \
> + -v info="$$info" -v xinfo="$$xinfo" \
> + -v maint="$$maint" -v xmaint="$$xmaint" \
> + -v cat="$$cat" -v xcat="$$xcat" \
> + -v bdeps="$$bdeps" -v xbdeps="$$xbdeps" \
> + -v rdeps="$$rdeps" -v xrdeps="$$xrdeps" \
> + -v display="$${display:-${PORTSEARCH_DISPLAY_FIELDS}}" \
> + 'BEGIN { \
> + sub(top, "${PORTSDIR}", there); \
> + IGNORECASE=icase; \
> + keylen = length(key); keylim = keylim && keylen; \
> + if (!keylim && keylen) \
> + parms[0] = key; \
> + xkeylen = length(xkey); xkeylim = xkeylim && xkeylen; \
> + if (!xkeylim && xkeylen) \
> + xparms[0] = xkey; \
> + if (length(name)) parms[1] = name; if (length(xname))
> xparms[1] = xname; \
> + if (length(path)) parms[2] = path; if (length(xpath))
> xparms[2] = xpath; \
> + if (length(info)) parms[4] = info; if (length(xinfo))
> xparms[4] = xinfo; \
> + if (length(maint)) parms[6] = maint; if (length(xmaint))
> xparms[6] = xmaint; \
> + if (length(cat)) parms[7] = cat; if (length(xcat))
> xparms[7] = xcat; \
> + if (length(bdeps)) parms[8] = bdeps; if (length(xbdeps))
> xparms[8] = xbdeps; \
> + if (length(rdeps)) parms[9] = rdeps; if (length(xrdeps))
> xparms[9] = xrdeps; \
> + fields["name"] = 1; names[1] = "Port"; \
> + fields["path"] = 2; names[2] = "Path"; \
> + fields["info"] = 4; names[4] = "Info"; \
> + fields["maint"] = 6; names[6] = "Maint"; \
> + fields["cat"] = 7; names[7] = "Index"; \
> + fields["bdeps"] = 8; names[8] = "B-deps"; \
> + fields["rdeps"] = 9; names[9] = "R-deps"; \
> + split(display, d, /,[ \t]*/); \
> + for (i in d) { \
> + fldname = d[i]; \
> + fldpos = fields[fldname]; \
> + disp[fldpos] = fldname; \
> + } \
> + } \
> + { \
> + if ($$2 !~ there) \
> + next; \
> + for (i in parms) \
> + if ($$i !~ parms[i]) \
> + next; \
> + for (i in xparms) \
> + if ($$i ~ xparms[i]) \
> + next; \
> + found = 0; \
> + for (i = 1; i < 10; i++) \
> + if (i in disp) { \
> + if (xkeylim && $$i ~ xkey) \
> + next; \
> + if (!found && keylim && $$i ~ key) \
> + found = 1; \
> + } \
> + if (keylim && !found) \
> + next; \
> + for (i = 1; i < 10; i++) \
> + if (i in disp) \
> + printf("%s:\t%s\n", names[i], $$i); \
> + print(""); \
> + }' ${PORTSDIR}/${INDEXFILE}
>
> ------------------------------
>
> Message: 11
> Date: Wed, 21 Apr 2004 20:22:13 -0700
> From: "Michael C. Shultz" <ringworm at inbox.lv>
> Subject: Re: setting up a ports infrastructure outside of /usr/ports
> To: freebsd-ports at freebsd.org
> Message-ID: <200404212022.14217.ringworm at inbox.lv>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Wednesday 21 April 2004 03:11 pm, Oliver Fischer wrote:
>> Hello,
>>
>> I would like to ports some programs but before I will start, I would
>> like to have a separate directory for it. So so my question is:
>>
>> Is it possible:
>>
>> 1. to have the ports directory in my home directory? I
>> think yes.
>>
>> 2. to build and to install a port as normal user to
>> a via PREFIX specified directory?
>>
>> 3. to use a different pkgdb directory than /var/db/pkg for
>> the ports build in this manner?
>>
>>
>> Regards,
>> Oliver Fischer
>> _______________________________________________
>> freebsd-ports at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
>> To unsubscribe, send any mail to
>> "freebsd-ports-unsubscribe at freebsd.org"
>
> Here is how I do it:
> ------------------------------------------------
> Here is how to handle locally installed ports if you plan to take
> advantage of
> some of FreeBSD's port system features:
>
> #######################################################################
> #
> * Makefile excerpt from /usr/ports/local/sysutils/portmanager/Makefile
> #
> #######################################################################
> #
> PORTNAME= portmanager
> PORTVERSION= 0.1.0
> CATEGORIES= local/sysutils
> VALID_CATEGORIES+= ${CATEGORIES} # for FreeBSD to accept our
> # local category
>
>
> Simply add a "local" directory to /usr/ports and install your local
> ports
> under that directory. Where a normal FreeBSD port may be in
> "sysutils/{portname} the example above would reside in
> "local/sysutils/portmanager".
> ------------------------------------------------
> The port still installs in the normal /var/db/pkg directory so "make
> install",
> and and "make deinstall" work normally. The is a note in portupgrade
> (if you
> use that ) about adding /usr/ports/local to their config files so their
> program will ignore your ports. I think the note is in the config file
> somewhere.
>
> -Mike
>
>
>
> ------------------------------
>
> Message: 12
> Date: Wed, 21 Apr 2004 23:58:07 -0700 (PDT)
> From: Joe Zeiler <zeiler07 at yahoo.com>
> Subject: FreeBSD Port: gxine-0.3.3
> To: greg at chown.ath.cx
> Cc: ports at FreeBSD.org
> Message-ID: <20040422065807.99431.qmail at web20204.mail.yahoo.com>
> Content-Type: text/plain; charset=us-ascii
>
> This port compiles fine, but does not run on 5x
> [hasn't in my experience in the entire 5 release line,
> current build 5.2.1-p4]. It hangs at
>
> Shared object "libgnomevfs.so.0" not found.
>
> when run from a command line. Symlinnking,
> libmapping, and installing the older libgnomevfs does
> not solve this.
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! Photos: High-quality 4x6 digital prints for 25¢
> http://photos.yahoo.com/ph/print_splash
>
> ------------------------------
>
> Message: 13
> Date: Thu, 22 Apr 2004 09:28:32 +0200
> From: Volker Stolz <vs at FreeBSD.org>
> Subject: Re: setting up a ports infrastructure outside of /usr/ports
> To: Oliver Fischer <plexus at snafu.de>
> Cc: ports at FreeBSD.org
> Message-ID: <20040422072832.GA47895 at i2.informatik.rwth-aachen.de>
> Content-Type: text/plain; charset=iso-8859-15
>
> In local.freebsd-ports, you wrote:
>> 1. to have the ports directory in my home directory? I
>> think yes.
>
> Yes. Only when specifying some dependencies via relative URLs
> you may need to work around this (${.CURDIR}/../net/foo).
>
>> 2. to build and to install a port as normal user to
>> a via PREFIX specified directory?
>> 3. to use a different pkgdb directory than /var/db/pkg for
>> the ports build in this manner?
>
> PACKAGES=$HOME/tmp PKG_DBDIR=$HOME/var/db/pkg PREFIX=$HOME/jail make
> install -DINSTALL_AS_USER
>
> However, many ports will fail on installing because they'd like
> to run binaries (e.g. for registering with already installed aps)
> which need root privileges. In that case, you can still install
> them to a different PREFIX and with a different PKG_DBDIR as root.
>
> I only used this for testing, though, I never tried to run stuff
> in there.
>
> Volker
> --
> http://www-i2.informatik.rwth-aachen.de/stolz/ *** PGP *** S/MIME
> Neu! Ändern Sie den Anfangstag Ihrer Woche
>
> ------------------------------
>
> Message: 14
> Date: Thu, 22 Apr 2004 08:30:54 +0100
> From: Matthew Seaman <m.seaman at infracaninophile.co.uk>
> Subject: Re: setting up a ports infrastructure outside of /usr/ports
> To: Oliver Fischer <plexus at snafu.de>
> Cc: freebsd-ports at freebsd.org
> Message-ID:
> <20040422073054.GB26669 at happy-idiot-talk.infracaninophile.co.uk>
> Content-Type: text/plain; charset="us-ascii"
>
> On Thu, Apr 22, 2004 at 12:11:22AM +0200, Oliver Fischer wrote:
>> Hello,
>>
>> I would like to ports some programs but before I will start, I would
>> like to have a separate directory for it. So so my question is:
>>
>> Is it possible:
>>
>> 1. to have the ports directory in my home directory? I
>> think yes.
>>
>> 2. to build and to install a port as normal user to
>> a via PREFIX specified directory?
>>
>> 3. to use a different pkgdb directory than /var/db/pkg for
>> the ports build in this manner?
>
> Sure. That's all possible. When I'm working on ports I just stick
> the port directory in my home dir and set up a bunch of environment
> variables so I don't trample over the official /var/db/pkg (or try to
> -- I work on the development stuff under my own UID, not root).
>
> I generally just source this into my tcsh session:
>
> # -*- csh -*-
> #
> # Set up environment for testing ports
>
> setenv WRKDIRPREFIX ${HOME}/tmp/ports
> setenv PKG_DBDIR ${HOME}/tmp/db/pkgs
> setenv PORT_DBDIR ${HOME}/tmp/db/ports
> setenv PREFIX ${HOME}/tmp/local
> setenv INSTALL_AS_USER yes
> setenv NOCLEANDEPENDS yes
>
> unsetenv JAVA_HOME
>
> Not that this still expects bsd.port.mk and all of the makefiles to
> live in /usr/ports/Mk -- as well as any dependency ports.
>
> Cheers,
>
> Matthew
>
> --
> Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
> Savill Way
> PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
> Tel: +44 1628 476614 Bucks., SL7 1TH
> UK
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 187 bytes
> Desc: not available
> Url :
> http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040422/
> 16a10fad/attachment-0001.bin
>
> ------------------------------
>
> Message: 15
> Date: Thu, 22 Apr 2004 08:36:11 +0100
> From: Matthew Seaman <m.seaman at infracaninophile.co.uk>
> Subject: Re: setting up a ports infrastructure outside of /usr/ports
> To: Oliver Fischer <plexus at snafu.de>, freebsd-ports at freebsd.org
> Message-ID:
> <20040422073611.GC26669 at happy-idiot-talk.infracaninophile.co.uk>
> Content-Type: text/plain; charset="us-ascii"
>
> On Thu, Apr 22, 2004 at 08:30:54AM +0100, Matthew Seaman wrote:
>> Not that this still expects bsd.port.mk and all of the makefiles to
>> live in /usr/ports/Mk -- as well as any dependency ports.
>
> Err.. let me repeat that in Englist rather than gibberish.
>
> Note that this expects bsd.port.mk and all of the oter makefiles to
> live in /usr/ports/Mk. Dependency ports will be searched for in the
> usual places under /usr/ports.
>
> Cheers,
>
> Matthew
>
> --
> Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
> Savill Way
> PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
> Tel: +44 1628 476614 Bucks., SL7 1TH
> UK
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 187 bytes
> Desc: not available
> Url :
> http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040422/
> 10318b9c/attachment-0001.bin
>
> ------------------------------
>
> Message: 16
> Date: Thu, 22 Apr 2004 00:47:42 -0700
> From: Ryan Merrick <sandshrimp at comcast.net>
> Subject: Re: FreeBSD Port: XFree86-libraries-4.3.0_7
> To: Michael Nottebrock <michaelnottebrock at gmx.net>
> Cc: ports at freebsd.org
> Message-ID: <4087789E.40006 at comcast.net>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Michael Nottebrock wrote:
>> On Wednesday 21 April 2004 10:22, Ryan Merrick wrote:
>>
>>> Hi,
>>>
>>> I am trying out the 4.10 beta and cant build XFree86-libraries. I
>>> only
>>> have #/usr/lib/libc.so.4 . Packages are not available for
>>> XFree86-libraries-4.3.0_7 yet, but all the ports list it as a
>>> dependency
>>
>>
>>> [...]
>>
>>
>>> ./config/imake/imake -I./config/cf -s xmakefile -DTOPDIR=.
>>> -DCURDIR=.
>>> rm -f ./config/imake/Makefile.proto
>>> making Makefiles in include/bitmaps...
>>> /usr/libexec/ld-elf.so.1: Shared object "libc.so.5" not found
>>> *** Error code 1
>>
>>
>> That's pretty odd. Did you install an imake package from
>> FreeBSD-CURRENT or
>> 5.x-Release? This can't work. pkg_delete -f imake\*, make clean in
>> x11/XFree86-4-libraries and then try again.
>>
>
> Hi,
>
> These were the packages and ports I had installed when the I could not
> build XFree86-libraries. I removed all packages and started over.
>
> :>pkg_info
> XFree86-libraries-4.3.0_6 XFree86-4 libraries and headers
> cvsup-without-gui-16.1h General network file distribution system
> optimized for CVS
> enlightenment-0.16.6_1 A very artistic X window manager
> esound-0.2.34 A sound library for enlightenment package
> expat-1.95.7 XML 1.0 parser written in C
> ezm3-1.1_1 Easier, more portable Modula-3 distribution for
> building CV
> fontconfig-2.2.2,1 An XML-based font configuration API for X Windows
> freetype-1.3.1_3 A free and portable TrueType font rendering engine
> freetype2-2.1.7_2 A free and portable TrueType font rendering engine
> gettext-0.13.1_1 GNU gettext package
> gkrellm-2.1.28_2 A GTK based system monitor
> glib-1.2.10_10 Some useful routines of C programming (previous
> stable vers
> gmake-3.80_2 GNU version of 'make' utility
> imake-4.3.0_2 Imake and other utilities from XFree86
> jpeg-6b_2 IJG's jpeg compression utilities
> libaudiofile-0.2.6 A sound library for SGI audio file
> libghttp-1.0.9 GNOME http client library
> libgnugetopt-1.2 GNU getopt library
> libiconv-1.9.1_3 A character set conversion library
> libtool-1.3.5_2 Generic shared library support script (version 1.3)
> perl-5.6.1_15 Practical Extraction and Report Language
> pkgconfig-0.15.0_1 A utility used to retrieve information about
> installed libr
> png-1.2.5_3 Library for manipulating PNG images
> portupgrade-20040325_1 FreeBSD ports/packages administration and
> management tool s
> rc_subr-1.16 Common startup and shutdown subroutines used by
> scripts
> ruby-1.8.1_2 An object-oriented interpreted scripting language
> ruby18-bdb1-0.2.2 Ruby interface to Berkeley DB revision 1.8x with
> full featu
> screen-4.0.2 A multi-screen window manager
> tiff-3.6.1_1 Tools and library routines for working with TIFF
> images
>
> The port installed correctly. I can only guess that the problem
> happened
> somewhere in the portinstall -P of enlightenment or the build of
> gkrellmd.
>
> Thank you,
>
> --
> -Ryan Merrick
> sandshrimp at comcast.net
>
>
>
> ------------------------------
>
> Message: 17
> Date: Thu, 22 Apr 2004 02:49:53 -0500
> From: Jeremy Messenger <mezz7 at cox.net>
> Subject: Re: FreeBSD Port: gxine-0.3.3
> To: Joe Zeiler <zeiler07 at yahoo.com>
> Cc: ports at FreeBSD.org
> Message-ID: <opr6uldfug8ckrg5 at smtp.central.cox.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
> The code is hardcore, so here's an attach of gxine.diff to fix it. I am
> able to run gxine on few videos in local machine and right off the
> Mozilla
> over at apple.com/trailers/ with no problem. I didn't do the hard
> check or
> test, just a quick glare and fix.
>
> Cheers,
> Mezz
>
> On Wed, 21 Apr 2004 23:58:07 -0700 (PDT), Joe Zeiler
> <zeiler07 at yahoo.com>
> wrote:
>
>> This port compiles fine, but does not run on 5x
>> [hasn't in my experience in the entire 5 release line,
>> current build 5.2.1-p4]. It hangs at
>>
>> Shared object "libgnomevfs.so.0" not found.
>>
>> when run from a command line. Symlinnking,
>> libmapping, and installing the older libgnomevfs does
>> not solve this.
>
>
> --
> bsdforums.org 's moderator, mezz.
> -------------- next part --------------
> diff -ur gxine.orig/Makefile gxine/Makefile
> --- gxine.orig/Makefile Sun Apr 4 22:30:00 2004
> +++ gxine/Makefile Thu Apr 22 02:46:24 2004
> @@ -7,7 +7,7 @@
>
> PORTNAME= gxine
> PORTVERSION= 0.3.3
> -PORTREVISION= 7
> +PORTREVISION= 8
> CATEGORIES= multimedia
> MASTER_SITES= ${MASTER_SITE_SOURCEFORGE}
> MASTER_SITE_SUBDIR= xine
> @@ -19,12 +19,16 @@
>
> USE_X_PREFIX= yes
> GNU_CONFIGURE= yes
> -USE_GNOME= gtk20
> +USE_GNOME= gtk20 lthack
> CONFIGURE_ENV= CPPFLAGS="-I${LOCALBASE}/include -I${X11BASE}/include"
> \
> LDFLAGS="-L${LOCALBASE}/lib -I${X11BASE}/lib"
>
> MANLANG= "" de
> MAN1= gxine.1
> +
> +post-patch:
> + @${REINPLACE_CMD} -e
> 's|libgnomevfs.so.0|${X11BASE}/lib/libgnomevfs-2.so|g' \
> + ${WRKSRC}/src/desktop_integration.c
>
> post-install:
> @${MKDIR} ${PREFIX}/lib/browser_plugins
>
> ------------------------------
>
> Message: 18
> Date: Thu, 22 Apr 2004 11:27:17 +0200
> From: Jean-Baptiste Quenot <jb.quenot at caraldi.com>
> Subject: mutt change breaks vim syntax highlighting
> To: Udo Schweigert <udo.schweigert at siemens.com>
> Cc: freebsd-ports <ports at freebsd.org>
> Message-ID: <20040422092714.GF40900 at anyware12.anyware>
> Content-Type: text/plain; charset="us-ascii"
>
> Dear Udo,
>
> Could you please review PR 63192? Since you introduced a patch to
> the
> creation of temp files in Mutt with PR 62569, there is now a
> problem
> with Vim syntax highlighting.
>
> Maintainer of Vim (David O'Brien) does not understand why this patch
> is
> FreeBSD-specific and has not been submitted to Mutt's upstreams
> author.
> Would you be kind to post a follow-up to this PR and to this
> list,
> explaining your motivation to do so?
>
> Thanks in advance,
> --
> Jean-Baptiste Quenot
> http://caraldi.com/jbq/
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 187 bytes
> Desc: not available
> Url :
> http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040422/
> 93bec1b6/attachment-0001.bin
>
> ------------------------------
>
> Message: 19
> Date: Thu, 22 Apr 2004 12:46:41 +0200
> From: Joerg Wunsch <j at ida.interface-business.de>
> Subject: ports build && make -j<something>
> To: ports at freebsd.org
> Message-ID: <20040422124641.B75449 at ida.interface-business.de>
> Content-Type: text/plain; charset=us-ascii
>
> What's the current stance on make -j4 builds in the ports tree?
>
> I've got that 4-CPU old sparc64 machine here, and running compiles in
> parallel seems to be good there since it distributes the load across
> the CPUs. While I understand that some of the ports simply cannot be
> built at all with a parallel make, many of them actually do compile
> fine, but I consistently get that kind of error whenever any dependant
> port is going to be compiled:
>
> ...
> ===> Applying FreeBSD patches for netpbm-10.21_1
> ===> netpbm-10.21_1 depends on executable: gmake - found
> ===> netpbm-10.21_1 depends on file: /usr/local/bin/perl5.6.1 - found
> ===> netpbm-10.21_1 depends on shared library: tiff.4 - not found
> ===> Verifying install for tiff.4 in /usr/ports/graphics/tiff
> cd: can't cd to /usr/ports/graphics/tiff/work/tiff-v3.6.1
> *** Error code 2
> 1 error
> *** Error code 2
> 1 error
>
> Apparently, one of the parallel builds already tries to change into
> the ${WRKDIR} while the other `thread' just only started to unpack the
> tree.
>
> Manually cd'ing to /usr/ports/graphics/tiff and starting make -j4
> works quite fine though.
>
> Would it be possible to fix that consistent failure?
> --
> J"org Wunsch Unix support engineer
> joerg_wunsch at interface-systems.de
> http://www.interface-systems.de/~j/
>
> ------------------------------
>
> Message: 20
> Date: Wed, 21 Apr 2004 23:08:55 +0200
> From: "Tomas Levin" <tomas at cacanny.no>
> Subject: FreeBSD Port: ispell-3.2.06
> To: <jmz at FreeBSD.org>
> Cc: ports at FreeBSD.org
> Message-ID: <200404212107.i3LL7kY7033756 at cacanny.no>
> Content-Type: text/plain; charset="iso-8859-1"
>
> HI
>
>
>
> Sorry to bother you. I’m an new comer to Freebsd and wanted to install
> Ispell with Norwegian dictionaries. My portstree is up-to-date as of
> today.
>
>
>
> When I run:
>
>
>
> make ISPELL_NO=yes install
>
>
>
> I get the following error:
>
>
>
> 199000 200000 201000 202000 203000 204000 205000 206000 207000
>
> /usr/ports/textproc/ispell/work//bin/unsq.pl < norsk.words.sq >
> norsk.words
>
> /usr/ports/textproc/ispell/work//bin/unsq.pl: not found
>
> gmake: *** [norsk.words] Error 127
>
> *** Error code 2
>
>
>
> Stop in /usr/ports/textproc/ispell.
>
>
>
> Do you have any clue to what I’m doing wrong or is there something
> strange
> with the port ?
>
>
>
> I would also like to take the time to express my deep gratitude to you
> for
> making this port available.
>
>
>
> Regards
>
>
>
> Tomas
>
>
>
> ***********************************************************************
> *****
> ***
>
> "Det er menneskelig å feile, men for virkelig å lage rot trengs en
> datamaskin." -- Ukjent Nørd
>
>
>
>
> ------------------------------
>
> Message: 21
> Date: Thu, 22 Apr 2004 04:54:40 -0700
> From: Kris Kennaway <kris at obsecurity.org>
> Subject: Re: FreeBSD Port: ispell-3.2.06
> To: Tomas Levin <tomas at cacanny.no>
> Cc: ports at FreeBSD.org
> Message-ID: <20040422115440.GA97639 at xor.obsecurity.org>
> Content-Type: text/plain; charset="us-ascii"
>
> On Wed, Apr 21, 2004 at 11:08:55PM +0200, Tomas Levin wrote:
>> HI
>>
>>
>>
>> Sorry to bother you. I?m an new comer to Freebsd and wanted to install
>> Ispell with Norwegian dictionaries. My portstree is up-to-date as of
>> today.
>>
>>
>>
>> When I run:
>>
>>
>>
>> make ISPELL_NO=yes install
>>
>>
>>
>> I get the following error:
>>
>>
>>
>> 199000 200000 201000 202000 203000 204000 205000 206000 207000
>>
>> /usr/ports/textproc/ispell/work//bin/unsq.pl < norsk.words.sq >
>> norsk.words
>>
>> /usr/ports/textproc/ispell/work//bin/unsq.pl: not found
>>
>> gmake: *** [norsk.words] Error 127
>>
>> *** Error code 2
>>
>>
>>
>> Stop in /usr/ports/textproc/ispell.
>>
>>
>>
>> Do you have any clue to what I?m doing wrong or is there something
>> strange
>> with the port ?
>
> Are you running 5.x but don't have perl installed? Perhaps the port
> is missing a dependency.
>
> Kris
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 187 bytes
> Desc: not available
> Url :
> http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040422/
> ada879db/attachment-0001.bin
>
> ------------------------------
>
> Message: 22
> Date: Thu, 22 Apr 2004 05:15:16 -0700 (PDT)
> From: Jean-Marc Zucconi <jmz at FreeBSD.org>
> Subject: Re: FreeBSD Port: ispell-3.2.06
> To: Kris Kennaway <kris at obsecurity.org>
> Cc: ports at FreeBSD.org
> Message-ID: <200404221215.i3MCFGPk044579 at freefall.freebsd.org>
>
>>>>>> Kris Kennaway writes:
>
>> On Wed, Apr 21, 2004 at 11:08:55PM +0200, Tomas Levin wrote:
>>> HI
>>>
>>>
>>>
>>> Sorry to bother you. I?m an new comer to Freebsd and wanted to
>>> install
>>> Ispell with Norwegian dictionaries. My portstree is up-to-date as of
>>> today.
>>>
>>>
>>>
>>> When I run:
>>>
>>>
>>>
>>> make ISPELL_NO=yes install
>>>
>>>
>>>
>>> I get the following error:
>>>
>>>
>>>
>>> 199000 200000 201000 202000 203000 204000 205000 206000 207000
>>>
>>> /usr/ports/textproc/ispell/work//bin/unsq.pl < norsk.words.sq >
>>> norsk.words
>>>
>>> /usr/ports/textproc/ispell/work//bin/unsq.pl: not found
>>>
>>> gmake: *** [norsk.words] Error 127
>>>
>>> *** Error code 2
>>>
>>>
>>>
>>> Stop in /usr/ports/textproc/ispell.
>>>
>>>
>>>
>>> Do you have any clue to what I?m doing wrong or is there something
>>> strange
>>> with the port ?
>
>> Are you running 5.x but don't have perl installed? Perhaps the port
>> is missing a dependency.
>
> No the problem is elsewhere: unsq disappeared from the newest ispell
> versions and broke ISPELL_NO=yes. Novegian users report it from time
> to time. I always ask the user to test a workaround but up to now I
> got zero feedback :-(
> I can't test it myself as I don't speak norsk.
>
> Jean-Marc
>
> --
> Jean-Marc Zucconi -- PGP Key: finger jmz at FreeBSD.org [KeyID: 400B38E9]
>
> ------------------------------
>
> Message: 23
> Date: Thu, 22 Apr 2004 15:17:14 +0200
> From: Udo Schweigert <Udo.Schweigert at siemens.com>
> Subject: Re: mutt change breaks vim syntax highlighting
> To: Jean-Baptiste Quenot <jb.quenot at caraldi.com>, freebsd-ports
> <ports at freebsd.org>
> Message-ID: <20040422131714.GA85938 at alaska.cert.siemens.de>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Apr 22, 2004 at 11:27:17 +0200, Jean-Baptiste Quenot wrote:
>> Dear Udo,
>>
>> Could you please review PR 63192? Since you introduced a patch to
>> the
>> creation of temp files in Mutt with PR 62569, there is now a
>> problem
>> with Vim syntax highlighting.
>>
>> Maintainer of Vim (David O'Brien) does not understand why this patch
>> is
>> FreeBSD-specific and has not been submitted to Mutt's upstreams
>> author.
>> Would you be kind to post a follow-up to this PR and to this
>> list,
>> explaining your motivation to do so?
>>
>
> Adding the patch was done by another user's request, because the
> current mutt
> code causes problems on open-session machines, when PIDs are reused
> and thus
> mutt sometimes failes to open a tmp-file because it's already opened by
> another user. Another benefit is that the usage of mktemp() gives (a
> little)
> more security here.
>
> I also submitted that to the mutt developers mailing list, but it
> seems it
> hasn't been incorporated into the sources yet - and I doubt it will be
> done
> soon, because the whole handling of tmp-files in mutt should be
> rewritten ...
>
> A possible workaround would be to change the FreeBSD-patch so that the
> used
> tmp-filenames are compatible with vim. That will again lower them
> security
> as one would have to do something like that:
>
> --- muttlib.c.orig Thu Apr 22 14:43:58 2004
> +++ muttlib.c Thu Apr 22 14:51:01 2004
> @@ -657,7 +657,11 @@
>
> void _mutt_mktemp (char *s, const char *src, int line)
> {
> - snprintf (s, _POSIX_PATH_MAX, "%s/mutt-%s-%d-%d", NONULL (Tempdir),
> NONULL(Hostname), (int) getpid (), Counter++);
> + char t[5];
> + snprintf (t, 5, "-%03d", Counter++);
> + snprintf (s, _POSIX_PATH_MAX-5, "%s/mutt-%s-XXXXXXXX",
> NONULL(Tempdir), NONULL(Hostname));
> + mktemp (s);
> + strncat(s, t, _POSIX_PATH_MAX);
> dprint (1, (debugfile, "%s:%d: mutt_mktemp returns \"%s\".\n", src,
> line, s));
> unlink (s);
> }
>
> (Unfortunately there's no mktemps(), and mkstemps() isn't usable here)
>
> It's a bit ugly but it works ;-)
>
>
> Best regards
>
> --
> Udo Schweigert, Siemens AG | Voice : +49 89 636 42170
> CT IC CERT, Siemens CERT | Fax : +49 89 636 41166
> D-81730 Muenchen / Germany | email : udo.schweigert at siemens.com
>
> ------------------------------
>
> Message: 24
> Date: Thu, 22 Apr 2004 08:20:52 -0400
> From: Dmitriy Shnayder <dis5149 at cs.rit.edu>
> Subject: FreeBSD Port: pgbash-7.3_1
> To: sascha at root-login.org
> Cc: ports at freebsd.org
> Message-ID: <4087B8A4.9080302 at cs.rit.edu>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I have two feature requests for pgbash. First, when I issue the
> "connect to"
> command within pgbash, the application displays the cleartext of the
> password. I
> would like it to display nothing at all instead. Second, I would like
> the
> application to have a "disconnect" command. This would sever the
> connection to
> the PostgreSQL server, but would stay within the shell. That way, I
> could then
> connect to a different PostgreSQL server without having to exit and
> re-enter the
> application.
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (FreeBSD)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFAh7ikvepOHXmSZpsRAnPvAJwPEiRhpIdQFtJfJmAQg83mz58z+ACfdrYS
> ADsIcGcZKcXA8RvtC7ksQ5M=
> =VQV4
> -----END PGP SIGNATURE-----
>
> ------------------------------
>
> Message: 25
> Date: Thu, 22 Apr 2004 15:25:36 +0200
> From: Jean-Baptiste Quenot <jb.quenot at caraldi.com>
> Subject: Re: mutt change breaks vim syntax highlighting
> To: freebsd-ports <ports at freebsd.org>
> Cc: obrien at FreeBSD.org
> Message-ID: <20040422132532.GD50477 at anyware12.anyware>
> Content-Type: text/plain; charset=us-ascii
>
> * Udo Schweigert:
>
>> Adding the patch was done by another user's request, because the
>> current mutt code causes problems on open-session machines, when PIDs
>> are reused and thus mutt sometimes failes to open a tmp-file because
>> it's already opened by another user. Another benefit is that the usage
>> of mktemp() gives (a little) more security here.
>>
>> I also submitted that to the mutt developers mailing list, but it
>> seems it hasn't been incorporated into the sources yet - and I doubt
>> it will be done soon, because the whole handling of tmp-files in mutt
>> should be rewritten ...
>
> It gives us some light as of why this change occured. Hopefully
> David
> O'Brien will be able to approve the patch against vim to allow the
> new,
> more secure mutt temp files naming scheme.
>
> Thanks for your help,
> --
> Jean-Baptiste Quenot
> http://caraldi.com/jbq/
>
> ------------------------------
>
> Message: 26
> Date: Thu, 22 Apr 2004 15:34:06 +0200
> From: dirk.meyer at dinoex.sub.org (Dirk Meyer)
> Subject: Re: setting up a ports infrastructure outside of /usr/ports
> To: freebsd-ports at freebsd.org
> Message-ID: <N+b8bJGH8y at dmeyer.dinoex.sub.org>
>
> Oliver Fischer schrieb:,
>
>> I would like to ports some programs but before I will start, I would
>> like to have a separate directory for it. So so my question is:
>> Is it possible:
>>
>> 1. to have the ports directory in my home directory? I
>> think yes.
>
> set PORTSDIR
>
>> 2. to build and to install a port as normal user to
>> a via PREFIX specified directory?
>
> set:
> LOCALBASE ( where you installed stuff lives )
> LD_LIBRARY_PATH ( so you can link with local libraries )
> PATH ( to include ${LOCALBASE}/bin and ${LOCALBASE}/sbin )
> INSTALL_AS_USER=yes (if you install as root)
> BINOWN (if you are not root, you can't set owner to root)
> BINGRP
> LDCONFIG=true (ldconfig will not pick up user paths)
>
>> 3. to use a different pkgdb directory than /var/db/pkg for
>> the ports build in this manner?
>
> just set PKG_DBDIR
>
>
> my solution:
> I use in my .profile on bento:
>
> export UNAMEM=`uname -m`
> export LOCALBASE=/home/dinoex/local-${UNAMEM}
> export PKG_DBDIR=/home/dinoex/local-${UNAMEM}/var.db.pk
> export
> PATH=/home/dinoex/batch:/home/dinoex/local-${UNAMEM}/bin:/home/dinoex/
> local-${UNAMEM}/sbin:${PATH}
> export LD_LIBRARY_PATH=/home/dinoex/local-${UNAMEM}/lib
> export PACKAGES=/home/dinoex/local-${UNAMEM}/packages
> export PORTSDIR=/home/dinoex/ports
> export WRKDIRPREFIX=/home/dinoex/work
> export INSTALL_AS_USER=yes
> export BINOWN=dinoex
> export BINGRP=dinoex
> export LDCONFIG=true
>
>
> Unsolved Problems:
> LIP_DEPENDS don't work, as the local libs are not picked up by
> LDCONFIG.
>
> You have to patch your local copy of bsd.port.mk
> or remove any LIB_DEPENDS in the port Makefile.
>
> kind regards Dirk
>
> - Dirk Meyer, Im Grund 4, 34317 Habichtswald, Germany
> - [dirk.meyer at dinoex.sub.org],[dirk.meyer at guug.de],[dinoex at FreeBSD.org]
>
> ------------------------------
>
> Message: 27
> Date: Thu, 22 Apr 2004 15:36:13 +0200
> From: Michael Nottebrock <michaelnottebrock at gmx.net>
> Subject: Re: FreeBSD Port: pgbash-7.3_1
> To: freebsd-ports at freebsd.org
> Cc: Dmitriy Shnayder <dis5149 at cs.rit.edu>
> Message-ID: <200404221536.16551.michaelnottebrock at gmx.net>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Thursday 22 April 2004 14:20, Dmitriy Shnayder wrote:
>> I have two feature requests for pgbash.
>
> You got the wrong guys here, port maintainers != software developers.
> http://www.psn.co.jp/PostgreSQL/pgbash/index-e.html is the homepage of
> the
> software.
>
> --
> ,_, | Michael Nottebrock | lofi at freebsd.org
> (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
> \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 187 bytes
> Desc: signature
> Url :
> http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20040422/
> 19c3dbf9/attachment-0001.bin
>
> ------------------------------
>
> Message: 28
> Date: Thu, 22 Apr 2004 15:38:51 +0200
> From: Udo Schweigert <Udo.Schweigert at siemens.com>
> Subject: Re: ports/63192: mutt change breaks vim syntax highlighting
> To: Dan Foster <dsf at globalcrossing.net>
> Cc: ports at FreeBSD.org
> Message-ID: <20040422133850.GA69477 at alaska.cert.siemens.de>
> Content-Type: text/plain; charset=us-ascii
>
> On Fri, Mar 26, 2004 at 04:27:41 +0000, Dan Foster wrote:
>> I'd like to revisit this because I've come across some more
>> information
>> that paints things in a different light.
>>
>> Specifically, what changed mutt's behavior for the temp file name is
>> patch 'patch-mktemp' supplied by the FreeBSD ports maintainer for
>> mutt.
>>
>> I just checked the mutt 1.4 and 1.5 source trees (multiple versions),
>> and in the unmodified mutt sources, mutt-<version/muttlib.c has this
>> function:
>>
>> void mutt_mktemp (char *s)
>> {
>> snprintf (s, _POSIX_PATH_MAX, "%s/mutt-%s-%d-%d", NONULL (Tempdir),
>> NONULL(Hostname), (int) getpid (), Counter++);
>> unlink (s);
> }}
>>
>> The FreeBSD patch -- which doesn't seem to have come from the mutt
>> developers -- has this modification:
>>
>> --- muttlib.c.orig Mon Feb 9 08:25:28 2004
>> +++ muttlib.c Mon Feb 9 08:32:46 2004
>> @@ -656,7 +656,8 @@
>>
>> void mutt_mktemp (char *s)
>> {
>> - snprintf (s, _POSIX_PATH_MAX, "%s/mutt-%s-%d-%d", NONULL (Tempdir),
>> NONULL(Hostname), (int) getpid (), Counter++);
>> + snprintf (s, _POSIX_PATH_MAX, "%s/mutt-%s-XXXXXXXX",
>> NONULL(Tempdir),
>> NONULL(Hostname));
>> + mktemp (s);
>> unlink (s);
> }}
>>
>> My point is that if mutt's behavior changed due to a FreeBSD-specific
>> decision, rather than a change made by the mutt developers, then a
>> FreeBSD-specific patch (for the syntax highlighting autocommand)
>> should
>> also be committed to vim to keep mutt and vim in sync.
>>
>> A reasonable person couldn't expect the vim team to accept a patch for
>> supporting a change in runtime.vim due to a change in mutt that was
>> not
>> committed by the mutt developers and is specific only to FreeBSD.
>>
>> This appears to be why vim developers will not commit the patch, and
>> they seem to be on solid ground with that position given the
>> reasoning.
>>
>> So I would, therefore, like to politely request reconsideration of the
>> proposed vim patch for inclusion to the FreeBSD vim port or to have
>> the
>> mutt patch-mktemp patch backed out.
>>
>> Either change would be sufficient to keep the two in sync and remain
>> consistent with policy regarding local changes.
>
> As also written in another mail today (this is for gnats):
>
> Adding the patch was done by another user's request, because the
> current mutt
> code causes problems on open-session machines, when PIDs are reused
> and thus
> mutt sometimes failes to open a tmp-file because it's already opened by
> another user. Another benefit is that the usage of mktemp() gives (a
> little)
> more security here.
>
> I also submitted that to the mutt developers mailing list, but it
> seems it
> hasn't been incorporated into the sources yet - and I doubt it will be
> done
> soon, because the whole handling of tmp-files in mutt should be
> rewritten ...
>
> A possible workaround would be to change the FreeBSD-patch so that the
> used
> tmp-filenames are compatible with vim. That will again lower them
> security
> as one would have to do something like that:
>
> --- muttlib.c.orig Thu Apr 22 14:43:58 2004
> +++ muttlib.c Thu Apr 22 14:51:01 2004
> @@ -657,7 +657,11 @@
>
> void _mutt_mktemp (char *s, const char *src, int line)
> {
> - snprintf (s, _POSIX_PATH_MAX, "%s/mutt-%s-%d-%d", NONULL (Tempdir),
> NONULL(Hostname), (int) getpid (), Counter++);
> + char t[5];
> + snprintf (t, 5, "-%03d", Counter++);
> + snprintf (s, _POSIX_PATH_MAX-5, "%s/mutt-%s-XXXXXXXX",
> NONULL(Tempdir), NONULL(Hostname));
> + mktemp (s);
> + strncat(s, t, _POSIX_PATH_MAX);
> dprint (1, (debugfile, "%s:%d: mutt_mktemp returns \"%s\".\n", src,
> line, s));
> unlink (s);
> }
>
> (Unfortunately there's no mktemps(), and mkstemps() isn't usable here)
>
> It's a bit ugly but it works ;-)
>
>
> So for me it's up to David O'Brien to decide on either to add a
> FreeBSD-specific patch to the vim port(s) or to let me change the
> patch as
> shown above. I won't have a problem with either decission.
>
>
> Best regards
>
> --
> Udo Schweigert, Siemens AG | Voice : +49 89 636 42170
> CT IC CERT, Siemens CERT | Fax : +49 89 636 41166
> D-81730 Muenchen / Germany | email : udo.schweigert at siemens.com
>
> ------------------------------
>
> Message: 29
> Date: Thu, 22 Apr 2004 15:17:56 +0100
> From: Jim Hatfield <subscriber at insignia.com>
> Subject: Re: Bugfix to dvd+rw-tools...
> To: freebsd-ports at freebsd.org
> Message-ID: <pgif80tq39fmruk5670khvghnqrqerbfmd at 4ax.com>
> Content-Type: text/plain; charset=us-ascii
>
> On Wed, 21 Apr 2004 22:30:52 +0100, in local.freebsd.ports you wrote:
>
>> A problem has been reported with the latest version of dvd+rw-tools:
>
> This really got me good! It coincided with me switching from
> branded Verbatim DVD-Rs to low-rent ones, so of course I forgot
> about the upgrade and was convinced it was the disks. So when I
> switched back to the Verbatim in disgust and it kept happening,
> I was utterly baffled :-(
>
> jim
>
> ------------------------------
>
> Message: 30
> Date: Thu, 22 Apr 2004 16:31:27 +0200 (CEST)
> From: Gerald Pfeifer <gerald at pfeifer.com>
> Subject: Re: ports/63427: [lang/gcc33] Disabling the Java frontend at
> compile time
> To: Etienne Robillard <erob at videotron.ca>
> Cc: kris at obsecurity.org
> Message-ID:
> <Pine.BSF.4.58.0404221626500.23591 at acrux.dbai.tuwien.ac.at>
> Content-Type: TEXT/PLAIN; charset=US-ASCII
>
> On Sun, 11 Apr 2004, Etienne Robillard wrote:
>> Done :) see below.
>
> I had a look at this patch, and as far as I understand it, building
> Java
> should be the default (not disabling it).
>
>
>> Ain't that GUI Options screen cool ? :-)
>
> :-)
>
>> -bin/%%GNU_HOST%%-gcj33
>> +%%LIBJAVA%%bin/%%GNU_HOST%%-gcj33
>
> This doesn't seem right: one might want to just disable building
> libgcj,
> and still build the Java frontend. In fact, does it really much sense
> to
> disable building the frontend, now that we have support for disabling
> libgcj?
>
> The frontend is comparatively light, adding such an option will add
> complexity to the port and an hardly tested path (combinatorial
> explosion).
>
>> There's still some minimal glitches about info files, namely gcj and
>> fastjar. I'm sure this is not a problem. One more thing, I didn't had
>> time to test _with_ (default settings) the JAVA knob. So maybe this is
>> still early, since Gerald wanted to clear out bugs before adding
>> stuff.
>
> Yes. :-) And I think the point you are making is a very good one: will
> this really be tested on a regular base, if we add such an option?
>
> Gerald
> --
> Gerald Pfeifer (Jerry) gerald at pfeifer.com
> http://www.pfeifer.com/gerald/
>
> ------------------------------
>
> Message: 31
> Date: Thu, 22 Apr 2004 11:56:30 -0400
> From: Chuck Swiger <cswiger at mac.com>
> Subject: Re: Bugfix to dvd+rw-tools...
> To: Jim Hatfield <subscriber at insignia.com>
> Cc: freebsd-ports at freebsd.org
> Message-ID: <4087EB2E.5040909 at mac.com>
> Content-Type: text/plain; charset=us-ascii; format=flowed
>
> Jim Hatfield wrote:
> [ ... ]
>> This really got me good! It coincided with me switching from
>> branded Verbatim DVD-Rs to low-rent ones, so of course I forgot
>> about the upgrade and was convinced it was the disks. So when I
>> switched back to the Verbatim in disgust and it kept happening,
>> I was utterly baffled :-(
>
> "We apologize for the inconvenience."
>
> I've received feedback (thanks!) that the bugfix does solve the
> problem, but
> that the tool Andy wrote doesn't seem to finalize DVD-Rs that weren't
> burnt
> properly.
>
> --
> -Chuck
>
> ------------------------------
>
> Message: 32
> Date: Thu, 22 Apr 2004 18:11:45 +0200
> From: Sascha Holzleiter <sascha at root-login.org>
> Subject: Re: FreeBSD Port: pgbash-7.3_1
> To: Dmitriy Shnayder <dis5149 at cs.rit.edu>
> Cc: ports at freebsd.org
> Message-ID: <20040422161145.GA16558 at daemonground.de>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Apr 22, 2004 at 08:20:52AM -0400, Dmitriy Shnayder wrote:
>> I have two feature requests for pgbash.
>
> Hi,
>
> as Michael already noted, please bring this up to the developer of the
> software. He has been quite responsive in the past so this shouldn't be
> a problem but i think the development on pgbash has ceased over the
> last
> year.
>
>
> --
> Sascha
>
> ------------------------------
>
> Message: 33
> Date: Thu, 22 Apr 2004 01:51:11 +0900
> From: Yoichi NAKAYAMA <yoichi at geiin.org>
> Subject: Re: [ports-i386 at bento.FreeBSD.org:
> pure-xemacs-devel-mule-0.6_1 failed on i386 4]
> To: Kris Kennaway <kris at obsecurity.org>
> Cc: ports at FreeBSD.org
> Message-ID: <873c6x8ebk.wl%yoichi at geiin.org>
> Content-Type: text/plain; charset=US-ASCII
>
> At Mon, 19 Apr 2004 05:56:56 -0700,
> Kris Kennaway wrote:
>>
>> Can you please investigate and/or report to the developers?
>>
>> ====================<phase 2: make package>=====================
>> ===> Vulnerability check disabled
>> ===> Extracting for pure-xemacs-devel-mule-0.6_1
>>>> Checksum OK for pure-0.6p.tar.gz.
>>>> Checksum OK for pure-0.6pl2.diff.gz.
>> ===> Patching for pure-xemacs-devel-mule-0.6_1
>> ===> Applying distribution patches for pure-xemacs-devel-mule-0.6_1
>> ===> pure-xemacs-devel-mule-0.6_1 depends on file:
>> /usr/local/bin/xemacs-21.5-b16 - found
>> ===> Configuring for pure-xemacs-devel-mule-0.6_1
>> ===> Building for pure-xemacs-devel-mule-0.6_1
>> /usr/local/bin/xemacs-21.5-b16 -batch -q -nw -no-site-file -l
>> ./pure-make.el -l ./make.el -f make-pure-compile
>>
>> XEmacs: fatal error: Incompatible window system type `tty': `stream'
>> already specified
>> *** Error code 1
>>
>> Stop in /tmp/a/ports/irc/pure-xemacs-devel-mule/work/pure-0.6p.
>> *** Error code 1
>>
>> Stop in /a/ports/irc/pure-xemacs-devel-mule.
>> ================================================================
>> build ended at Thu Apr 15 15:54:55 GMT 2004
>
> The package was created for xmeacs-21.4.x. I've removed
> pure-xemacs-devel-mule and irchat-pj-xemacs-devel-mule.
> Thanks!
> --
> Yoichi NAKAYAMA
>
> ------------------------------
>
> Message: 34
> Date: Thu, 22 Apr 2004 19:12:39 +0200
> From: Roman Neuhauser <neuhauser at chello.cz>
> Subject: Re: Ethereal
> To: "Jacob S. Barrett" <jbarrett at amduat.net>
> Cc: ports at freebsd.org
> Message-ID: <20040422171239.GB1106 at isis.wad.cz>
> Content-Type: text/plain; charset=us-ascii
>
> # jbarrett at amduat.net / 2004-04-21 15:30:56 -0700:
>> On Wednesday 21 April 2004 09:57 am, Roman Neuhauser
>> <neuhauser at chello.cz>
>> wrote:
>>> # jbarrett at amduat.net / 2004-04-21 06:57:20 -0700:
>>>> I have rebuilt and installed ethereal a dozen times from ports and
>>>> every time it just installs tethereal and not ethereal. I have
>>>> explicitly set the WITH_GTK2 and still nothing. What am I doing
>>>> wrong?
>>>
>>> Anything suspicious in ${WRKSRC}/config.log ?
>>
>> checking for GTK+ - version >= 2.0.0... no
>> *** Could not run GTK+ test program, checking why...
>> *** The test program failed to compile or link. See the file
>> config.log for
>> the
>> *** exact error that occured. This usually means GTK+ is incorrectly
>> installed.
>>
>> configure:9102: checking for GTK+ - version >= 2.0.0
>> configure:9247: result: no
>> configure:9280: cc -o conftest -D_U_="__attribute__((unused))" -Wall
>> -W -O
>> -pipe -march=pentiumpro -I/usr/local/include -I/usr/local/include
>> -L/usr/local/lib conftest.c >&5
>> conftest.c:24:21: gtk/gtk.h: No such file or directory
>> conftest.c: In function `main':
>> conftest.c:30: error: `gtk_major_version' undeclared (first use in
>> this
>> function)
>> conftest.c:30: error: (Each undeclared identifier is reported only
>> once
>> conftest.c:30: error: for each function it appears in.)
>> conftest.c:30: error: `gtk_minor_version' undeclared (first use in
>> this
>> function)
>> conftest.c:30: error: `gtk_micro_version' undeclared (first use in
>> this
>> function)
>
> I don't know about your system, but on my boxes gtk is not in
> /usr/local:
>
> roman at isis ~ 1006:0 > ls -d /usr/X11R6/include/gtk*
> /usr/X11R6/include/gtk-2.0 /usr/X11R6/include/gtk12
>
> You said you didn't define WITHOUT_X11. Can you confirm it
> scientifically? Stick
>
> .if defined(WITHOUT_X11)
> .error "WITHOUT_X11 defined"
> .endif
>
> somewhere in /usr/ports/net/ethereal/Makefile and run make.
>
> --
> If you cc me or remove the list(s) completely I'll most likely ignore
> your message. see http://www.eyrie.org./~eagle/faqs/questions.html
>
> ------------------------------
>
> Message: 35
> Date: Thu, 22 Apr 2004 17:33:19 +0000 (UTC)
> From: naddy at mips.inka.de (Christian Weisgerber)
> Subject: gtar update: opinions sought
> To: freebsd-ports at freebsd.org
> Message-ID: <c68vkv$1suq$1 at kemoauc.mips.inka.de>
>
> obrien@ has pointed out to me that new releases of GNU tar have
> become available (1.13.94 so far), so I intend to revive the
> archivers/gtar port.
>
> Currently, the gtar port introduces a number of gratuitous differences
> to gtar as distributed. These were originally modifications to our
> in-tree tar and sobomox@ synched them into the port (without
> consulting the maintainer). These changes range from the arguably
> useful --fast-read option and differences in permission handling
> for root to cosmetics such as a different, locale-dependent date
> format in archive listings.
>
> Personally, I would like to drop these differences with the update
> and make our gtar port by and large follow the distribution defaults
> again. Introducing local behavior changes (other than bug fixes,
> of course) into a cross-platform tool like gtar is confusing to
> users, if not outright dangerous.
>
> Since other people might not share this view, I'd like to ask for
> opinions.
>
> Note that our system tar will likely switch to bsdtar sooner or
> later, so I don't think the gtar port is going to serve as a prototype
> for a system tar upgrade. It will just be a plain port of an
> external tool.
>
> --
> Christian "naddy" Weisgerber
> naddy at mips.inka.de
>
>
> ------------------------------
>
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to
> "freebsd-ports-unsubscribe at freebsd.org"
>
> End of freebsd-ports Digest, Vol 57, Issue 5
> ********************************************
>
Renaud B aboin
renaud at baboin.com
Mobile (France) + 33 6 84 75 06 17
Mobile (Italie) + 39 320 217 50 48
Fax + 33 1 53 01 29 06
More information about the freebsd-ports
mailing list