- Feel free to populate bsd.licenses.db.mk and adjust the variables:
NO_LICENSES_INSTALL and NO_LICENSES_DIALOGS (default to off).
- For more information see http://wiki.freebsd.org/PortsLicenseInfrastructure
Reviewed by: erwin
9-CURRENT introduced unzip command to the base system. Unfortunately it is
not fully compatible with the archivers/unzip implementation and non-trivial
amount of ports fail to build when using it. Thus we will keep using
archivers/unzip for unzipping source in Ports Collection until someone
volunteer to fix all individual ports. Two most common problems with base
unzip are:
* extracting files without +x flag (some ports rely to execute unzipped
configure scripts, for example)
* different semantics of CR/LF conversion
Error logs of failed port builds with in-base unzip can be made available on
request to portmgr@.
With hat: portmgr
PR: ports/136065 ports/127469
Submitted by: N.J. Mann <njm@njm.me.uk> and Aldis Berjoza <killasmurf86@gmail.com>
- Early identify port CONFLICTS
PR: 137855
Submitted by: Piotr Smyrak <smyru@heron.pl>
- Add --no-same-permissions to the EXTRACT_AFTER_ARGS command.
Tijl Coosemans has been reported an issue that when root is extracting from the
tarball, and the tarball contains world writable files
(sysutils/policykit as an example), there is a chance that the files
gets changed by malicious third parties right after the extraction,
which makes it possible to inject code into the package thus compromise
the system.
Submitted by: Tijl Coosemans <tijl@coosemans.org> Xin LI (delphij@)
- Fix some whitespaces
Tested with: exp-run
passed to configure when GNU_CONFIGURE is set. [1]
- Few changes to the new USERS/GROUPS variables (users/groups are created
earlier, so they're available in do-install; creates homedir when
it's not /var/empty or /nonexistent; set login class if specified).
PR: ports/67436 [1]
Submitted by: (hrs, self) [1]
Feature safe: yes
files. Users and groups won't be deleted at deinstall time as we're lacking
a refcount to know if any port is using them.
Also convert a few ports while I'm here.
PR: ports/108514
Submitted by: mm, self
The default is switched for OSVERSION >= 800076 (when the last known
issue was fixed at the base system). From now the default linux
base port is linux_base-f10. Default linux infrastrucure ports
are linux-f10-*.
HEADSUP to current@ is comming.
Exp-run by: portmgr (pav)
modular xorg.
- supply corresponding USE_XORG for all imake-using ports that need it
- USE_IMAKE no longer implies USE_XLIB in absence of USE_XORG
- retire USE_X_PREFIX which is not really used anywhere after the
above change
- a few minor nits like whitespace and SF macro
Tested by: 2 tinderbox runs by pav
Approved by: portmgr (pav)
PR: ports/135083
Submitted by: ed
- Separate MAKE_JOBS_NUMBER from _MAKE_JOBS, so it can be used in
individual ports
PR: ports/134977
Submitted by: David Naylor <naylor.b.david@gmail.com>
the system (typically FreeBSD prior to 6.3). Allows to continue if the write
fails. This should allow us to start using it widely in the ports tree
(please not just yet, wait for a heads-up, in case this change needs to be
backed out.)
passed to the top level vendor Makefile in build stage, where X is number of
CPU cores by default. The whole system is opt-in, ie. ports need to be enabled
individually. There is a global override available for adventurious users.
both current (fc4) and future linux (f8) distributions at one
ports tree.
The patch contains full changes to ports/Mk files and all ports involved.
But only infrastructure is changed. The resulting packages are the same as
before. Hence no need to bump PORTREVISIONs.
The idea was taken from bsd.gnome.mk and others.
More than 130 ports are switched to follow a new linux infrastructure
introduced by changes to bsd.port.mk, bsd.linux-rpm.mk and a new
bsd.linux-apps.mk.
Thanks for all who was involved and helped me with this work.
And help from Alexander Leidinger was incredible.
Other changes are coming. Stay tuned!
PR: ports/132510
Submitted by: bsam (me)
Exp-run by: portmgr (pav)
- Bump PORTREVISION for all ports depending on libglut since the shlib
version number went from 4 to 3.
- Bump PORTREVISION for all ports depending on libXaw as libXaw.so.8 isn't
installed anymore.
- Couple of ports fixes (mostly missing xorg components added to USE_XORG).
Submitted by: pav
- Fix COPYTREE_* macros not to change permissions and ownership on files, that
were already present in the target path
Submitted by: beech
- Add a showconfig-recursive target, which has been in documentation for years
but never implemented
PR: ports/87642, ports/126770
Submitted by: Andy Kosela <andy.kosela@gmail.com>
- Fix ignorelist-verbose target (in preparation for duds.verbose)
PR: ports/127286 (part of)
Submitted by: linimon
- Fix OPTIONS dialog to show up for every previously unconfigured port in the
dependency chain
PR: ports/127554
Submitted by: ale
- Fail, if recursing into a dependency failed to satisfy the dependency object
(only for :install targets)
PR: ports/116601
Submitted by: edwin
following way:
print/ghostscript-gnu -> print/ghostscript7
print/ghostscript-gnu-nox11 -> print/ghostscript7-nox11
print/ghostscript-gnu-commfont -> print/ghostscript7-commfont
print/ghostscript-gpl -> print/ghostscript8
print/ghostscript-gpl-nox11 -> print/ghostscript8-nox11
japanese/ghostscript-gnu-jpnfont -> print/ghostscript7-jpnfont
korean/ghostscript-gnu-korfont -> print/ghostscript7-korfont
* USE_GHOSTSCRIPT now supports a version number which the port
requires. The valid value is "7" or "8". If other value is
specified, value of WITH_GHOSTSCRIPT_VER is used.
* WITH_GHOSTSCRIPT_GNU has been removed in favor of
WITH_GHOSTSCRIPT_VER. The valid value of WITH_GHOSTSCRIPT_VER is
"7" or "8", and the default value is "8".
Approved by: portmgr (pav)
update: if a port version is 2.13, my magic detection treats this port
using the old autoconf. To fix this, change the regex to include the prefix
"autoconf" before the version number 2.13.
Tested by: pointyhat 7-amd64 exp run (by pav)
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)
for FreeBSD. The official KDE 4.1.0 release notes can be found at
http://www.kde.org/announcements/4.1/.
Some note:
* Prefix
KDE4 will be install into a custom prefixes namely ${LOCALBASE}/kde4.
KDE4 and KDE3 can co-exist
* Sound
For sound to work, it is necessary to have dbus and hal enabled
in your system. Please see the respective documentation on how
to enable these.
For more Informations see the HEADS UP at ports@ and kde-freebsd@
or our wiki page http://wiki.freebsd.org/KDE4/Install.
Have fun!
this way from outside already). Unless stripped, later CFLAGS+= assignments
will produce a double-space in CFLAGS string. Sub-configure will reduce it
back to single space and complain that CFLAGS changed underneath it.
Most prominent example of a problem solved by this kludge is the -CURRENT,
where -fno-strict-aliasing is added to every port's CFLAGS.
- Change default OpenLDAP version to 2.4
- Remove OpenLDAP 2.2 support, the port has been gone for some time now
- Add -DDEPRECATED to CFLAGS for all OpenLDAP using ports
PR: ports/123602, ports/124115, ports/125605
Submitted by: delphij, Jens Rehsack <rehsack@web.de>,
Yuri Pankov <yuri.pankov@gmail.com>
- Remove USE_GTK, it's no longer used
PR: ports/123528
Submitted by: mezz
- Use PATCH_WRKSRC instead of WRKSRC in do-patch target
PR: ports/124169
Submitted by: Max Brazhnikov <makc@issp.ac.ru>
- Remove USE_XPM, it's been replaced by USE_XORG+=xpm
PR: ports/124506
Submitted by: Alex Kozlov <spam@rm-rf.kiev.ua>
- Minor fixups for bsd.port.mk
PR: ports/122675
Submitted by: linimon
- Remove stale comment about USE_GETOPT_LONG
PR: ports/124521
Submitted by: Alex Kozlov <spam@rm-rf.kiev.ua>
- Correct comment about default fetch arguments
PR: ports/125334
Submitted by: Gary Palmer <freebsd-gnats@in-addr.com>
