for maintainers:
it introduces 3 different types of options: simple, multi and single:
- simple options are the same as the current options (i.e. on or off.)
- multi options are options where at least one must be set (1-N).
- single options are options where one and only one must be set (exclusive
options).
for users:
- OPTIONS_SET: globally enable some options
- OPTIONS_UNSET: globally disable some options
- ${UNIQUENAME}_SET: enable per-port choice of options
- ${UNIQUENAME}_UNSET: disable per-port choice of options
For compatibility the old OPTIONS framework is now working on top of the new one
The options previously set with old OPTIONS are imported and converted
transparently.
A new knob NO_DIALOG if defined in the the config-conditional target is ignored
(prevent the dialog(1) ui to show up.
Thanks to all people involved:
beat@, crees@, Bryan Drewery, linimon@, novel@ and others, for testing, comments, patches
check for vulnerabilities, but call portaudit instead.
This fixes a remote command execution vulnerability for users who have
portaudit installed.
While changing the code anyway, remove the annoying and very verbose
"Vulnerability check disabled, database not found" warning.
Security: Remote code execution
Security: http://vuxml.FreeBSD.org/6d329b64-6bbb-11e1-9166-001e4f0fb9b1.html
Approved by: portmgr
Feature safe: yes (or at least approved)
With hat: so
if you want to use it please define WITH_PKGNG=yes in your /etc/make.conf
For more information read the announcement on the mailing list
With hat: portmgr
Non-Regression test: linimon
- Add a new flag WITHOUT_FBSD10_FIX for maintainer testing
Some additional notes:
We are planing to make 10 exp-run after the 9.0 Release within 2 weeks to poke maintainers
and upstream as to ensure that for the 10.0 Release, everything is fixed and we can remove
the current workaround.
Submitted by: bf@, rea@ (based on)
Thanks to: beat, kwm, dough
Reviewed by: erwin
Tested via PH: 2x exp-run
Approved by: portmgr (myself)
Ports that need this can set WITH_FBSD10_FIX to apply the hack, but
only on FreeBSD 10. This is only a temporary workaround as the real fix
lies upstream by fixing the included scripts, but this will take a
long time.
Submitted by: ed, jilles, stas, beat (and more)
Tested on: pointyhat i386-9-exp and i386-10
got finished correctly in the first place.
Note that this reverts two things in gabor's original bsd.perl.mk rewrite
that were never actually used/tested:
- ability of USE_PERL5 and other variables to specify a version.
- conditional inclusion of bsd.perl.mk based on USE_PERL5 or similar.
What this commit does is to make bsd.perl.mk be _exactly_ the current
code from bsd.port.mk (modulo a few comments).
Work to test the former would be welcome. The problem with the latter
is that multiple attempts over the last N years to test it inevitably
showed INDEX breakage. My own conclusion is that that simply makes the
tree too fragile (and is the reason I kept putting off working on it in
the first place). Others will disagree.
Hopefully this change will make the perl-specific bits in bsd.*.mk easier
to maintain.
While here, fix a bogus comment (CCFLAGS).
Adding to pointy hat collection: linimon
reason is that bsd.fpc.mk was only defining PPNAME for i386 and amd64.
Provide a placeholder and proper IGNORE for tier-2 [1]
- remove obsolete check for /usr/share/mk/bsd.port.options.mk [2]
- add USE_DRUPAL for easy include of Mk/bsd.drupal.mk [3]
PR: ports/155017 [2],
ports/159288 [3]
Submitted by: linimon (discussed with acm),
eadler,
crees
- bsd.port.mk: add INDEX_PORTS, to support INDEX creation for a subset of the ports tree [1]
- bsd.port.mk: call target "install-rc-script" before "post-install" [2]
- [patch] ports/Mk bsd.port.mk order if groups/users are created by package [3]
- [bsd.port.mk] [patch] reaper of the dead: md5 has been in /sbin for a while [4]
- [bsd.port.mk] [patch] remove support for pre 7.x systems (b.*.m) [5]
- [patch] [bsd.port.mk] reaper of the dead: are three variable defintions needed [6]
PR: ports/156575 [1],
ports/139116 [2],
ports/152498 [3],
ports/155983 [4],
ports/155510 [5],
ports/156340 [6]
Submitted by: Florent Thoumie <flz@xbsd.org> [1],
Sergey Skvortsov <skv@freebsd.org> [2],
Olli Hauer <ohauer@FreeBSD.org> [3],
Eitan Adler <lists@eitanadler.com> [4],
Eitan Adler <lists@eitanadler.com> [5],
Eitan Adler <lists@eitanadler.com> [6]
to support future apache versions and the transition to apache22.
Existing and new USE_APACHE* parameters:
USE_APACHE set apache and apxs as build and run dependency
USE_APACHE_BUILD set apache and apxs as build dependency
USE_APACHE_RUN set apache and apxs as run dependency
The following example is representative of all three possible parameters to use:
USE_APACHE= 22 specify exact version
USE_APACHE= 1.3+ specify [min] version, no [max] version
USE_APACHE= 13-22 specify [min]-[max] range
USE_APACHE= -2.2 specify [max] version, no [min] version
Values can be specified with and without "." (dot) between major and minor
version numbers. For example 22 is equal to 2.2
For documentation and full changelist please take a look into
Mk/bsd.apache.mk or http://wiki.freebsd.org/bsd.apache.mk
Commit with hat apache@
PR: ports/156533
Submitted by: ohauer
If a ports is linked against ncurses from base or from the ports, it should then add:
USE_NCURSES=yes
it is also possible to specify the hard dependency on the ports ncurses or one the base one adding the following macros:
WITH_NCURSES_PORT=yes or WITH_NCURSES_BASE=yes
PR: ports/155269
Submitted by: me
Reviwed by: pav@
Approved by: portmgr (pav@)
Exp-run by: portmgr (pav@)
