Rework the adding of dependancies in Mk/bsd.gstreamer.mk.
Previous when using USE_GSTREAMER[1] it would just add the request modules to BUILD/RUN_DEPENDS. This caused the qa script to complain because the old code didn't implicit depend on the gstreamer1 and gstreamer1-plugins[-bad] ports for the libraries they carried, even if they where present via the plugins! The new code adds implicit depends on these ports so USE_GSTREAMER[1] using ports have all the libraries included.
* The mad mp3 plugin was removed, mpg123 plugin also provides mp3 decoding. Switch over ports that used the gstreamer1 mad plugin.
* gtksink plugin renamed -> gtk
* Hook up the sndio plugin into the framework
* Add some indirect dependacies where needed
* Reorder the plugin list in bsd.gstreamer.mk so only one plugin per line. When changing plugins it doesn't result in multiple lines being changed.
* Remove mentions in bsd.gstreamer.mk of plugins mentions that where removed.
* Depend on libunwind on i386/amd64, GStreamer links to it if it is present.
PR: 220753
Exp-run by: antoine@
Repeat after me: If you change IFS, it will break something unexpected.
The problem is that we use IFS to change read's field separator. This
has the side effect of changing how sh(1) splits all string, including
in command parsing functions.
In this case, unless quoted, the strings are always splitted using IFS.
So changing IFS will change how these strings are splitted, and you end
up having a headache. For example:
$ GID_FILES="foo bar"
$ set -x
$ echo $GID_FILES
+ echo foo bar
foo bar
$ IFS=:
$ GID_FILES="foo bar"
$ set -x
$ echo $GID_FILES
+ echo 'foo bar'
foo bar
In the first case, it runs echo with two arguments, first is foo, second is bar.
In the second case, it runs echo with one argument, 'foo bar'.
To fix this, restrict the time during which IFS changes to only one
command, set, and use positional parameters to extract values.
Reported by: feld
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D11632
On x86 architectures when base compiler doesn't support C++14
USES=compiler prefers Clang. As only lang/gcc* provide C++14 library
outside of base some ports need to define USE_GCC. However, adding it
would require ugly bsd.port.options.mk conditionals thus FAVORITE_COMPILER
was used. As /stable/9 reached EOL we no longer need to support ancient
libstdc++ on x86.
Since ruby detects this if it's installed, and it's more often installed now
due to other deps, and ruby provides no way to not depend on it if it's found,
pull it in as a dependency unconditionally. While here, fix plist for ruby 2.4
with the CAPIDOCS option on, and restore the MAKE_JOBS_UNSAFE flag when using
that build option since it's not fixed like I thought it was.
PR: 219796
Reported by: Grzegorz Junka <list1@gjunka.com>
libdeclarative_qmlwebsockets.so is not installed into ${QT_LIBDIR}, which
causes the dependency logic in bsd.qt.mk to actually do something equivalent to
this instead:
BUILD_DEPENDS+= ${QT_LIBDIR}/${QT_QMLDIR}/QtWebSockets/libdeclarative_qmlwebsockets.so:www/qt5-websockets-qml
RUN_DEPENDS+= ${QT_LIBDIR}/${QT_QMLDIR}/QtWebSockets/libdeclarative_qmlwebsockets.so:www/qt5-websockets-qml
which translates into something like
/usr/local/lib/qt5//usr/local/lib/qt5/qml/QtWebSockets/libdeclarative_qmlwebsockets.so:www/qt5-websockets-qml
which obviously does not exist.
Instead of settin websockets-qml_LIB, set websockets-qml_PATH like we do for
other QML ports, so that our dependency logic does not needlessly prepend
${QT_LIBDIR} there. This fixes devel/qt5's build.
PR: 220045
This splits qt5-websockets into a qt5-websockets port containing the core parts,
and a qt5-websockets-qml port with the QML parts. The QML parts depend on Qt Quick,
so on the GUI parts (and hence X11) while the core parts do not.
PR: 220045
Submitted by: Adriaan de Groot <groot@kde.org>
- Update all ports that currently use a custom definition
- Also add a link to a list of certified copyfree licenses
Approved by: portmgr (mat)
Differential Revision: https://reviews.freebsd.org/D11487
* The MATE DE is now GTK+3 based
* mate-calc has come back.
* New USE_MATE=mixer macro
* Add license
* Review dependancies
* Swich to USES=localbase
* atril/eom options reworked into option helper
Thanks to Eric Turgeon for submitting the bulk of this MATE update.
Obtained from: gnome devel repo
Move `files.pythonhosted.org` mirror to the top
The mirror `pypi.python.org` soon will be replaced with the
new Warehouse [1][2], now it's only serving the old files
and its returning `404 - Not Found` to the new files hosted
[1] https://pypi.org
[2] https://github.com/pypa/warehouse
Approved by: garga (mentor), python (sunpoet)
Differential Revision: https://reviews.freebsd.org/D11420
Using ninja instead of make (1) can lead to significant speed ups while building.
Therefore switch from having the ninja generator opt-in to having it opt-out.
Previously cmake-ports that wanted to use ninja could set
CMAKE_NINJA=yes
now, ports that do not work with ninja can set
cmake:<existing args>,noninja
Note, that needing this should be an exception and most often points to a broken
cmake of the port.
The ports using cmake were modified
* removed USES=gmake, if ninja is used
* removed MAKE_ARGS, if ninja is used
* added the cmake-argument noninja if necessary
PR: 219629
PR: 213331
Exp-run by: antoine
Reviewed by: rakuco
Differential Revision: https://reviews.freebsd.org/D10748
* qtdiag outputs diagnostics on the current Qt installation and can be helpful to find issues.
* qtpluginfo is useful while writing plugins for Qt5/KDE Plasma
Reviewed by: rakuco, mat
Differential Revision: https://reviews.freebsd.org/D11280
If NO_ARCH is set then check that no FreeBSD elf(5) files are in $STAGEDIR.
If an elf(5) file is bundles as part of the package, but is not meant to be
run directly (i.e. the elf(5) file is a payload, and not compiled) then
those files can be added to NO_ARCH_IGNORE to avoid the check from failing,
Changes to ports:
- Ports that have NO_ARCH set, but actually compile files have had NO_ARCH
removed.
- Ports that have elf(5) payloads have had those files added to
NO_ARCH_IGNORE.
- R-cran ports that do not set USES=cran:compiles have NO_ARCH set,
PR: 218976
Reviewed by: antoine, mat
Approved by: portmgr
The port's own USES may note that is only supports certain versions. If it
is attempted to build an unsupported version there's no reason to even
try. Rather than giving a WARNING, actually mark it IGNORE.
Currently this should only impact devel/py3-enum34 which does not support
the default python3 version of 3.6.
With hat: portmgr
For example a option of the "boolean" type only accepts true/false this
option is covered by ${opt}_MESON_TRUE/_FALSE.
Add option helpers ${opt}_MESON_YES/_NO for the "combo" type which
accepts yes and no.
Approved by: portmgr@ (mat@)
Differential Revision: https://reviews.freebsd.org/D11078
libdata/pkgconfig.
Fix ports that where installing the file in the wrong place.
PR: 218067
Submitted by: mat
Exp-run by: antoine
Reviewed by: rene, antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D10129
gold linker from binutils 2.28 may produce duplicate library
symbols, which makes shared libraries created with it not usable
with conventional ld linker.
PR: 218187
Submitted by: amdmi3
A few important changes:
- '.' is no longer in @INC.
- "do" now gives a deprecation warning when it fails to load a file
which it would have loaded had "." been in @INC.
- In regular expression patterns, a literal left brace "{" should be
escaped.
Changes: https://metacpan.org/pod/release/XSAWYERX/perl-5.26.0/pod/perldelta.pod
Sponsored by: Absolight
- Add 102m client and library version
- Add dynamic libmysqlclient dependency (libmariadb)
- Make WARNING and IGNORE messages display the correct port
Reviewed by: mmokhi
Differential Revision: https://reviews.freebsd.org/D10057
it will handle the dependencies on groff by using groff from ports if not
available in base
Reviewed by: swills
Approved by: swills
Differential Revision: https://reviews.freebsd.org/D9084
KDE has moved distfiles for applications 16.12.3 to Attic/ on their mirros.
Reported by: Matthias Apitz <guru@unixarea.de>
Reviewed by: rakuco
Approved by: rakuco (mentor, implicit)
Differential Revision: https://reviews.freebsd.org/D10830
makes ports build by meson respect the current policy regarding pkg-config
files. I picked this solution over hacking meson itself, and potential
breaking more.
Bump graphics/graphene due to this change.
Obtained from: Code copied from ports/218067 by mat@
USES=mono: minor fixes
- save a copy of the nuget package in the packages directory
- force linking of directories, allowing nuget-extract to be rerun
without `make clean`
- fix makenuget: nuget requires an equals to identify the version, not a dash
devel/monodevelop: update to 6.2.1.3
- update nuget packages:
- link older System.Collection.Immutable 1.1.37 to newer 1.3.1 (used
by C# and F# respectively)
- update external github repositories
- allow post-extract target to be run multiple times
- change MonoDevelop.Packaging to use a newer version of
NuGet.Build.Packaging (the older version is no longer fetchable)
- remove patch integrated upstream
- moved `nuget restore` patching from post-patch into a patch file (the
former broke silently)
- ChangeLog:
- https://developer.xamarin.com/releases/studio/xamarin.studio_6.2/xamarin.studio_6.2/
irc/smartirc4net: update to 1.1
- add LICENSE
lang/fsharp: update to 4.1.18
- add test dependency on libgdiplus
- update nuget packages
- update test paths for fsharp assemblies
- update patches to prevent `nuget restore` from running
- ChangeLog:
- Set executable bit correctly on output
- Integrate visualfsharp
- Fix regression on binding redirects for System.Collections.Immutable
- Fix regression in Microsoft.Build.FSharp.targets
- Fix binding redirects for System.Collections.Immutable
- Fix version of library going in %PREFIX/lib/mono/fsharp
- Align fsc task and target file
- Use install layout that includes mono/fsharp
- Fix F# Intereactive on Mono 4.9+
- Update compiler tools
- Updates to FSharp.Core nuget package for F# 4.1
- Fix#656: error FS0193: internal error: No access to the given key
lang/mono: various fixes
- fix linking with lld [1]
- double maximum handle size [2]
- add option to run acceptance tests
- allow for optional bootstrapping of mono via either installed mcs (if
available) or via downloaded "monolite" (default)
- add python and py-pillow as dependencies for bin/mono-heapviz
- add armv6 as a supported architecture (untested)
- switch to github for source code:
- official tarball does not include tests
- patches:
- recognise FreeBSD for AOT suffix
- change mono-heapviz to use pillow instead of PIL
multimedia/banshee: tell portscout to ignore this port
- Portscout was not skipping the 2.9.1 version, and upstream appears to be
quiet for the last few years.
x11-toolkits/gtk-sharp20: update to 2.12.43
- ChangeLog:
- fix compilation on mono-4.8.0 (incorrect use of sizeof())
- correctly set owned=true on custom constructors
PR: 218885 [1]
PR: 200937 [2]
* libGL, libEGL, libglesv2, libglapi, and gbm have been moved into mesa-libs,
graphics/dri has been renamed to mesa-dri, and USE_GL has been adjusted
* mesa-libs has a new WAYLAND option that enables platform support in libEGL
* mesa-dri now depends on graphics/s2tc for compressed texture support [1]
* re-remove obsolete dependency on makedepends [2]
* correct sed fix backported from 17.1 [3]
PR: 218799 (exp-run), 212762 [1], 218552 [2], 218562 [3]
Submitted by: dbn [1], jbeich [2,3]
Reported by: afiskon@devzen.ru [1]
Reviewed by: kwm, johalun0@gmail.com
Approved by: portmgr, swills (mentor)
Differential Revision: https://reviews.freebsd.org/D10448
and consequently many of the USES=compiler flavors use the canonical
version of GCC as defined in Mk/bsd.default-versions.mk as well as
the lang/gcc port
With the "new" setup starting with GCC 5 where I have introduced
lang/gcc5-devel for regular snapshots and lang/gcc5 for releases,
and similarly for GCC 6 and onward, we can now leverage lang/gcc5
(and later) for most of the role that lang/gcc used to play -- and
indeed as of today lang/gcc and lang/gcc5 are nearly identical
short of symlinks for gcc, g++, and gfortran binaries that the
former provides.
So now use lang/gcc5 instead of lang/gcc whenever requested via the
USE_GCC framework directly or indirectly.
This is similar to how the python ports work, for example, and it
allows simplifications in Mk/bsd.gcc.mk and Mk/Uses/fortran.mk and
dropping LANG_GCC_IS from Mk/bsd.default-versions.mk. As a next
step lang/gcc is going to become a "hull" essentially only providing
those symlinks and requiring lang/gcc5 (or whatever has been set as
default in Mk/bsd.default-versions.mk).
* This is mostly based on the work by Adriaan de Groot <groot@kde.org> in our development repo.
PR: 217305
PR: 218539
Submitted by: Adriaan de Groot <groot@kde.org>
Reviewed by: rakuco, mat
Approved by: rakuco (mentor)
Exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D9771
symlinks using install's relative symlinks feature.
If you were going through hoops doing things like this to get relative
symlinks:
${LN} -sf ../lib/some/thing ${STAGEDIR}${PREFIX}/bin
You can now use full paths for both the source and destination:
${RLN} ${STAGEDIR}${PREFIX}/libexec/some/thing ${STAGEDIR}${PREFIX}/bin
One caveat is that the source must exist when this is run, because
install needs to run realpath(1) on it.
Sponsored by: Absolight
Now each files generated are explicit targets depending on the files
This would allow to simply loop over a list of packages for subpackages to
create them.
Remove the code for transition from pkg_install to pkg packages
The latest symlink is now a specific target only defined when needed
Reviewed by: swills
Approved by: portmgr (swills)
Differential Revision: https://reviews.freebsd.org/D10323
This uses will handling building software that uses the meson
build system. Expand the option framework to handle MESON options.
Approved by: portmgr (swills@)
Differential Revision: https://reviews.freebsd.org/D104091
BROKEN/IGNORE for specific OpenSSL flavors.
Convert a few ports as an example.
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D10340
===> Applying FreeBSD patches for firefox-53.0,1
No such line 323 in input file, ignoring
sed: /usr/ports/www/firefox/work/firefox-53.0/media/libcubeb/tests/moz.build: No such fileor directory
*** Error code 1
PR: 218585
Reported by: jrm, Marco Beishuizen
Submitted by: tobik
MFH: 2017Q2 (r438264 followup)
There are two cases:
- The upstream versionning is compatible with our versionning, or using
DISTVERSION's magic leads to a compatible PORTVERSION, use
DISTVERSION. If it is possible to use DISTVERSIONPREFIX and
DISTVERSIONSUFFIX to make it compatible, use them.
- The upstream versionning is not compatible with our versionning, and
DISTVERSION's magic does not lead to a correct PORTVERSION, then set
PORTVERSION to the equivalent of our versionning, and set DISTNAME.
It is possible to use a third variable where you store upstream's
version and use it to compute PORTVERSION and/or DISTNAME, like the
dns/bind9* ports do.
Sponsored by: Absolight
More candidates are likely to come before the official announcement (aka
the rush hour) scheduled on 2017-04-19. This one intended to pick up upstream
security fixes earlier while looking for downstream regressions.
Changes: https://www.mozilla.org/firefox/53.0/releasenotes/
Security: 5e0a038a-ca30-416d-a2f5-38cbf5e7df33
MFH: 2017Q2 (piling up)
and `/usr/bin/env python') as invalid, because ports always depend on specific
version of python (e.g. python2 or python3), and generic `python'
which is link to either of them may point to incorrect version or
be not available at all (since it's installed by separate optional
python metaport)
Approved by: portmgr (mat), python (sunpoet)
Differential Revision: D9332
and www. Scripts (with possibly incorrect shebangs) may be located
anywhere in ${PREFIX}, including, for instance, lib/ (multimedia/lives):
Error: '/usr/bin/perl' is an invalid shebang you need USES=shebangfix for 'lib/lives/plugins/effects/rendered/colour_replace'
and ${DATADIR}/ (databases/cego):
Error: '/bin/bash' is an invalid shebang you need USES=shebangfix for 'share/cego/cgbackup'
There may be some more false positives, but broken scripts are much
more severe problem. There's also whitelist mechanism which lets
you ignore shebangs for certain kinds of files (like .pm) which may
be extended to fix FPs
Approved by: portmgr (swills)
Differential Revision: D8923
It is not needed at all.
While here remove:
- the stub pre-everything:: declaration, let the framework define it if needed
- remove the stub describe target with NO_DESCRIBE is set. It is useless
- remove options-message it was only used by gnome and dropped a long time ago
- remove pre-distclean it was never used
Approved by: portmgr (mat)
Differential Revision: https://reviews.freebsd.org/D10326
In order to have subpackages we need in the end do-package to depend on
a target per package that would be created per subpackages
For this we need to decouple the content of do-package so it becomes
a target that only creates the packages.
As a first step use natural make(1) mechanism for a target: if checks first
for the existence of a file and it it does not exists that execute the content
of the target, in that case it creates the PKGREPOSITORY
Bonus it simplifies a bit the code.
While here to avoid testing multiple time for the PACKAGES directory set a
variable after we tested it the first time
PR: 216877
Approved by: portmgr (mat)
Reviewed by: mat
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D9466
We have some hacks in the ports tree to detect or to unconditionally disable
IDEA crypto support. These hacks existed because OpenSSL in FreeBSD 9.3 and
earlier was shipped without IDEA support by default but we were allowed to
enable it via WITH_IDEA src.conf(5) option.
https://www.freebsd.org/cgi/man.cgi?query=src.conf&manpath=FreeBSD+9.3-RELEASE
Therefore, we had to implement some hacks to support three different cases,
i.e., a) 9.3 and earlier without IDEA crypto (default), b) 9.3 and earlier
with IDEA crypto (via WITH_IDEA src.conf option), and c) 10.0 and later with
unconditional IDEA support. Now we can safely remove them because 9.3 and
earlier is no longer supported.
PR: 218233
Exp-Run by: antoine
Approved by: antoine (portmgr)
Despite the name, kf5-oxygen-icons5 does not depend on Qt5 and just contains
the Oxygen icon set without any architecture-dependent files.
As such, we can make all ports depend on it and remove kde4-icons-oxygen
altogether and avoid having two conflicting ports for KDE4 and KF5.
x11-themes/kf5-oxygen-icons5 was adjusted to have its dependencies reduced even
further:
- The dependencies on qt5-core and qt5-testlib were removed, as they were only
needed to build tests.
- We're also passing some CMake arguments to avoid looking for qt5-core
altogether.
With the changes above, the only port kf5-oxygen-icons5 depends on at runtime
is devel/kf5-extra-cmake-modules, which itself does not depend on anything
else.
Reviewed by: tcberner
Differential Revision: https://reviews.freebsd.org/D10237
Collection (requested by USE_GCC=yes and various USES=compiler
invocations) from GCC 4.9.4 to GCC 5.4.
files/patch-arm-support and files/patch-gcc_system.h have become
obsolete. New patches files/patch-arm-unwind-cxx-support and
files/patch-libc++ help support arm targets and new libc++ in base.
ONLY_FOR_ARCHS now also includes arm.
A new option GRAPHITE_DESC, off by default for now, adds support for
Graphite loop optimizations.
Finally, conflicts with other lang/gcc* ports are adjusted suitably.
In terms of changes for users, this upgrade brings the following:
The default mode for C is now -std=gnu11 instead of -std=gnu89.
New warning options -Wc90-c99-compat and -Wc99-c11-compat may
prove useful on that front.
The C++ front end now has full C++14 language support including
C++14 variable templates, C++14 aggregates with non-static data
member initializers, C++14 extended constexpr, and more.
The Standard C++ Library (libstdc++) has full C++11 support and
experimental full C++14 support. It uses a new ABI by default.
There have been significant improvements to inter-procedural optimizations
and link-time optimization such as One Definition Rule based merging of C++
types as well as register allocation.
OpenMP 4.0 specification offloading features are now supported by the C,
C++, and Fortran compilers. Cilk Plus, an extension to the C and C++
languages to support data and task parallelism, has been added as well.
New warning options -Wswitch-bool, -Wlogical-not-parentheses,
-Wbool-compare and -Wsizeof-array-argument may prove useful as
may new preprocessor directives __has_include, __has_include_next,
and __has_attribute.
GCC can now be built as a shared library for embedding in other processes
(such as interpreters), suitable for Just-In-Time compilation to machine
code. This provides a C API and a C++ wrapper API.
Many code generation improvements for AArch64, ARM, support for
AVX-512{BW,DQ,VL,IFMA,VBMI} and Intel MPX on x86-64, and generally
improvements on many targets.
The Local Register Allocator (LRA) now contains a rematerialization
subpass and is able to reuse the PIC hard register on x86/x86-64 to
improve performance of position independent code.
https://gcc.gnu.org/gcc-5/changes.html has a more extensive set of
changes and https://gcc.gnu.org/gcc-5/porting_to.html has a solid
overview of issue you may encountering porting to this new version.
PR: 216707, 218125
Tested by: antoine (-exp runs)
Supported by: jbeich, tcberner, and others
Drop obsolete patches, add one to fix build, and rename a few patches.
Reviewed by: rakuco, tcberner, mat
Approved by: swills (mentor)
Differential Revision: https://reviews.freebsd.org/D10148
This is the latest stable release, and contains many of the patches we kept in
files/. The exception is patch-mimetypes_kde.xml, which just did not seem
necessary any longer: area51 r8180 mentions it was working around issues in
shared-mime-info, which has since been updated. While here, add several
dependencies that were reported by Poudriere's checks.
Bump PORTREVISION in ports that use %%KDE4_KDELIBS_VERSION%% in pkg-plist.
Reviewed by: tcberner
It is the latest available release. While it is not used by any port at the
moment, ensure it is up-to-date for ports to actually start using it.
Reviewed by: tcberner
* While here, set the MASTER_SITES for the portingAids separately.
* Stop to couple kirigamis' distfiles with kf5 until it's actually a part of it.
PR: 217709
Exp-Run by: antoine
Reviewed by: rakuco
Approved by: rakuco (mentor)
Differential Revision: https://reviews.freebsd.org/D9959
SHAREMODE defaults to 444, and gives us endless grief because one
cannot modify a file that is not writable.
So use _SHAREMODE that is 644, so that we can avoid all those CHMOD +w
in so many Makefiles.
Exp-run: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D7623
As noted in PR 209813, some glib headers include libintl.h and then use
gettext in some macros. Programs that use this API (directly or indirectly)
can end up with calls to gettext and need to be linked with libintl.so.
glib-2.0.pc has -lintl in its Libs too.
PR: 209813
With hat: portmgr
http://mirrors.kernel.org/sourceware/ in MASTER_SITE_GCC and
MASTER_SITE_SOURCEWARE.
The original name sources.redhat.com for sourceware.org has been
deprecated many years ago.
This allows WITH_CCACHE_BUILD to be set and still allow modifying MAKE_ENV/CC,
etc, to achieve using the ccache wrappers located at LOCALBASE/libexec/ccache.
This kind of mechanism is needed to support ccache-memcached which has
many build dependencies. Building a version of that first then allows
building further ports with it without introducing cyclic dependencies.
Poudriere will grow support for using a static version of ccache for this
purpose.
With hat: portmgr
ftp://ftp.funet.fi/pub/mirrors/sourceware.org in MASTER_SITE_GCC and
MASTER_SITE_SOURCEWARE, sourceware.org having replaced sources.redhat.com
as the standard name of that host years ago.
This should not bring any practical change for now; it's really the same.
More candidates are likely to come before the official announcement (aka
the rush hour) scheduled on 2017-03-07. This one intended to pick up upstream
security fixes earlier while looking for downstream regressions.
Changes: https://www.mozilla.org/firefox/52.0/releasenotes/
Security: 96eca031-1313-4daf-9be2-9d6e1c4f1eb5
MFH: 2017Q1 (piling up, requires r431637 + r434531)
* Update Qt5 to 5.7.1
* Move Qt4 binaries to lib/qt4/bin
* Move Qt5 libraries to lib/qt5/lib
By moving the libraries we should finally be able to get rid of the inplace
upgrade bug (see ports bugs 194088, 195105 and 198720): when Qt5's libraries
were lying in /usr/local/lib, which would often get added by pkgconfig to the
linker paths via dependencies, the already installed libraries were linked
against, instead of the ones that were being built. This forced us to make
sure, that -L${WRKSRC}/lib was always coming before -L/usr/local/lib in the
linker flags. With this change this should no longer be the case.
* Rename some ports to match the rest (foo-qtX -> qtX-foo)
* Depend on new port misc/qtchooser [see UPDATING & CHANGES]
There are several new Qt5 ports which all have been created by Marie Loise Nolden
<nolden@kde.org>. Thanks again.
PR: 216797
Exp-Run by: antoine
Reviewed by: rakuco, mat, groot_kde.org
Approved by: rakuco (mentor)
Differential Revision: https://reviews.freebsd.org/D9213
This was causing excessive 'uname -s' executions during Poudriere dependency
calculations. The reasoning is due to HAVE_COMPAT_IA32_KERN having a newline
quoted at the end of it as '\ ' by bmake:
# make -f Mk/bsd.port.mk -V 'HAVE_COMPAT_IA32_KERN=${HAVE_COMPAT_IA32_KERN:Q}' | cat -v
HAVE_COMPAT_IA32_KERN=YES\
This resulted in the following being executed:
export HAVE_COMPAT_IA32_KERN="YES OPSYS=FreeBSD"
With hat: portmgr
The mistake was completely on my part, I somehow connected the dots the
wrong way in my head.
The only exceptions (for now) are archivers/zstd and ports-mgmt/synth
which were already picked up by new volunteers in the mean time.
Tested with a modified sysutils/biosfont in which the :debug option was added,
a file was installed into ${KERN_DEBUGDIR}/${KMODDIR} and that file was added
to pkg-plist.
PR: 216879 (inspired by)
Submitted by: Sergey Kozlov (kozlov.sergey.404@gmail.com)
No longer depend on (KERN_)DEBUGDIR being non-empty to decide whether to
create the empty KERN_DEBUGDIR/KMODDIR directory, instead use a new
argument 'debug' to indicate this.
Add KERN_DEBUGDIR to PLIST_SUB and MAKE_ENV so that the including ports
can use them.
Ports using kmod:debug do need to add @dir entries to their pkg-plist for
now to prevent 'make check-plist' errors, for example for default KMODDDIR:
@dir /%%KERN_DEBUGDIR%%/%%KMODDIR%%
@dir /%%KERN_DEBUGDIR%%/boot
@dir /%%KERN_DEBUGDIR%%
It would indeed be nice to automate this.
PR: 216879
Submitted by: Sergey Kozlov (kozlov.sergey.404@gmail.com)
from ports, remove the symlink dance with libGL/libEGL/libgles and the
nvidia-driver ports.
* Revert libGL/libEGL/libglesv2 ports to normal.
* Rename the conflicting libraries from the nvidia-driver ports with a
-NVIDIA prefix and install a libmap.conf file to map to these versions.
* Remove the special case from Mk/Scripts/qa.sh for libGL and libEGL.
* Sadly the symlink dance between nvidia-driver and xorg-server for glx.so
need to stay, due to xorg-server opening that file with dlopen(3).
Approved by: portmgr@ (mat@ (prio version))
Differential Revision: https://reviews.freebsd.org/D7848
bsd.default-versions.mk can rely on ARCH being defined.
- In bsd.port.mk move inclusion of bsd.default-versions.mk from the
pre-makefile section to the options section so the variables can be used
earlier. Also put the bit of code sitting between the options section and
the pre-makefile section into the options section.
- Remove last few cases where ports set WITH_OPENSSL_PORT. This variable is
handled in bsd.default-versions.mk and some ports were setting it after
including bsd.port.options.mk. After FreeBSD 9 EoL all but a few ports,
and then only when setting non-default options, work without setting that
variable.
PR: 215996
Exp-run by: antoine
Approved by: portmgr (antoine)
a last resort.
- Construct a list of DISTFILES for every architecture (amd64, i386).
Select one list for regular make and all lists for make makesum so linux
ports can have one combined distinfo file.
- Set DIST_SUBDIR?=centos so there's only one copy of common distfiles.
- Use MASTER_SITES and DISTFILES groups so make fetch is a bit smarter.
- Regenerate all distinfo files.
- For linux_base-c6 (just like linux_base-c7 already does) turn bin, lib,
lib64 and sbin into symbolic links to the same directory under usr.
This fixes the problem where some programs/libraries exist under / on
FreeBSD and /usr on Linux or vice versa and then depending on the order
of search paths Linux programs may run/load FreeBSD programs/libraries
and fail.
- Turn usr/share/icons into a symbolic link to LOCALBASE/share/icons so
Linux programs can find desktop theme icons. This eliminates the need
for x11-themes/linux*-hicolor-icon-theme.
- Rename pkg-plist.x86_64 to pkg-plist.amd64.
- Regenerate all pkg-plist files.
- Add @preexec to linux_base pkg-plist that moves existing files in bin,
lib, lib64, sbin and icons to the new destination before the directories
are turned into symbolic links.
- Remove several empty directories from linux_base ports.
- Sweep over all linux ports: use consistent style, remove old CONFLICTS,
remove unused pkg-descr files, add NLS option,...
- Remove old linux arts, esound and openssl-compat ports.
be doing at the time.
When fetching, the code was looking for a distfile in either its
DIST_SUBDIR or the main DISTDIR, which was ok. Until a port
(devel/cargo) moves one of its distfile
(cargo-nightly-x86_64-unknown-freebsd.tar.gz) into a subdirectory.
do-fetch would see the distfile in DISTDIR and say, ok, it's there, and
checksum would not see it in its subdirectory and fail.
1: phabricator's blame mode is really, really, great to unroll history.
PR: 216442
Submitted by: mat
Reported by: Bob Willcox, dhw (on ports)
Exp-run by: antoine
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D9318
Change default GEM_NAME from ${PORTNAME}-${PORTVERSION} to ${DISTNAME} to avoid
unnecessary GEM_NAME setting in ports Makefile
Differential Revision: https://reviews.FreeBSD.org/D9250
PR: 216267
Exp-run by: antoine
packages there are no such packages for 7.3 yet so i386 support has been
marked IGNORE for now.
Change DIST_SUBDIR to just "centos" so distfiles that remain the same
between major versions don't have to be redownloaded.
Remove fmake hacks from linux.mk.
Submitted by: Piotr Kubaj <pkubaj@anongoth.pl>
Sometime, Perl ports names do not map to the modules they provide
easily, and it makes it impossible to check for the existence of those
modules in Perl core.
Sponsored by: Absolight
locale set by the user. Add LANG=C and LC_ALL=C at the beginning of
bsd.port.mk and export them so all commands are executed with the C locale.
LC_ALL=C overrides all other LC_* variables. LANG is used by setlocale(3)
as default value for LC_* variables, so normally it isn't used when LC_ALL
is set, but there's code out there that looks at LANG directly so it's safer
to set it as well. The only commands not captured by this are !=
assignments before any inclusion of bsd.port.*mk.
Introduce USE_LOCALE=<locale> that adds LANG=<locale> and LC_ALL=<locale> to
CONFIGURE_ENV and MAKE_ENV so upstream build systems can be executed with a
different locale (e.g. USE_LOCALE=en_US.UTF-8).
PR: 215882
Exp-run by: antoine
Approved by: portmgr (antoine)
Unfortunately, it's not uncommon for FreeBSD users to not update
their systems timely and thus end up using unsupported FreeBSD
release. These users continue to update ports tree as usual and
expect it to work, either unaware of the release EoL, or not clearly
understanding the consequences, which results in unexpected build
failures, bogus bug reports, attempts to bring back removed legacy
support bits and general discontent.
This change introduces system version check which makes ports refuse
to build anything on unsupported system. This makes users aware of
EoL of their system and makes it clear that no port is guaranteed to
build.
The error message tells how to override the check (by defining
ALLOW_UNSUPPORTED_SYSTEM, in which case it's turned into a simple
warning), additionally stressing that this configurartion is not
supported.
Currently outdated are OSVERSION < 1003000 (pre 10.3-RELEASE) and
1100000 <= OSVERSION < 1100122 (from 11-CURRENT'2013 to 11.0-PRERELEASE)
I expect these to be kept up to date with base system lifetimes,
be updated BEFORE removing any support for outdated release from
the tree and also serve as a reference of which OSVERSION checks
may be removed.
Approved by: portmgr (swills, mat)
Differential Revision: D9210
More candidates are likely to come before the official announcement (aka
the rush hour) scheduled on 2017-01-24. This one intended to pick up upstream
security fixes earlier while looking for downstream regressions.
Changes: https://www.mozilla.org/firefox/51.0/releasenotes/
Security: e60169c4-aa86-46b0-8ae2-0d81f683df09
MFH: 2017Q1 (piling up)
- client and server version 5.7.16-10
- pam-for-mysql: compatible with newer MySQL API (MySQL 5.7+)
Thanks to all who have worked on Percona, MariaDB, and MySQL ports. Your
tireless efforts have been instrumental in making this port happen.
Differential Revision: https://reviews.freebsd.org/D8785
- Add PYTHON_PYOEXTENSION and PYTHON_SUFFIX
- Add PYTHON2 and PYTHON3
- Respect PYTHON_VERSION
- Rename PYOEXTENSION to PYTHON_PYOEXTENSION
This change would help:
- Build databases/postgresql*-plpython with Python 3
(It has PLIST issue since bsd.python.mk to Uses/python.mk transition)
- Simplify Makefile
PR: 205807
Differential Revision: https://reviews.FreeBSD.org/D4758
Exp-run by: antoine
This is a development snapshot of upcoming MySQL 8.0.
PR: 215738
Submitted by: Mahdi Mokhtari <mokhi64@gmail.com>
Reviewed by: matthew, feld
Approved by: matthew (mentor), feld
Differential Revision: https://reviews.freebsd.org/D9031
- us.pear.php.net - dead, domain name does not resolve
- de.pear.php.net - not updated, does not contain new packages, creates problems for repackaged modules (see ports/208532)
Approved by: portmgr (mat)
Differential Revision: D8913
- Minimize the differences with editors/emacs.
- Do not require GCC to work around a clang bug. The OS versions for
which this was relevant are no longer supported.
- The check for X11 is handled with the X11 option and _IMPLIES, so
remove the redundant .if logic.
Approved by: swills (mentor) asish (maintainer)
Differential Revision: https://reviews.freebsd.org/D8796
