Re: Building the README.html's (was Re: Building the INDEX)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 2 Nov 2006, Michel Talon wrote: Speaking of "make index", I do a "make TEMPLATES=/root/.update-ports/templates/ readmes" at the top level (/usr/ports) and the perl program doesn't respect the TEMPLATES dir... the top level and the categories use the template, the individual ports do not. By the way, what do you think of the idea, instead of polluting the ports tree with README.html everywhere, to have a simple script which dynamically computes the page you want to look? All the information is in the INDEX file, hence can be extracted instantaneously. It's only a question of having pretty templates to show something nice, and a simple http server. For example i know this is trivial to do with python BaseHTTPServer, but it should be as trivial with perl or other similar tool. I *like* that idea... should such a script be in the ports tree as a port? I'll write it (in perl, it's what I happen to know and write in) if it's wanted. (I actually hook my ports tree into Apache at the moment for that http server, but I have Apache up for other purposes, anyway - see the site in my signature.) (Not that we shouldn't fix what's there. As long as we're providing it, we should fix the bugs. I'm testing my patches now. They're a +1 -1 patch to Mk/bsd.port.subdir.mk and a +2 -1 patch to Tools/make_readmes, by the way) - -- Curtis Jewell https://lap.curtisjewell.boldlygoingnowhere.org/ [EMAIL PROTECTED] "Killed enough? ... Yes, Your Highness, I think we all have." --John Patrick Ryan (from 'The Sum Of All Fears', Tom Clancy) [I use Pine, which deliberately does not display colors and pictures in HTML mail] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFFSyrLvCi+150VKIMRAqZdAJ9ozd42epZCV8yfHJHBlytc5oFBpwCfccrl o161+dxwuqlegxYQjVOUgWA= =YS4D -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
freebsd port compilation error
libsocket++ is installed yet I get an error. :-(( checking socket++/sockinet.h usability... no checking socket++/sockinet.h presence... yes configure: WARNING: socket++/sockinet.h: present but cannot be compiled configure: WARNING: socket++/sockinet.h: check for missing prerequisite headers? configure: WARNING: socket++/sockinet.h: see the Autoconf documentation configure: WARNING: socket++/sockinet.h: section "Present But Cannot Be Compiled" configure: WARNING: socket++/sockinet.h: proceeding with the preprocessor's result configure: WARNING: socket++/sockinet.h: in the future, the compiler will take precedence configure: WARNING: ## -- ## configure: WARNING: ## Report this to the AC_PACKAGE_NAME lists. ## configure: WARNING: ## -- ## checking for socket++/sockinet.h... yes checking for pid_t... yes checking for size_t... yes checking whether time.h and sys/time.h may both be included... yes checking whether struct tm is in sys/time.h or time.h... time.h checking for struct tm.tm_zone... yes checking for socket in -lsocket... no checking for gethostbyname in -lnsl... no checking for crypt in -lcrypt... yes checking for hosts_ctl in -lwrap... yes checking for stdlib.h... (cached) yes checking for unistd.h... (cached) yes checking for getpagesize... yes checking for working mmap... yes checking return type of signal handlers... void checking for gethostname... yes checking for gettimeofday... yes checking for mkdir... yes checking for select... yes checking for setpriority... yes checking for socket... yes checking for strerror... yes checking for strstr... yes checking for strtol... yes checking for syslog... yes checking for sigaction... yes checking argument 3 of accept... unsigned int* checking "libsocket++"... no configure: error: No libsocket++ Library found! ===> Script "configure" failed unexpectedly. Please report the problem to [EMAIL PROTECTED] [maintainer] and attach the "/usr/ports/news/newscache/work/NewsCache-1.2rc6/config.log" including the output of the failure of your make command. Also, it might be a good idea to provide an overview of all packages installed on your system (e.g. an `ls /var/db/pkg`). *** Error code 1 Stop in /usr/ports/news/newscache. eagle# ls /var/db/pkg XFree86-clients-4.3.0_5 lzo2-2.02_1 XFree86-fontEncodings-4.3.0 m4-1.4.4 XFree86-fontScalable-4.3.0 minicom-2.1 XFree86-libraries-4.3.0_6 mkisofs-2.0.3 Xft-2.1.2 mrtg-2.10.5_1,1 atk-1.4.1_1 ncftp-3.1.9 autoconf-2.59_2 netpbm-10.17_1 automake-1.9.6 ngpt-1.0.1 bsdpan-News-Article-1.27nmap-3.48_1 bsdpan-SNMP_Session-1.07nmapfe-3.48_1 bsdpan-newslib-0.84 nzbget-0.1.1 curl-7.10.7 openvpn-2.0.6 cvsup-without-gui-16.1h p5-IO-INET6-1.28 e2fsprogs-1.38_1p5-Socket6-0.10 expat-1.95.8_3 p5-gettext-1.05_1 ezm3-1.1pango-1.2.5 fontconfig-2.2.90_3 pcre-4.4 freetype2-2.1.5_1 perl-5.6.1_15 gd-2.0.15_1,1 perl-5.8.7 gettext-0.12.1 pkgconfig-0.15.0_1 glib-1.2.10_10 png-1.2.5_2 glib-2.2.3 postgresql-7.3.4_1 gmake-3.80_1pptpclient-1.3.1 gtk-1.2.10_10 py23-imaging-1.1.4 gtk-2.2.4_1 py23-numeric-23.0 help2man-1.36.3 py23-tkinter-2.3.2_1 imake-4.3.0_1 python-2.3.2_3 jbigkit-1.5 racoon-20050510a jpeg-6b_1 rpm2cpio-1.1.20020306 libglut-5.0.2 swig-1.1p5_9 libiconv-1.9.1_3tcl-8.4.4_1,1 libsocket++-1.12.12_1 tiff-3.6.0 libtool-1.3.5_1 tk-8.4.4,1 libtool-1.4.3_2 unrar-3.43,2 libtool-1.5.22_2uulib-0.5.20 libxml2-2.6.16 wxgtk-common-2.4.2 linux-glib2-2.2.1 wxgtk2-2.4.2_1 linux_base-7.1_5xinetd-2.3.14 lrzsz-0.12.20_1 xorg-documents-6.8.2 lynx-ssl-2.8.4.1d xorg-manpages-6.8.2 eagle# ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: make search (Was Re: Perl5.8.7 ports)
On Thu, Nov 02, 2006 at 11:05:37PM -0800, Doug Barton wrote: > >Seems make search doesn't like the following line in my /etc/make.conf > > > >PORTSDIR=/compile/ports > > > >I thought PORTSDIR was required to be set if your ports were in a > >nonstandard location, if you wanted everything to work correctly? > > I put just about everything in /usr/local (src, obj, ports, etc.) and > found out long ago that putting symlinks in /usr/ is infinitely easier > than trying to make it work with custom variables. I usually do the same, except if I have room I'll create a /compile partition and symlink src, obj, ports into it. Got bitten by a crash during a build before and had parts of /usr get trashed (probably due to ATA write cache). I figure having it as physically separate as I can get it improves the odds slightly. I added the PORTSDIR variable a while back, I'm not 100% sure why. I vaguely recall a problem with a particular port not installing correctly if /usr/ports was a symlink, but it worked fine if you had PORTSDIR set. I'm not sure if it happened to me or if I just read about it on the list, however. Craig ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: py24-m2crypto-0.16
I was just trying to build net-im/cjc, which requires security/m2crypto and ran into a problem where a symbol found in the ASN1.py file wasn't defined. Upon further investigation, it turns out that the line in the _m2crypto.i file that include _asn1.i has been commented out in the patch found in m2crypto/files/patch::_m2crypto.i. I removed this file and all is well now with both m2crypto and net-im/cjc. There is no comment as to why this line is commented out and I'm thinking it shouldn't be. -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Daemon Dancing in the Dark, a FreeBSD weblog: http://freebsd.amazingdev.com/blog/ UNIX is user-friendly. It's just a bit picky about who its friends are. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: multimedia/vlc - x264 error [multimedia/mplayer - x264 error]
On Thu, Aug 10, 2006, at 01:08:03 +0300, Vlad V. Teterya wrote: > >>> I find myself unable to build vlc. The build terminates with the > >>> following error: > >>> > >>> if /usr/local/bin/distcc cc -DHAVE_CONFIG_H -I. -I. -I../.. > >>> -I/usr/obj/mnt/homeKamikaze/ports/multimedia/vlc/work/vlc-0.8.5/include > >>> -I/usr/X11R6/include/wx-2.6/ -I/usr/local/include/dirac > >>> -I/usr/local/include/speex -I/usr/local/include > >>> -I/usr/X11R6/include -I/usr/local/include -DSYS_FREEBSD6_1 > >>> -I../../include `top_builddir="../.." ../../vlc-config --cflags > >>> plugin x264` -Wsign-compare -Wall -O2 -fno-strict-aliasing -pipe > >>> -march=pentium-m -pthread -pipe -MT libx264_plugin_a-x264.o -MD > >>> -MP -MF ".deps/libx264_plugin_a-x264.Tpo" -c -o > >>> libx264_plugin_a-x264.o `test -f 'x264.c' || echo './'`x264.c; \ > >>> then mv -f ".deps/libx264_plugin_a-x264.Tpo" > >>> ".deps/libx264_plugin_a-x264.Po"; else rm -f > >>> ".deps/libx264_plugin_a-x264.Tpo"; exit 1; fi In file included > >>> from x264.c:32: /usr/local/include/x264.h:32:4: warning: #warning > >>> You must include stdint.h or inttypes.h before x264.h x264.c: In > >>> function `Open': x264.c:550: error: structure has no member named > >>> `b_cbr' distcc[10192] ERROR: compile x264.c on localhost failed > >>> gmake[4]: *** [libx264_plugin_a-x264.o] Error 1 > > > > You can get same errors when you try to build multimedia/mplayer > > with option WITH_X264=true (after updating multimedia/x264 to > > x264-0.0.20060808) > > > > mplayer compilation errors: > > cc -c -I../libvo -I../../libvo -I/usr/X11R6/include -fno-PIC -O2 -pipe > - -march=i6 > 86 -mtune=pentium3 -O3 -ffast-math -fomit-frame-pointer > - -D_LARGEFILE_SOURCE -D_ > FILE_OFFSET_BITS=64 -I/usr/local/include/freetype2 > -I/usr/local/include > - -I. -I.. > -Inative -I../libmpdemux -I../loader -I../libavutil -I../libavcodec > - -I/usr/loc > al/include/freetype2 -I/usr/local/include -D_GNU_SOURCE -o > ve_x264.o ve_x264. > c > ve_x264.c: In function `parse_cqm': > ve_x264.c:215: warning: passing arg 2 of `strtol' from incompatible > pointer type > > ve_x264.c: In function `config': > ve_x264.c:278: error: structure has no member named `b_cbr' > gmake[1]: *** [ve_x264.o] Error 1 > gmake[1]: Залишаю каталог > "/usr/ports/multimedia/mplayer/work/MPlayer-1.0pre8/libmpcodecs" > gmake: *** [libmpcodecs/libmpcodecs.a] Error 2 > *** Error code 2 Was there a solution to the vlc/mplayer build problems (without disabling x264)? I'm just about finished with a big cvsup/rebuild with the GNOME/GTK updates, and vlc/mplayer are some of the last ports not upgraded. They are both failing with the exact same errors about x264 as in this thread. x264-0.0.20061030 and an ports tree as of around 2:00 PM Eastern USA time on Wednesday Thanks -Mark -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [nycbug-talk] creating "local" ports (fwd)
Hello all, I'm finding that there are a number of ports that we need to patch for some functionality that's unique to our business (qmail, mailfront, etc.). Currently we just do "make patch" and then apply our patches. This works, but is a bit of a pain to maintain. Is there a way to create a "local" category? ie: /usr/ports/LOCAL We might occasionally look at the real qmail/mailfront/djbdns or other ports and see if there's anything we want to pull in, but we'd most likely be doing more work with merging in more of our own patches/software. Is there some mechanism that I'm missing to deal with a local category? I've been googling without much luck, and I didn't see this addressed in the porter's handbook. Beyond that, I have a few other questions: -By default cvsup and (I assume portsnap) would nuke anything in /usr/ports that was not part of the main ports tree. How can this be dealt with in a way that none of the current/future port update methods will not clobber our local tree? -How does one handle packages that depend on say, qmail, but I now want to depend on local-qmail? I know portupgrade can be tought this by setting an alternate pkgdep, but is there any clever way of doing this so that when you're not using portupgrade the deps are adjusted? Thanks, Charles ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PHP5 for apache2.2.3
Hey I was wondering if anyone out there had any tips for installing php5 for apache2.2.3 If someone could point me in the right direction as to how to install it that would be sweet. Thanks guys. -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.430 / Virus Database: 268.13.26/516 - Release Date: 11/3/2006 2:20 PM ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ports with version numbers going backwards: www/mod_bandwidth
** The following ports have a version number that sorts before a previous one ** For many package tools to work correctly, it is of utmost importance that version numbers of a port form a monotonic increasing sequence over time. Refer to the FreeBSD Porter's Handbook, 'Package Naming Conventions' for more information. Tools that won't work include pkg_version, portupgrade and portaudit. A common error is an accidental deletion of PORTEPOCH. Please fix any errors as soon as possible. - *www/mod_bandwidth* <[EMAIL PROTECTED]>: mod_bandwidth-2.0.6.b < mod_bandwidth-2.0.6 | revision 1.9 | date: 2006/11/03 15:15:40; author: clement; state: Exp; lines: +3 -4 | - Update to 2.0.6.b ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bugathon, yeah it's time again
On Fri, 2006-10-27 at 18:13 +0100, Florent Thoumie wrote: > Ok, heads up folks. > > Ports have been frozen for some weeks now, and it's only a matter of > time before ice starts melting. So we're planning to hold the next > bugathon next week end (well, in one week). Same server, same channel > (#freebsd-bugbusters @ EFNET), you have one week to grab a list of PR > and start working on them. > > WWW: http://wikitest.freebsd.org/Bugathons/November2006 > > Note: Since I still don't receive much feedback from src-committers, I > expect it to be mainly ports-related. Obviously I may be wrong and there > will probably a few src-committers coming, this channel is still a good > place to discuss bugs. I hereby declare open the holy bugathon! -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: This is a digitally signed message part
Re: creating "local" ports (fwd)
You've got a bunch of misconceptions. In this case, that turns out to be good, because the solutions are a lot simpler than you think. Charles Sprickman <[EMAIL PROTECTED]> writes: > Hello all, > > I'm finding that there are a number of ports that we need to patch for > some functionality that's unique to our business (qmail, mailfront, > etc.). Currently we just do "make patch" and then apply our patches. > This works, but is a bit of a pain to maintain. > > Is there a way to create a "local" category? ie: /usr/ports/LOCAL Yes, you can look at category creation in the porters' handbook, but there is an easier approach: just put your own patches in the files directory of the port. This lets you take advantage of changes to the official port. > Is there some mechanism that I'm missing to deal with a local > category? I've been googling without much luck, and I didn't see this > addressed in the porter's handbook. See /usr/ports/Mk/bsd.local.mk; it is the hook that will let you do your category customization without needing to actually modify any official files. > Beyond that, I have a few other questions: > > -By default cvsup and (I assume portsnap) would nuke anything in > /usr/ports that was not part of the main ports tree. Not true. cvsup will only touch files that it thinks *it* originally put in the tree. I haven't used portsnap, but it looks as though the same applies. Therefore... > How can this be > dealt with in a way that none of the current/future port update > methods will not clobber our local tree? it's not a problem. > -How does one handle packages that depend on say, qmail, but I now want to > depend on local-qmail? I know portupgrade can be tought this by setting > an alternate pkgdep, but is there any clever way of doing this so that > when you're not using portupgrade the deps are adjusted? I don't know a way to do exactly this. My advice would be to finesse the problem: either by using portupgrade, or by using the "real" port (e.g., qmail rather than local-qmail) with your own patches, as I explained earlier. I hope that helps. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: multimedia/vlc - x264 error [multimedia/mplayer - x264 error]
On 11/3/06, Mark Kane <[EMAIL PROTECTED]> wrote: On Thu, Aug 10, 2006, at 01:08:03 +0300, Vlad V. Teterya wrote: > >>> I find myself unable to build vlc. The build terminates with the > >>> following error: > >>> > >>> if /usr/local/bin/distcc cc -DHAVE_CONFIG_H -I. -I. -I../.. > >>> -I/usr/obj/mnt/homeKamikaze/ports/multimedia/vlc/work/vlc-0.8.5/include > >>> -I/usr/X11R6/include/wx-2.6/ -I/usr/local/include/dirac > >>> -I/usr/local/include/speex -I/usr/local/include > >>> -I/usr/X11R6/include -I/usr/local/include -DSYS_FREEBSD6_1 > >>> -I../../include `top_builddir="../.." ../../vlc-config --cflags > >>> plugin x264` -Wsign-compare -Wall -O2 -fno-strict-aliasing -pipe > >>> -march=pentium-m -pthread -pipe -MT libx264_plugin_a-x264.o -MD > >>> -MP -MF ".deps/libx264_plugin_a-x264.Tpo" -c -o > >>> libx264_plugin_a-x264.o `test -f 'x264.c' || echo './'`x264.c; \ > >>> then mv -f ".deps/libx264_plugin_a-x264.Tpo" > >>> ".deps/libx264_plugin_a-x264.Po"; else rm -f > >>> ".deps/libx264_plugin_a-x264.Tpo"; exit 1; fi In file included > >>> from x264.c:32: /usr/local/include/x264.h:32:4: warning: #warning > >>> You must include stdint.h or inttypes.h before x264.h x264.c: In > >>> function `Open': x264.c:550: error: structure has no member named > >>> `b_cbr' distcc[10192] ERROR: compile x264.c on localhost failed > >>> gmake[4]: *** [libx264_plugin_a-x264.o] Error 1 > > > > You can get same errors when you try to build multimedia/mplayer > > with option WITH_X264=true (after updating multimedia/x264 to > > x264-0.0.20060808) > > > > mplayer compilation errors: > > cc -c -I../libvo -I../../libvo -I/usr/X11R6/include -fno-PIC -O2 -pipe > - -march=i6 > 86 -mtune=pentium3 -O3 -ffast-math -fomit-frame-pointer > - -D_LARGEFILE_SOURCE -D_ > FILE_OFFSET_BITS=64 -I/usr/local/include/freetype2 > -I/usr/local/include > - -I. -I.. > -Inative -I../libmpdemux -I../loader -I../libavutil -I../libavcodec > - -I/usr/loc > al/include/freetype2 -I/usr/local/include -D_GNU_SOURCE -o > ve_x264.o ve_x264. > c > ve_x264.c: In function `parse_cqm': > ve_x264.c:215: warning: passing arg 2 of `strtol' from incompatible > pointer type > > ve_x264.c: In function `config': > ve_x264.c:278: error: structure has no member named `b_cbr' > gmake[1]: *** [ve_x264.o] Error 1 > gmake[1]: Залишаю каталог > "/usr/ports/multimedia/mplayer/work/MPlayer-1.0pre8/libmpcodecs" > gmake: *** [libmpcodecs/libmpcodecs.a] Error 2 > *** Error code 2 Was there a solution to the vlc/mplayer build problems (without disabling x264)? I'm just about finished with a big cvsup/rebuild with the GNOME/GTK updates, and vlc/mplayer are some of the last ports not upgraded. They are both failing with the exact same errors about x264 as in this thread. x264-0.0.20061030 and an ports tree as of around 2:00 PM Eastern USA time on Wednesday Everything should have been fixed months ago, if you're still having problems send us an error log. Thanks -Mark -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [nycbug-talk] creating "local" ports (fwd)
Charles Sprickman wrote: > Is there a way to create a "local" category? ie: /usr/ports/LOCAL Create /usr/ports/Makefile.local containing: SUBDIR+= LOCAL > -By default cvsup and (I assume portsnap) would nuke anything in > /usr/ports that was not part of the main ports tree. How can this be > dealt with in a way that none of the current/future port update > methods will not clobber our local tree? cvsup won't nuke a file that it knows nothing about. ie. it only nukes files that have history in CVS. portsnap I believe is less friendly to local additions. A simple method of dealing with this is to keep your LOCAL tree in an entirely separate filesystem and write yourself a tiny little script to generate symlinks under /usr/ports. > -How does one handle packages that depend on say, qmail, but I now > want to depend on local-qmail? I know portupgrade can be tought this > by setting an alternate pkgdep, but is there any clever way of doing > this so that when you're not using portupgrade the deps are adjusted? That's a generic problem with ports -- instead of registering a dependency on the package that provided the file that satisfied the test specified by the FOO_DEPENDS variable in the port Makefile, the dependency is registered on the default package to install to resolve the dependency as shown in the second half of the FOO_DEPENDS line. As far as I know portupgrade is the only software with the alt-pkgdep functionality available: it isn't available in the basic ports per-se, although a number of popular core ports can specify alternate dependencies where support for doing that has been specifically written into the various Makefiles involved. No idea if either portmaster or portmanager have any similar alternate dependency functionality though. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: PHP5 for apache2.2.3
Jason Gretz wrote: > Hey I was wondering if anyone out there had any tips for installing > php5 for apache2.2.3 If someone could point me in the right direction > as to how to install it that would be sweet. Thanks guys. Step 1: Install www/apache22 # cd /usr/ports/www.apache22 # make install Step 2: Install lang/php5, making sure to check the 'APACHE' option in the configuration dialog. # cd /usr/ports/lang/php5 # make install Step 3: You're done. Or you can put: WITH_APACHE2= yes APACHE_PORT=www/apache22 into /etc/make.conf, then jump to step 2 above and let apache22 be installed as a dependency of lang/php5 Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: [nycbug-talk] creating "local" ports (fwd)
On Nov 3, 2006, at 3:30 PM, Charles Sprickman wrote: Is there some mechanism that I'm missing to deal with a local category? I've been googling without much luck, and I didn't see this addressed in the porter's handbook. Check the June 8 archives for this mailing list, for my message with subject "Re: category for local ports". I only use it for truly local ports, not altered versions of regular ports. Can you not submit patches to them with appropriate flags to set to get the behavior you desire? Beyond that, I have a few other questions: -By default cvsup and (I assume portsnap) would nuke anything in / usr/ports that was not part of the main ports tree. How can this be dealt with in a way that none of the current/future port update methods will not clobber our local tree? portsnap seems to leave my local subdir alone. I don't recall doing anything special to make it ignore it. -How does one handle packages that depend on say, qmail, but I now want to depend on local-qmail? I know portupgrade can be tought this by setting an alternate pkgdep, but is there any clever way of doing this so that when you're not using portupgrade the deps are adjusted? I doubt it. Answer is to always use portupgrade :-)
Re: multimedia/vlc - x264 error [multimedia/mplayer - x264 error]
On Fri, Nov 03, 2006, at 16:11:55 -0500, Michael Johnson wrote: > Everything should have been fixed months ago, if you're still having > problems send us an error log. Here are the full build logs from vlc and mplayer: http://tntpowerhost.com/mixx941/mixx941_vlc_and_mplayer_build_logs_110306.tar.bz2 Most everything else upgraded fine. There are a few things that I still need to go through and see what the errors were, but they're unrelated to vlc and mplayer (stuff like linux-realplayer, bmpx, blender-devel, etc). Thanks. -Mark FreeBSD 6.2-PRERELEASE [amd64] -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: multimedia/vlc - x264 error [multimedia/mplayer - x264 error]
On 11/3/06, Mark Kane <[EMAIL PROTECTED]> wrote: On Fri, Nov 03, 2006, at 16:11:55 -0500, Michael Johnson wrote: > Everything should have been fixed months ago, if you're still having > problems send us an error log. Here are the full build logs from vlc and mplayer: http://tntpowerhost.com/mixx941/mixx941_vlc_and_mplayer_build_logs_110306.tar.bz2 both are fixed now, thanks! Most everything else upgraded fine. There are a few things that I still need to go through and see what the errors were, but they're unrelated to vlc and mplayer (stuff like linux-realplayer, bmpx, blender-devel, etc). Thanks. -Mark FreeBSD 6.2-PRERELEASE [amd64] -- Internet Radio: Party107 (Trance/Electronic) - http://www.party107.com Rock 101.9 The Edge (Rock) - http://www.rock1019.net IRC: MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [nycbug-talk] creating "local" ports (fwd)
On Fri, Nov 03, 2006 at 03:30:47PM -0500, Charles Sprickman wrote:
> I'm finding that there are a number of ports that we need to patch for
> some functionality that's unique to our business (qmail, mailfront, etc.).
> Currently we just do "make patch" and then apply our patches. This works,
> but is a bit of a pain to maintain.
The easiest way is to make patch-* files and put them in the 'files'
directory under a port, as already mentioned. cvsup will leave them
alone but I think portsnap might delete them.
A few times I've wanted to rm -rf /usr/ports and recreate it for
whatever reason without losing my patches, so nowadays I'm using the
following (ugly) hack:
- BEGIN /usr/Makefile.inc --
.include "/usr/ports-patches/Makefile"
- END /usr/Makefile.inc --
- BEGIN /usr/ports-patches/Makefile -
TMPCURDIR=${.CURDIR:S/\/usr\/ports//}
.ifmake do-patch
TPATCHES!=echo /usr/ports-patches${TMPCURDIR}/patch-*
.if ! ${TPATCHES:M*\*}
EXTRA_PATCHES+= ${TPATCHES}
.endif
.endif
- END /usr/ports-patches/Makefile -
Under /usr/ports-patches I set up a hierarchy mirroring /usr/ports
except it only contains local patch files that I want to apply. The
layout works something like this:
$ cd /usr/ports-patches && find . -type f | sort
./Makefile
./devel/sdl12/patch-cmb-joystick
./graphics/png/patch-apng
./net/rdesktop/patch-seamless-fixes
./net-im/gaim/patch-cmb-jep0008
./www/firefox/patch-apng
./x11/kdebase3/patch-cmb-bsdmonitors
./x11/kdebase3/patch-cmb-unbreak-bargraph
Actually mine is slightly different since I have ports under a different
directory and define TMPCURDIR in /etc/make.conf (in order to do
conditional settings), but the above should work for a stock install.
The /usr/Makefile.inc hack is really bad, but bsd.port.mk doesn't seem
to import any other top-level local Makefiles. It would be nice if
there was a better hook to do this sort of thing. make.conf might work
as well but I was trying to minimize the impact on non-FreeBSD
makefiles.
Craig
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [nycbug-talk] creating "local" ports (fwd)
Charles,
On Nov 3, 2006, at 3:30 PM, Charles Sprickman wrote:
Hello all,
I'm finding that there are a number of ports that we need to patch
for some functionality that's unique to our business (qmail,
mailfront, etc.). Currently we just do "make patch" and then apply
our patches. This works, but is a bit of a pain to maintain.
Is there a way to create a "local" category? ie: /usr/ports/LOCAL
I hate to keep referring to my article but I go over this here:
http://www.onlamp.com/pub/a/bsd/2006/04/13/freebsd-build-system.html?
page=2
Basically, you can create a port with this in the Makefile:
CATEGORIES=local
VALID_CATEGORIES+= ${CATEGORIES}
I have an example port here:
http://www.onlamp.com/bsd/2006/04/13/examples/Makefile
Thanks goes to freebsd-ports.freebsd.org for this tip actually (which
is where I originally found out about it).
We might occasionally look at the real qmail/mailfront/djbdns or
other ports and see if there's anything we want to pull in, but
we'd most likely be doing more work with merging in more of our own
patches/software.
Is there some mechanism that I'm missing to deal with a local
category? I've been googling without much luck, and I didn't see
this addressed in the porter's handbook.
Beyond that, I have a few other questions:
-By default cvsup and (I assume portsnap) would nuke anything in /
usr/ports that was not part of the main ports tree. How can this
be dealt with in a way that none of the current/future port update
methods will not clobber our local tree?
Add "local" to /usr/ports/.cvsignore
-How does one handle packages that depend on say, qmail, but I now
want to
depend on local-qmail? I know portupgrade can be tought this by
setting
an alternate pkgdep, but is there any clever way of doing this so
that when you're not using portupgrade the deps are adjusted?
Not sure how to handle this one. You may need to just either make
dependent packages or patch the Makefiles after you do a cvsup.
Besides that, cool tip about the patches being able to put in the
files dir and the bsd.local.mk file.
-Bjorn
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
sysutils/syslog-ng/files/syslong-ng.sh.in patch
This is a nice little patch we use to purge out /dev/klog after
/etc/rc.d/dmesg and before /usr/local/etc/rc.d/syslog-ng.sh.
It's useful for shops that translate user.info facility/priority syslog
messages into SMS/E-Mail via a log{} mechanism (i.e., hardware error
messages from the kernel, like some flunky in the NOC plugging a keyboard
into your system).
It lets you avoid 200 lines of boot messages in log(9) making their way
into your log{} mechanism or into your pager.
We want to feed it upstream because we think others will find it useful.
~BAS
$ diff -u /usr/ports/sysutils/syslog-ng/files/syslog-ng.sh.in
syslog-ng.sh.in
--- /usr/ports/sysutils/syslog-ng/files/syslog-ng.sh.in Wed Mar 29
16:20:19 2006
+++ syslog-ng.sh.in Fri Nov 3 20:32:59 2006
@@ -14,6 +14,8 @@
#syslog_ng_enable="YES"
#
+syslog_ng_purgeklog=${syslog_ng_purgeklig-"NO"}
+
. %%RC_SUBR%%
name=syslog_ng
@@ -23,6 +25,11 @@
required_files=%%PREFIX%%/etc/syslog-ng/syslog-ng.conf
pidfile=/var/run/syslog.pid
extra_commands=reload
+
+if checkyesno syslog_ng_purgeklog; then
+start_precmd="echo \"Purging klog(9)\" && sysctl -w
kern.msgbuf_clear=1 $start_precmd";
+fi
+
stop_postcmd=stop_postcmd
load_rc_config $name
l8*
-lava (Brian A. Seklecki - Pittsburgh, PA, USA)
http://www.spiritual-machines.org/
"...from back in the heady days when "helpdesk" meant nothing, "diskquota"
meant everything, and lives could be bought and sold for a couple of pages
of laser printout - and frequently were."
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Ports with duplicate LATEST_LINKS
Dear port maintainers, The following list includes ports maintained by you that have duplicate LATEST_LINK values. They should either be modified to use a unique LATEST_LINK or suppressed using NO_LATEST_LINK, to avoid overwriting each other in the packages/Latest directory. If your ports conflict with ports maintained by another person, please coordinate your efforts with them. Thanks, Kris "Annoying Reminder Guy II" Kennaway LATEST_LINK PORTNAME MAINTAINER == audacity audio/audacity [EMAIL PROTECTED] audacity audio/audacity-devel [EMAIL PROTECTED] dbh databases/dbh [EMAIL PROTECTED] dbh databases/dbh10[EMAIL PROTECTED] metasploit security/metasploit[EMAIL PROTECTED] metasploit security/metasploit-devel [EMAIL PROTECTED] mnogosearch www/pecl-mnogosearch [EMAIL PROTECTED] mnogosearch www/mnogosearch[EMAIL PROTECTED] nsd dns/nsd[EMAIL PROTECTED] nsd dns/nsd2 [EMAIL PROTECTED] vtk43math/vtk43 [EMAIL PROTECTED] vtk43math/vtk43-headers [EMAIL PROTECTED] Total: 12 ports ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: make ports depending on sysutils/cdrtools* USE_GNOME=cdrools
Thanks for your many comments!
On Tue, 31 Oct 2006 14:36:54 -0600
"Scot Hetzel" <[EMAIL PROTECTED]> wrote:
> If it doesn't then it would be better to add a USE_CDRTOOLS knob to
> bsd.port.mk
> that would allow the selection of either the cdrtools or cdrtools-cjk ports.
> .if defined(USE_CDRTOOLS)
> .if exists(${DOCSDIR}/cdrtools-cjk/README) || defined(WITH_CJK) ||
> ${USE_CDRTOOLS} == "CJK"
> WANT_CDRTOOLS_CJK= yes
> .endif
> .if defined(WANT_CDRTOOLS_CJK)
> RUN_DEPENDS+= cdrecord:${PORTSDIR}/sysutils/cdrtools-cjk
> .else
> RUN_DEPENDS+= cdrecord:${PORTSDIR}/sysutils/cdrtools
> .endif
> .endif
I rewrote a patch like following.
o Fix some bugs. (position is bad)
o Change bsd.port.mk instead of bsd.gnome.mk.
If this patch is good, I'll send-pr it and forward to [EMAIL PROTECTED]
Index: Mk/bsd.port.mk
===
RCS file: /home/ncvs/ports/Mk/bsd.port.mk,v
retrieving revision 1.544
diff -u -r1.544 bsd.port.mk
--- Mk/bsd.port.mk 30 Sep 2006 19:25:45 - 1.544
+++ Mk/bsd.port.mk 4 Nov 2006 03:29:31 -
@@ -2081,6 +2081,15 @@
RUN_DEPENDS+= gs:${PORTSDIR}/${GHOSTSCRIPT_PORT}
.endif
+# Set up the cdrtools.
+.if defined(USE_CDRTOOLS)
+.if exists(${DOCSDIR}/cdrtools-cjk/README) || defined(WITH_CJK) ||
${USE_CDRTOOLS:L} == "cjk"
+RUN_DEPENDS+= cdrecord:${PORTSDIR}/sysutils/cdrtools-cjk
+.else
+RUN_DEPENDS+= cdrecord:${PORTSDIR}/sysutils/cdrtools
+ .endif
+.endif
+
# Macro for doing in-place file editing using regexps
REINPLACE_ARGS?= -i.bak
REINPLACE_CMD?=${SED} ${REINPLACE_ARGS}
Index: audio/abcde/Makefile
===
RCS file: /home/ncvs/ports/audio/abcde/Makefile,v
retrieving revision 1.29
diff -u -r1.29 Makefile
--- audio/abcde/Makefile3 May 2006 05:14:08 - 1.29
+++ audio/abcde/Makefile4 Nov 2006 03:19:51 -
@@ -28,7 +28,7 @@
PLIST_FILES= bin/abcde bin/cddb-tool etc/abcde.conf
.if defined(WITH_CDDA2WAV)
-RUN_DEPENDS+= cdda2wav:${PORTSDIR}/sysutils/cdrtools
+USE_CDRTOOLS= yes
.endif
.if defined(WITH_DAGRAB)
Index: audio/grip/Makefile
===
RCS file: /home/ncvs/ports/audio/grip/Makefile,v
retrieving revision 1.73
diff -u -r1.73 Makefile
--- audio/grip/Makefile 14 Oct 2006 08:52:32 - 1.73
+++ audio/grip/Makefile 4 Nov 2006 03:19:51 -
@@ -64,7 +64,7 @@
.endif
.if defined(WITH_CDDA2WAV)
-RUN_DEPENDS+= cdda2wav:${PORTSDIR}/sysutils/cdrtools
+USE_CDRTOOLS= yes
.endif
.if defined(WITH_BLADEENC)
Index: audio/mp3burn/Makefile
===
RCS file: /home/ncvs/ports/audio/mp3burn/Makefile,v
retrieving revision 1.5
diff -u -r1.5 Makefile
--- audio/mp3burn/Makefile 3 Jul 2006 03:39:46 - 1.5
+++ audio/mp3burn/Makefile 4 Nov 2006 03:19:51 -
@@ -17,13 +17,13 @@
ogg123:${PORTSDIR}/audio/vorbis-tools \
${SITE_PERL}/MP3/Info.pm:${PORTSDIR}/audio/p5-MP3-Info \
${SITE_PERL}/${PERL_ARCH}/Ogg/Vorbis/Header.pm:${PORTSDIR}/audio/p5-Ogg-Vorbis-Header
\
- cdrecord:${PORTSDIR}/sysutils/cdrtools \
${SITE_PERL}/String/ShellQuote.pm:${PORTSDIR}/textproc/p5-String-ShellQuote
WRKSRC=${WRKDIR}/${PORTNAME}
USE_BZIP2= yes
USE_PERL5= yes
+USE_CDRTOOLS= yes
NO_BUILD= yes
MAN1= mp3burn.1
Index: audio/prokyon3/Makefile
===
RCS file: /home/ncvs/ports/audio/prokyon3/Makefile,v
retrieving revision 1.10
diff -u -r1.10 Makefile
--- audio/prokyon3/Makefile 3 May 2006 05:14:25 - 1.10
+++ audio/prokyon3/Makefile 4 Nov 2006 03:19:51 -
@@ -38,8 +38,8 @@
.endif
.if defined(WITH_BURN)
-RUN_DEPENDS+= cdrecord:${PORTSDIR}/sysutils/cdrtools \
- mpg123:${PORTSDIR}/audio/mpg123 \
+USE_CDRTOOLS= yes
+RUN_DEPENDS+= mpg123:${PORTSDIR}/audio/mpg123 \
ogg123:${PORTSDIR}/audio/vorbis-tools \
normalize:${PORTSDIR}/audio/normalize \
bash:${PORTSDIR}/shells/bash2
Index: graphics/lphoto/Makefile
===
RCS file: /home/ncvs/ports/graphics/lphoto/Makefile,v
retrieving revision 1.14
diff -u -r1.14 Makefile
--- graphics/lphoto/Makefile24 May 2006 14:21:42 - 1.14
+++ graphics/lphoto/Makefile4 Nov 2006 03:19:51 -
@@ -23,7 +23,7 @@
RUN_DEPENDS= gphoto2:${PORTSDIR}/graphics/gphoto2 \
kdepyuic:${PORTSDIR}/x11-toolkits/py-kde \
${PYTHON_SITELIBDIR}/OpenGL/GL/GL__init__.py:${PORTSDIR}/graphics/py-opengl
-# cdrecord:${PORTSDIR}/sysutils/cdrtools
+#USE_CDRTOOLS= yes
USE_PYTHON=yes
NO_BUILD= yes
Index: misc/instant-workstation/Makefile
=
$snmpd_flush_cache for Net-SNMP ports/net-mgmt/net-snmp/files/snmpd.sh.in
FYI to SNMP hackers. Objections to this patch?
--
Brian A. Seklecki <[EMAIL PROTECTED]>
Collaborative Fusion, Inc.
--- Begin Message ---
Good call on the $snmpd_pidfile=
Another useful flag would be an optional pre_start() to blow away the
Exec cache (which lingers after the process dies without documentation)
Basically if you're writing a lot of your own passthrough OIDs and one
of them fails to exec, a simple restart of SNMP should be enough to
flush out:
+start_precmd=snmpd_precmd
+snmpd_precmd () {
+ if checkyesno snmpd_flush_cache; then
+ rm -rvf /var/net-snmp/.snmp-exec-cache
fi
~BAS
--
Brian A. Seklecki <[EMAIL PROTECTED]>
Collaborative Fusion, Inc.
--- End Message ---
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [nycbug-talk] creating "local" ports (fwd)
Matthew Seaman wrote: > That's a generic problem with ports -- instead of registering a > dependency on the package that provided the file that satisfied the > test specified by the FOO_DEPENDS variable in the port Makefile, the > dependency is registered on the default package to install to resolve > the dependency as shown in the second half of the FOO_DEPENDS line. That's both a positive and a negative. The positive is that the ports infrastructure works transparently when a dependency is satisfied by another port at build/run time. But you're right, it doesn't have a mechanism for translating that knowledge into something to record in the +CONTENTS file. > No idea if either portmaster or portmanager have any similar > alternate dependency functionality though. What portmaster does is to read CONFLICTS for each port that is depended on, and then look to see if you have one of those ports installed. If it does, it treats that port as the one to satisfy the dependency for purposes of looking for updates, building your port, etc. It does not twiddle with the DEPORIGIN in the +CONTENTS file however. hth, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: $snmpd_flush_cache for Net-SNMP ports/net-mgmt/net-snmp/files/snmpd.sh.in
On Fri, 03 Nov 2006 23:18:11 -0500 "Brian A. Seklecki" <[EMAIL PROTECTED]> mentioned: > FYI to SNMP hackers. Objections to this patch? > Looks reasonable. -- Stanislav Sedov <[EMAIL PROTECTED]>[[Russia, Moscow]] PGP id: 0xEB269581 http://people.freebsd.org/~stas/stas.key.asc pgplB9SiMLXq4.pgp Description: PGP signature
