theory, but in practice, things will break if you set them to non-default
values. This allows us to unobfuscate the plist and fix a broken @dirrmtry.
Convert the NO_SHARED option to a proper port option (ZSH_STATIC).
Specifically, newer autoconf (> 2.13) has different semantic of the
configure target. In short, one should use --build=CONFIGURE_TARGET
instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning
and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)
Update csup, portsnap and portlint completion. Add completion for powerd,
freebsd-update, fetch and portaudit (from submitter) as well as zfs and
zpool (from zsh repo).
Bump PORTREVISION.
PR: ports/126457
Submitted by: baptiste.daroussin@gmail.com
script arrived at the correct value for ZSH_NO_XOPEN, but since autoheader
did not run, it did not propagate to config.h. Add autoheader to the
USE_AUTOTOOLS list to correct this.
detection. This fixes the issue on 7-CURRENT where Zsh was manipulating
environment directly in conflict with the new *env() functions:
http://lists.freebsd.org/pipermail/freebsd-current/2007-July/075538.html
6-STABLE continues to works correctly.
More info about the patch:
http://www.zsh.org/mla/workers/2007/msg00619.html
- Fix completions for locate(1), mount(8), umount(8) to avoid some linuxisms
and do the right thing under FreeBSD
PR: ports/115094, ports/115702
Submitted by: Sean C. Farley (scf)
- Pet a bit portlint
- OPTION'ify
- Add PCRE support OPTION off by default
- Add more MASTER_SITES
- Remove ?= from MAINTAINER and COMMENT since there are no more slave ports
- Remove CONFLICTS since conflicting ports doesn't exist anymore
- Fix iconv detection and add USE_ICONV=yes
- Use PORTDOCS and PORTEXAMPLES and cleanup pkg-plist
- Respect NOPORTEXAMPLES
- Add csup, portsnap and portlint Completions, it was already added to zsh cvs
but add it here using a patch while new version don't come
Reviewed by: sergei@
Approved by: sergei@ (maintainer)
FreeBSD 4.x doesn't have wide character support,
so avoid adding --enable-multibyte to CONFIGURE_ARGS on FreeBSD 4.x
PR: ports/96645 [1]
Submitted by: Tod McQuillin <devin@spamcop.net> [1],
Hajimu UMEMOTO <ume@FreeBSD.org> (in private e-mail)
- Enable multibyte character support in Zsh by default [3], [4]
- Added new knob (WITHOUT_ZSH_MULTIBYTE) to disable multibyte support
- Fix zsh.info installation that was previously attempted before "su"
(and thus could fail when running "make install" under a regular user) [2] -
apply a different fix, though - move zsh.info generation from pre-install
to post-build phase
PR: ports/95970 [1], ports/94205 [2]
Submitted by: Martin Wilke <freebsd@unixfreunde.de> [1],
Michael Kuhn <mkuhn.nw@web.de> [2]
umei [3] (in private e-mail),
"J.R. Oldroyd" <jr@opal.com> [4] (in private e-mail)
rzsh(1) is the restricted version of zsh(1), with various things disabled
so as to provide a strictly limited access to the system.
A user with a shell in /etc/shells can use chsh(1) to change their shell,
can use FTP, can use other file-transfer services, etc. Thus, adding rzsh
to /etc/shells could be a security risk in certain configurations.
- zsh-mime-setup is set up to look for /etc/{mime.types,mailcap}.
Neither of them should exist on a stock FreeBSD system.
Teach it to look in ${LOCALBASE}/etc instead. [2]
- Zsh completion doesn't know about bsdtar(1) achievements:
it won't complete to foo.tar.gz if you just enter 'tar xf foo^D'.
Teach zsh completion about this and other formats supported by bsdtar(1).
NOTE: This is only applicable to FreeBSD 5.3-RELEASE or newer,
where bsdtar(1) replaced GNU tar(1) in the base system.
- Bump PORTREVISION
PR: ports/82066 [2], ports/83023 [3]
Submitted by: Phil Pennock <pdp@nl.demon.net> [1]
Ulrich Spoerlein <q@galgenberg.net> [2] [3]
