Re: FreeBSD Port: mrxvt-0.3.9
On Wed, Aug 01, 2007 at 12:28:36PM -0400, David Yeske wrote: > I will look into this. Thank you for informing me of this. > > On 1/19/05, Jan Marek <[EMAIL PROTECTED]> wrote: > > Hello, > > sorry for disturbing, but do You plan to add more updated version of > > this terminal ? I think there's version 0.3.14 available for linux which > > allows to customize keybindigs, that miss so much in this version. > > Thx for Your answer > > > > Jan Marek You can also try x11/mrxvt-devel, which is at version 0.5.2. Lars pgpsjopIoKO6V.pgp Description: PGP signature
Re: ldconfig when PACKAGE_BUILDING=YES (and linux ports)
On Fri, 3 Aug 2007 19:38:29 -0400 Kris Kennaway wrote: > On Sat, Aug 04, 2007 at 02:09:47AM +0400, Boris Samorodov wrote: > > On Fri, 03 Aug 2007 23:58:47 +0200 Pav Lucistnik wrote: > > > Boris Samorodov pe v so 04. 08. 2007 v 01:30 +0400: > > > > > > Seems that running ldconfig while building a package at package > > > > cluster (i.e. when PACKAGE_BUILDING is defined) is quite useless. [1] > > > > > > > > To be more specific I'm interested at linux ports. ATM we run linux > > > > ldconfig (using linuxulator) _at package building_. Hence to create a > > > > package for FC6 port we should change compat.linux.osrelease (which I > > > > don't like and try to avoid). If the "ldconfig" stage may be skipped > > > > when PACKAGE_BUILDING is defined then things get way too easier both > > > > for default kernel linux.osrelease and default linux_base port change. > > > > > I don't follow - what is the problem? > > > > An FC6 port can't be build (and more specific -- linux-fc6 ldconfig > > doesn't run) with current default compat.linux.osrelease=2.4.2. So > > this sysctl should be changed to 2.6.16 for package building sake. > > When the default compat.linux.osrelease will be switched to 2.6.16 we > > will get the other way round problem if we try to build and FC4 port. > > > > I don't like the status quo and want to find a way to siplify it. > That's a kernel problem, not a ldconfig problem. Kris, now I don't follow. Can you explain what did you mean? WBR -- bsam ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
HEADSUP: Ports DESTDIR functionality reworked
FYI, the overcomplicated and nearly useless DESTDIR functionality has been rewritten as my SoC 2007 project and the new implementation has been committed into CVS. This one does not require individual ports to be modified, so it is much simpler to use. It utilizes chroot(1) and mount_nullfs(1) to build packages for a jail. It is implemented in a new Makefile, called bsd.destdir.mk. You can refer to the header of this file if you need a documentation. At the same time, another new Makefile has been introcuded: bsd.commands.mk. All the variable definitions that cover the command line tools, e.g. MKDIR has been extracted, because it simplifies the structure of the infrastructure Makefiles and it can be reused later within the infrastructure. Thanks goes to Andrew Pantyukhin (sat@) for providing important and useful suggestions and a lot of support as my SoC mentor. Regards, -- Gabor Kovesdan FreeBSD Volunteer EMAIL: [EMAIL PROTECTED] .:|:. [EMAIL PROTECTED] WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org --- Begin Message --- gabor 2007-08-04 11:37:24 UTC FreeBSD ports repository Modified files: .CHANGES UPDATING Mk bsd.emacs.mk bsd.gnome.mk bsd.mail.mk bsd.openssl.mk bsd.port.mk bsd.port.subdir.mk bsd.python.mk bsd.ruby.mk Tools/scriptssecurity-check.awk Added files: Mk bsd.commands.mk bsd.destdir.mk Log: - Extract command variable definitions from bsd.port.mk, they are now stored in bsd.commands.mk and can be easily reused within the infrastructure. - Revert old DESTDIR implementation. - Add a new, fully chrooted DESTDIR implementation as bsd.destdir.mk. Sponsored by: Google Summer of Code 2007 Approved by:portmgr (pav) Revision ChangesPath 1.77 +17 -1 ports/CHANGES 1.1 +99 -0 ports/Mk/bsd.commands.mk (new) 1.1 +222 -0ports/Mk/bsd.destdir.mk (new) 1.68 +3 -3 ports/Mk/bsd.emacs.mk 1.143 +8 -8 ports/Mk/bsd.gnome.mk 1.3 +3 -3 ports/Mk/bsd.mail.mk 1.35 +7 -7 ports/Mk/bsd.openssl.mk 1.578 +168 -450 ports/Mk/bsd.port.mk 1.71 +35 -40ports/Mk/bsd.port.subdir.mk 1.99 +2 -2 ports/Mk/bsd.python.mk 1.163 +3 -3 ports/Mk/bsd.ruby.mk 1.3 +10 -40ports/Tools/scripts/security-check.awk 1.532 +18 -1 ports/UPDATING --- 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: FreeBSD Port: rsyslog-1.17.4
On 8/2/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Trying to install rsyslog from ports and getting the following error: > > net.h:72: warning: "struct sockaddr_storage" declared inside parameter list > net.h:72: warning: its scope is only this definition or declaration, which > is probably not what you want > omfwd.c: In function `doAction': > omfwd.c:571: error: `AI_NUMERICSERV' undeclared (first use in this function) > omfwd.c:571: error: (Each undeclared identifier is reported only once > omfwd.c:571: error: for each function it appears in.) > omfwd.c: In function `parseSelectorAct': > omfwd.c:854: error: `AI_NUMERICSERV' undeclared (first use in this function) > *** Error code 1 > > Stop in /usr/ports/sysutils/rsyslog/work/rsyslog-1.17.6. > *** Error code 1 > > Stop in /usr/ports/sysutils/rsyslog/work/rsyslog-1.17.6. > *** Error code 1 > > Stop in /usr/ports/sysutils/rsyslog. > > > System is FreeBSD 5.x STABLE, here is uname: > FreeBSD rjclark1.mdacc.tmc.edu 5.5-STABLE FreeBSD 5.5-STABLE #0: Fri Jul 20 > 10:08:31 CDT 2007 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/MDACC1 i386 > > Is there an issue with my system, or is something broken in the code? I'm afraid 5.x may have differences from 6.x substantial enough to break rsyslog. I'll wait for our package-building cluster and see if it can reproduce the error, but if it does, I'll probably just mark rsyslog broken on 5.x. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
FreeBSD Port: automake-1.9.6_2
Hello, Please check http://docs.freebsd.org/cgi/getmsg.cgi?fetch=2031017+0+current/freebsd-ports-bugs Is this bug? -- Sincerely, Sergiy mailto:[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: ldconfig when PACKAGE_BUILDING=YES (and linux ports)
On Sat, Aug 04, 2007 at 03:20:49PM +0400, Boris Samorodov wrote: > On Fri, 3 Aug 2007 19:38:29 -0400 Kris Kennaway wrote: > > On Sat, Aug 04, 2007 at 02:09:47AM +0400, Boris Samorodov wrote: > > > On Fri, 03 Aug 2007 23:58:47 +0200 Pav Lucistnik wrote: > > > > Boris Samorodov pe v so 04. 08. 2007 v 01:30 +0400: > > > > > > > > Seems that running ldconfig while building a package at package > > > > > cluster (i.e. when PACKAGE_BUILDING is defined) is quite useless. [1] > > > > > > > > > > To be more specific I'm interested at linux ports. ATM we run linux > > > > > ldconfig (using linuxulator) _at package building_. Hence to create a > > > > > package for FC6 port we should change compat.linux.osrelease (which I > > > > > don't like and try to avoid). If the "ldconfig" stage may be skipped > > > > > when PACKAGE_BUILDING is defined then things get way too easier both > > > > > for default kernel linux.osrelease and default linux_base port change. > > > > > > > I don't follow - what is the problem? > > > > > > An FC6 port can't be build (and more specific -- linux-fc6 ldconfig > > > doesn't run) with current default compat.linux.osrelease=2.4.2. So > > > this sysctl should be changed to 2.6.16 for package building sake. > > > When the default compat.linux.osrelease will be switched to 2.6.16 we > > > will get the other way round problem if we try to build and FC4 port. > > > > > > I don't like the status quo and want to find a way to siplify it. > > > That's a kernel problem, not a ldconfig problem. > > Kris, now I don't follow. Can you explain what did you mean? ldconfig is just a symptom. If you make it so ldconfig doesn't run then you'll just run into the next problem from another 2.6.x binary being run. The fix is to get 2.6.16 kernel support good enough so that it can a) run 2.4 binaries in a backwards compatible mode (this is required anyway, you need to be able to run both binaries on the same system), b) be made default. kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: ports CHANGES UPDATING ports/Mk bsd.commands.mk bsd.destdir.mk bsd.emacs.mk bsd.gnome.mk bsd.mail.mk bsd.openssl.mk bsd.port.mk bsd.port.subdir.mk bsd.python.mk bsd.ruby.mk ports/Tool
Gabor Kovesdan wrote:
> gabor 2007-08-04 11:37:24 UTC
>
> FreeBSD ports repository
>
> Modified files:
> .CHANGES UPDATING
> Mk bsd.emacs.mk bsd.gnome.mk bsd.mail.mk
> bsd.openssl.mk bsd.port.mk
> bsd.port.subdir.mk bsd.python.mk
> bsd.ruby.mk
> Tools/scriptssecurity-check.awk
> Added files:
> Mk bsd.commands.mk bsd.destdir.mk
> Log:
> - Extract command variable definitions from bsd.port.mk, they are now
> stored in
> bsd.commands.mk and can be easily reused within the infrastructure.
> - Revert old DESTDIR implementation.
> - Add a new, fully chrooted DESTDIR implementation as bsd.destdir.mk.
>
> Sponsored by: Google Summer of Code 2007
> Approved by:portmgr (pav)
>
> Revision ChangesPath
> 1.77 +17 -1 ports/CHANGES
> 1.1 +99 -0 ports/Mk/bsd.commands.mk (new)
> 1.1 +222 -0ports/Mk/bsd.destdir.mk (new)
> 1.68 +3 -3 ports/Mk/bsd.emacs.mk
> 1.143 +8 -8 ports/Mk/bsd.gnome.mk
> 1.3 +3 -3 ports/Mk/bsd.mail.mk
> 1.35 +7 -7 ports/Mk/bsd.openssl.mk
> 1.578 +168 -450 ports/Mk/bsd.port.mk
> 1.71 +35 -40ports/Mk/bsd.port.subdir.mk
> 1.99 +2 -2 ports/Mk/bsd.python.mk
> 1.163 +3 -3 ports/Mk/bsd.ruby.mk
> 1.3 +10 -40ports/Tools/scripts/security-check.awk
> 1.532 +18 -1 ports/UPDATING
>
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/CHANGES.diff?&r1=1.76&r2=1.77&f=h
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.commands.mk
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.destdir.mk
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.emacs.mk.diff?&r1=1.67&r2=1.68&f=h
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.gnome.mk.diff?&r1=1.142&r2=1.143&f=h
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.mail.mk.diff?&r1=1.2&r2=1.3&f=h
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.openssl.mk.diff?&r1=1.34&r2=1.35&f=h
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk.diff?&r1=1.577&r2=1.578&f=h
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.subdir.mk.diff?&r1=1.70&r2=1.71&f=h
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.python.mk.diff?&r1=1.98&r2=1.99&f=h
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Mk/bsd.ruby.mk.diff?&r1=1.162&r2=1.163&f=h
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/Tools/scripts/security-check.awk.diff?&r1=1.2&r2=1.3&f=h
> http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/UPDATING.diff?&r1=1.531&r2=1.532&f=h
This is nice work, but it seems to require the attached patch. Without
it I get the following error messages:
"/usr/ports/Mk/bsd.port.mk", line 1092: Could not find /Mk/bsd.commands.mk
-p: not found
"/usr/ports/Mk/bsd.port.mk", line 1139: warning: " -p" returned
non-zero status
-s: not found
"/usr/ports/Mk/bsd.port.mk", line 1147: warning: " -s" returned
non-zero status
-r: not found
-e: not found
"/usr/ports/Mk/bsd.port.mk", line 1152: warning: " -r | -e
's/[-(].*//'" returned non-zero status
/^#define __FreeBSD_version/ {print $3}: not found
"/usr/ports/Mk/bsd.port.mk", line 1158: warning: " '/^#define
__FreeBSD_version/ {print $3}' < /usr/include/sys/param.h" returned
non-zero status
/var/db/ports//options: not found
"/usr/ports/Mk/bsd.port.mk", line 1217: warning: "
"/var/db/ports//options"" returned non-zero status
make: fatal errors encountered -- cannot continue
hth,
Doug
--
This .signature sanitized for your protection
Index: bsd.port.mk
===
RCS file: /usr/local/ncvs/ports/Mk/bsd.port.mk,v
retrieving revision 1.578
diff -u -r1.578 bsd.port.mk
--- bsd.port.mk 4 Aug 2007 11:37:23 - 1.578
+++ bsd.port.mk 4 Aug 2007 18:46:39 -
@@ -1089,6 +1089,8 @@
# Most port authors should not need to understand anything after this point.
#
+PORTSDIR?= /usr/ports
+
.include "${PORTSDIR}/Mk/bsd.commands.mk"
#
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ldconfig when PACKAGE_BUILDING=YES (and linux ports)
On Sat, 4 Aug 2007 12:14:30 -0400 Kris Kennaway wrote: > On Sat, Aug 04, 2007 at 03:20:49PM +0400, Boris Samorodov wrote: > > On Fri, 3 Aug 2007 19:38:29 -0400 Kris Kennaway wrote: > > > On Sat, Aug 04, 2007 at 02:09:47AM +0400, Boris Samorodov wrote: > > > > On Fri, 03 Aug 2007 23:58:47 +0200 Pav Lucistnik wrote: > > > > > Boris Samorodov pe v so 04. 08. 2007 v 01:30 +0400: > > > > > > > > > > Seems that running ldconfig while building a package at package > > > > > > cluster (i.e. when PACKAGE_BUILDING is defined) is quite useless. > > > > > > [1] > > > > > > > > > > > > To be more specific I'm interested at linux ports. ATM we run linux > > > > > > ldconfig (using linuxulator) _at package building_. Hence to create > > > > > > a > > > > > > package for FC6 port we should change compat.linux.osrelease (which > > > > > > I > > > > > > don't like and try to avoid). If the "ldconfig" stage may be skipped > > > > > > when PACKAGE_BUILDING is defined then things get way too easier both > > > > > > for default kernel linux.osrelease and default linux_base port > > > > > > change. > > > > > > > > > I don't follow - what is the problem? > > > > > > > > An FC6 port can't be build (and more specific -- linux-fc6 ldconfig > > > > doesn't run) with current default compat.linux.osrelease=2.4.2. So > > > > this sysctl should be changed to 2.6.16 for package building sake. > > > > When the default compat.linux.osrelease will be switched to 2.6.16 we > > > > will get the other way round problem if we try to build and FC4 port. > > > > > > > > I don't like the status quo and want to find a way to siplify it. > > > > > That's a kernel problem, not a ldconfig problem. > > > > Kris, now I don't follow. Can you explain what did you mean? > ldconfig is just a symptom. If you make it so ldconfig doesn't run So far nobody said if running ldconfig for package building is useless (as I suspect). If it's useless then axing this process doesn't do any harm. But it may help building most of linux-2.6 ports (which use the only one linux binary -- ldconfig -- when building/packaging). And even more, packages may be created at any FreeBSD version for any FreeBSD version. [1] That is what I try to discuss. > then you'll just run into the next problem from another 2.6.x binary > being run. The fix is to get 2.6.16 kernel support good enough so > that it can a) run 2.4 binaries in a backwards compatible mode (this > is required anyway, you need to be able to run both binaries on the > same system), b) be made default. While you may be right I can't comment in details here. But anyway seems that problems building an FC6 package at 7-x jail at 6-x host may exist very long since now. And this problem doen't exist at the scenario [1] I try to discuss. WBR -- bsam ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvs commit: ports CHANGES UPDATING ports/Mk bsd.commands.mk bsd.destdir.mk bsd.emacs.mk bsd.gnome.mk bsd.mail.mk bsd.openssl.mk bsd.port.mk bsd.port.subdir.mk bsd.python.mk bsd.ruby.mk ports/Tools
On 8/4/07, Doug Barton <[EMAIL PROTECTED]> wrote:
> This is nice work, but it seems to require the attached patch. Without
> it I get the following error messages:
>
> "/usr/ports/Mk/bsd.port.mk", line 1092: Could not find /Mk/bsd.commands.mk
> --- bsd.port.mk 4 Aug 2007 11:37:23 - 1.578
> +++ bsd.port.mk 4 Aug 2007 18:46:39 -
> @@ -1089,6 +1089,8 @@
> # Most port authors should not need to understand anything after this point.
> #
>
> +PORTSDIR?= /usr/ports
> +
> .include "${PORTSDIR}/Mk/bsd.commands.mk"
Looks like it's defined in /usr/share/mk/bsd.port.mk
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Jasper - error - jasper-1.900.1_5 has no origin recorded
Gents/Dames-- I am in the middle of performing some updates. I ran into a brick wall. Apparenly, jasper is the offender. Here's the output of pkw_info: jakarta-commons-lang-2.1 Jakarta library with helper utilities for the java.lang API jasper-1.900.1_5??? javavmwrapper-2.3 Wrapper script for various Java Virtual Machines jasper is required by this package: ImageMagick (which was recently updated). pkg_delete: package 'jasper-1.900.1_5' is required by these other packages and may not be deinstalled: ImageMagick-6.2.8.5 Here's a session of trying to update jasper Script started on Fri Aug 3 17:33:48 2007 agora# cd /usr/ports/graphics/jasper && make deinstall ===> Deinstalling for graphics/jasper pkg_info: package jasper-1.900.1_5 has no origin recorded ===> jasper not installed, skipping agora# pkgdb -F ---> Checking the package registry database Missing origin: bsdpan-Convert-yEnc-1.02 -> Ignored. (the package is held; specify -f to force) Missing origin: bsdpan-TermReadKey-2.30 -> Ignored. (the package is held; specify -f to force) Missing origin: jasper-1.900.1_5 Skip this for now? [yes] To skip it without asking in future, please list it in HOLD_PKGS. Stale origin: 'x11/xorg-manpages': perhaps moved or obsoleted. -> The port 'x11/xorg-manpages' was removed on because: "X.org manual pages are now installed with every single port" -> Hint: xorg-manpages-6.9.0 is required by the following package(s): xorg-6.9.0 -> Hint: checking for overwritten files... -> No files installed by xorg-manpages-6.9.0 have been overwritten by other packages. Deinstall xorg-manpages-6.9.0 ? [no] Duplicated origin: multimedia/gstreamer - gstreamer-0.10.11 gstreamer80-0.8.12_2 Unregister any of them? [no] Duplicated origin: x11-fonts/encodings - encodings-1.0.2,1 xorg-fonts-encodings-6.9.0_1 Unregister any of them? [no] Stale dependency: GraphicsMagick-1.1.7 -> libGLU-7.0 (graphics/libGLU): libGL-7.0 (score:35%) ? ([y]es/[n]o/[a]ll) [no] Install stale dependency? ([y]es/[n]o/[a]ll) [yes] [Gathering depends for graphics/libGLU .. done] ---> Installing 'libGLU-7.0' from a port (graphics/libGLU) ---> Building '/usr/ports/graphics/libGLU' ===> Cleaning for libGLU-7.0 ===> Extracting for libGLU-7.0 => MD5 Checksum OK for MesaLib-7.0.tar.bz2. => SHA256 Checksum OK for MesaLib-7.0.tar.bz2. ===> Patching for libGLU-7.0 ===> Applying FreeBSD patches for libGLU-7.0 /bin/cp /usr/ports/graphics/libGLU/files/config /usr/ports/graphics/libGLU/work/Mesa-7.0/configs/current ===> libGLU-7.0 depends on file: /usr/local/libdata/xorg/libraries - not found ===>Verifying install for /usr/local/libdata/xorg/libraries in /usr/ports/x11/xorg-libraries /usr/X11R6 exists, but it is not a symlink. Installation cannot proceed. This looks like an incompletely removed old version of X. In the current version, /usr/X11R6 must be a symlink if it exists at all.Please read /usr/ports/UPDATING (entry of 20070519) for the procedure to upgrade X.org related ports.*** Error code 1 Stop in /usr/ports/x11/xorg-libraries. *** Error code 1 Stop in /usr/ports/graphics/libGLU. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall.16278.0 env make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! graphics/libGLU (unknown build error) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed Command failed [exit code 1]: /usr/local/sbin/portinstall graphics/libGLU agora# cd /usr/ports/graphics/GraphicsMagick/ && make deinstall >& GMERROR agora# cat GMERROR ===> Deinstalling for graphics/GraphicsMagick pkg_info: package jasper-1.900.1_5 has no origin recorded ===> Deinstalling GraphicsMagick-1.1.7 pkg_delete: package jasper-1.900.1_5 has no origin recorded pkg_delete: package jasper-1.900.1_5 has no origin recorded pkg_delete: package jasper-1.900.1_5 has no origin recorded pkg_delete: package jasper-1.900.1_5 has no origin recorded pkg_delete: package jasper-1.900.1_5 has no origin recorded pkg_delete: package jasper-1.900.1_5 has no origin recorded pkg_delete: file '/usr/local/man/man1/GraphicsMagick++-config.1.gz' doesn't exist pkg_delete: file '/usr/local/man/man1/GraphicsMagick-config.1.gz' doesn't exist pkg_delete: file '/usr/local/man/man1/GraphicsMagickWand-config.1.gz' doesn't exist pkg_delete: file '/usr/local/man/man1/gm.1.gz' doesn't exist pkg_delete: file '/usr/local/man/man4/miff.4.gz' doesn't exist pkg_delete: file '/usr/local/man/man5/quantize.5.gz' doesn't exist pkg_delete: file '/usr/local/bin/GraphicsMagick++-config' doesn't exist pkg_delete: file '/usr/local/bin/GraphicsMagick-config' doesn't exist pkg_delete: file '/usr/local/bin/Gr
Out of order line in /usr/ports/MOVED
The following line was placed first in the file, instead of in chronological order. Is there a reason that it needs to be first? Thanks, Doug lang/tcl-tk-wrapper||2007-05-31|Replaced by tcl-wrapper and tk-wrapper -- 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]"
HEADS UP for portmaster users: Mandatory upgrade
Howdy, The short version is that the DESTDIR changes that were made to ports/Mk/bsd.port.mk today broke the method that portmaster was using to detect variable PORTSDIR and PKG_DBDIR. It's fixed now, but in order to keep using portmaster you must upgrade. You won't be able to use portmaster to do the upgrade, so you'll have to do it the old fashioned way: pkg_delete portmaster* cd /usr/ports/ports-mgmt/portmaster make clean ; make install After that you should be fine. Regards, Doug Original Message Date: Sun, 5 Aug 2007 05:04:15 + (UTC) dougb 2007-08-05 05:04:15 UTC FreeBSD ports repository Modified files: ports-mgmt/portmaster/files portmaster.sh.in Log: 1. Change to 'make -f/usr/share/mk/bsd.port.mk' in several places due to the DESTDIR changes today. 2. Export pd, pdb, and distdir to avoid having to look them up each time 3. Streamline find_moved() by grepping for lines, and then recursing 4. Further streamline by using variable stripping instead of cut http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/ports-mgmt/portmaster/files/portmaster.sh.in.diff?&r1=1.18&r2=1.19&f=h ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
PORTSDIR use-before-define fix
Previous DESTDIR commits introduced dereferences of ${PORTSDIR} before
it was set (via .include), which broke e.g. portmaster. This diff
shuffles some things around to hopefully restore everything to being
defined before it is used. It also cleans up some stale cruft. It
has only been lightly tested.
Kris
Index: bsd.port.mk
===
RCS file: /home/pcvs/ports/Mk/bsd.port.mk,v
retrieving revision 1.579
diff -u -r1.579 bsd.port.mk
--- bsd.port.mk 4 Aug 2007 19:48:34 - 1.579
+++ bsd.port.mk 5 Aug 2007 05:50:10 -
@@ -1089,6 +1089,17 @@
# Most port authors should not need to understand anything after this point.
#
+# These need to be absolute since we don't know how deep in the ports
+# tree we are and thus can't go relative. They can, of course, be overridden
+# by individual Makefiles or local system make configuration.
+PORTSDIR?= /usr/ports
+LOCALBASE?=/usr/local
+X11BASE?= ${LOCALBASE}
+LINUXBASE?=/compat/linux
+DISTDIR?= ${PORTSDIR}/distfiles
+_DISTDIR?= ${DISTDIR}/${DIST_SUBDIR}
+INDEXDIR?= ${PORTSDIR}
+
.include "${PORTSDIR}/Mk/bsd.commands.mk"
#
@@ -1294,16 +1305,6 @@
PKGNAME= ${PKGNAMEPREFIX}${PORTNAME}${PKGNAMESUFFIX}-${PKGVERSION}
DISTNAME?=
${PORTNAME}-${DISTVERSIONPREFIX}${DISTVERSION:C/:(.)/\1/g}${DISTVERSIONSUFFIX}
-# These need to be absolute since we don't know how deep in the ports
-# tree we are and thus can't go relative. They can, of course, be overridden
-# by individual Makefiles or local system make configuration.
-PORTSDIR?= /usr/ports
-LOCALBASE?=/usr/local
-X11BASE?= ${LOCALBASE}
-LINUXBASE?=/compat/linux
-DISTDIR?= ${PORTSDIR}/distfiles
-_DISTDIR?= ${DISTDIR}/${DIST_SUBDIR}
-INDEXDIR?= ${PORTSDIR}
INDEXFILE?=INDEX-${OSVERSION:C/([0-9]).*/\1/}
DOCSDIR?= ${PREFIX}/share/doc/${PORTNAME}
@@ -2300,7 +2301,6 @@
.undef NO_PACKAGE
.endif
-COMMENTFILE?= ${PKGDIR}/pkg-comment
DESCR?=${PKGDIR}/pkg-descr
PLIST?=${PKGDIR}/pkg-plist
PKGINSTALL?= ${PKGDIR}/pkg-install
Index: bsd.port.subdir.mk
===
RCS file: /home/pcvs/ports/Mk/bsd.port.subdir.mk,v
retrieving revision 1.71
diff -u -r1.71 bsd.port.subdir.mk
--- bsd.port.subdir.mk 4 Aug 2007 11:37:24 - 1.71
+++ bsd.port.subdir.mk 5 Aug 2007 05:50:10 -
@@ -40,6 +40,21 @@
# Search for ports using either 'make search key='
# or 'make search name='.
+PORTSDIR?= /usr/ports
+TEMPLATES?=${PORTSDIR}/Templates
+.if defined(PORTSTOP)
+README=${TEMPLATES}/README.top
+.else
+README=${TEMPLATES}/README.category
+.endif
+MOVEDDIR?= ${PORTSDIR}
+MOVEDFILE?=MOVED
+
+# XXX Are these needed here? DESCR was set wrong for a few years
+MASTERDIR?= ${.CURDIR}
+PKGDIR?= ${MASTERDIR}
+DESCR?=${PKGDIR}/pkg-descr
+
.include "${PORTSDIR}/Mk/bsd.commands.mk"
.MAIN: all
@@ -66,6 +81,9 @@
.endif
.endif
+INDEXDIR?= ${PORTSDIR}
+INDEXFILE?=INDEX-${OSVERSION:C/([0-9]).*/\1/}
+
UID!= ${ID} -u
.if exists(${LOCALBASE}/sbin/pkg_info)
PKG_INFO?= ${LOCALBASE}/sbin/pkg_info
@@ -249,28 +267,6 @@
@${MAKE} README.html
.endif
-.if (${OPSYS} == "NetBSD")
-PORTSDIR ?= /usr/opt
-.else
-PORTSDIR ?= /usr/ports
-.endif
-TEMPLATES ?= ${PORTSDIR}/Templates
-.if defined(PORTSTOP)
-README=${TEMPLATES}/README.top
-.else
-README=${TEMPLATES}/README.category
-.endif
-COMMENTFILE?= ${.CURDIR}/pkg/COMMENT
-DESCR?=${.CURDIR}/pkg/DESCR
-INDEXDIR?= ${PORTSDIR}
-.if ${OSVERSION} >= 500036
-INDEXFILE?=INDEX-${OSVERSION:C/([0-9]).*/\1/}
-.else
-INDEXFILE?=INDEX
-.endif
-MOVEDDIR?= ${PORTSDIR}
-MOVEDFILE?=MOVED
-
HTMLIFY= ${SED} -e 's/&/\&/g' -e 's/>/\>/g' -e 's/ [EMAIL PROTECTED]
.else
-.if exists(${COMMENTFILE})
- @${HTMLIFY} ${COMMENTFILE} > [EMAIL PROTECTED]
-.else
@> [EMAIL PROTECTED]
.endif
.endif
@@ -415,7 +408,7 @@
break; \
}\
} \
- if (toprint == 1 ) disp[fields[d[i]]] = 1; \
+ if (toprint == 1 ) disp[fields[d[i]]] = 1; \
} \
} \
{ \
pgpFpeJxO73nc.pgp
Description: PGP signature
