* PyQt could not be installed for multiple Python versions at
the same time, as there were conflicting files.
This patch creates Python-version versioned directories for
all these, and further installs binaries with a version number.
* Note, there might be some hickups for software that depends on
on of the .so's provided by PyQt5, which might not be found
anymore autmotically, and maybe need some LD-flaggery.
* Update PyQt5 to 5.10.1
* Mark www/py-qt5-webengine broken. It is unforuntately no longer
compatible with the old qt5-webengine-5.9.4 we ship.
PR: 232745
Exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D8714
for orphans, i.e., files in STAGEDIR that are not covered by plist.
This is a follow-up to revision 484628 after which texinfo files are
now installed into ${PREFIX}/share/info. (A file "dir" is then created
and maintained by the tooling.)
Approved by: portmgr (antoine)
After a discussion on the mailing list on moving manpages to
${PREFIX}/share/man for consistency with base where it is
installed in usr/share/man, it appeared the same should happen
to GNU info files which were installed under share in base and
not in ports.
Now texinfo is not in base on any of the supported version of FreeBSD
it is possible to proceed to this move and it is easier to do than
the manpage change.
Other benefit than consistency are less patching: all build tools but
cmake are expecting info files to be under share/info and cmake (patched here)
was having an exception for BSD so the patch makes FreeBSD case less
specific for them
Bump revision of all impacted ports
PR: 232907
exp-run by: antoine
Differential Revision: https://reviews.freebsd.org/D17816
If a port has multiple flavors and one needs to be deprecated,
one can now write
qt4_DEPRECATED= Qt4 has been EOL since december 2015
qt4_EXPIRATION_DATE= 2019-03-15
to let users know that changes are coming.
Approved by: portmgr (rene)
Differential Revision: https://reviews.freebsd.org/D17740
- There was no obvious reason to split these ports, and it makes
porting simpler; the set of ports using either mostly coincided.
Exp-run by: antoine
PR: 223687
PR: 232751
Simplify some ports where DragonFlyBSD no longer needs to be special-cased.
Submitted by: rene
Reviewed by: bapt, jbeich
Differential Revision: https://reviews.freebsd.org/D17724
PostgreSQL 11, the latest version of the world’s most advanced open
source database.
PostgreSQL 11 provides users with improvements to overall performance of
the database system, with specific enhancements associated with very
large databases and high computational workloads. Further, PostgreSQL 11
makes significant improvements to the table partitioning system, adds
support for stored procedures capable of transaction management,
improves query parallelism and adds parallelized data definition
capabilities, and introduces just-in-time (JIT) compilation for
accelerating the execution of expressions in queries.
"For PostgreSQL 11, our development community focused on adding features
that improve PostgreSQL's ability to manage very large databases," said
Bruce Momjian, a core team member of the PostgreSQL Global Development
Group. "On top of PostgreSQL's proven performance for transactional
workloads, PostgreSQL 11 makes it even easier for developers to run big
data applications at scale."
PostgreSQL benefits from over 20 years of open source development and
has become the preferred open source relational database for developers.
The project continues to receive recognition across the industry, and
has been featured as the "DBMS of the Year 2017" by DB-Engines and in
the SD Times 2018 100.
PostgreSQL 11 is the first major release since PostgreSQL 10 was
released on October 5, 2017. The next update release for PostgreSQL 11
containing bug fixes will be PostgreSQL 11.1, and the next major release
with new features will be PostgreSQL 12.
Release Notes: https://www.postgresql.org/docs/11/static/release-11.html
Notable changes:
- Switch from PCRE to PCRE2
- Many modules now require PCRE2 for building
- graphics/php73-gd: X11 option is no longer default
Changes to Mk/Uses/php.mk approved by ale
Standardizing on one Clang version makes stability more predictable
across supported FreeBSD versions. As a side effect performance may
suffer some improvement. This also makes it easier to enable LTO as
old LLD versions are more buggy.
This resolves a ninja-related issues, corrects passing private args to linker
while building libruby itself (without external LDFLAGS), exports the full
symbols table, and pet 'pkg check -d'. Issues with weechat, vim, facter,
rubygem-hpricot and rubygem-rdiscount should be fixed. See [1] for long story
of hunting and fixing these issues.
Bump PORTREVISIONS accordingly.
PR: 230238 [1], 231361
Submitted by: fuffy
Approved by: fuffy
- libgit2 in ports is nowadays newer than bundled version
- libssh2 was already unbundled until 1.29.0 update
- Unbundle libssh2 for USES=cargo (unused atm)
PR: 231411
Approved by: rust (dumbbell, tobik)
It was initially got from ruby23, but recent ruby releases have some
differences in runtime linking, which was not hit by exp-run, and caused
trouble with some ports (e.g. devel/leatherman, sysutils/facter).
PR: 230238
Submitted by: fluffy
Reported by: freebsd@ptty.com
Approved by: fluffy
- Add missing component entries for KDE Frameworks 5:
- baloo-widgets
- libkcddb
- libcompactdisc
- Remove components from _USE_KDE4_ALL that are defined in
_USE_KDE_BOTH.
Note that baloo (for KDE Frameworks 5) is explicitly defined in the
KDE Frameworks 5 section, and not the common section.
Approved by: adridg (KDE)
- add support for v3 of the nuget API
- switch to using v3 for NUGET [1]
- rewrite makenupkg to avoid full feed list [2]
- change fetch group to allow "+" in package name/version
[1] NUGET redirects to the source under the v2 API, however this breaks
`makenupkg` as curl fails to follow the redirect when getting the header.
[2] Previously, makenupkg got the complete list of packages (and versions)
a feed. However, for some feeds this takes a very really long time (slow
server response rate). To avoid this, rather check if the package is
available (without downloading it).
Change x11/xorgproto to become a build time dependency when added to
USE_XORG. Change the dependency to be on the port, rather than a file the
port installs.
Fix fallout.
Bump portrevision on depending ports.
PR: 230909
Reviewed by: eadler
Approved by: portmgr (antoine)
Obtained from: https://github.com/FreeBSDDesktop/freebsd-ports/tree/feature/xorgproto
exp-run: antoine
Differential Revision: https://reviews.freebsd.org/D16906
Change USE_GL to become USES=gl. You still need to specify USE_GL as well,
to specify which gl components you need, such as egl glesv2 glut glu glw gl.
Only specifying USE_GL is supported for now, to ease in transition. It is
however deprecated, and will be removed eventually.
Specifying USES=gl without USE_GL is an error.
USE_GL=yes is also deprecated, but supported for now. It implies USE_GL=glu.
Fix fallout from this change.
PR: 230692
Approved by: portmgr (antoine)
exp-run by: antoine
Reviewed by: mat
Differential Revision: https://reviews.freebsd.org/D16774
This will make maintaining ports easier when upstream does not
provide a Cargo.lock on its own.
It uses the crate registry and will output the newest crate versions
available based on the restrictions in Cargo.toml. As such subsequent
runs of `make cargo-crates` might not generate the same output.
Upstream should still be encouraged to provide Cargo.lock if possible.
Requested by: mat
Differential Revision: https://reviews.freebsd.org/D17003
OpenBSD has cdn.openbsd.org officially now which uses cloudflare
and falls back to fastly if its upstream mirror is not available.
Submitted by: T.J. Townsend <tj@openbsd.org>
- People keep adding options named DEBUG to enable verbose things in
their ports and have no idea it also enables WITH_DEBUG.
- We already have WITH_DEBUG_PORTS that can enable WITH_DEBUG on a per
port basis.
Differential Revision: https://reviews.freebsd.org/D16829
cargo.mk is still too eager in splitting a crate's name and version
in two when the name contains a dash followed by a number. For
example with utf-8-0.7.4 the wrong URL ends up being used in
MASTER_SITES
.../utf/8-0.7.4/download/...
instead of
.../utf-8/0.7.4/download/...
PR: 230413
Reported by: Thomas Hurst <tom@hur.st>
GCC, from CFLAGS and CXXFLAGS.
This also establishes a good place where to add any additional such
cases in the future.
PR: 230200
Submitted by: rozhuk.im@gmail.com
Upstream used to distribute protocol headers as separate packages, but has
decided to merge those to a common package, named xorgproto. This update
tracks that change.
* Add a new port, x11/xorgproto, with are protocol headers for xorg.
* Hook the new protocol port to the build and to infrastructure in
bsd.xorg.mk.
* Update all ports with a dependency on any of the old *proto packages to
instead depend on xorgproto. Bump portrevision.
* Delete the old *proto packages, update MOVED.
PR: 230023
Submitted by: zeising
Approved by: portmgr (antoine)
exp-run by: antoine
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
others) from GCC 6 to GCC 7.
PR: 222542
Tested by: antoine (exp-runs)
Approved by: antoine
Thanks to: jbeich, tobik, and others for helping fix (broken) ports
lang/ruby23 is already fixed same way, port it to newer releases
By the way, this unbreak ninja builds with any port relied on libruby.so
PR: 229898
Submitted by: fluffy
Reviewed by: ruby (miwi)
Approved by: ruby (miwi)
Exp-run by: antoine
MFH: 2018Q3
Differential Revision: D16341
- To support amd64, map amd64 to x86_64 when generating the --host argument
to configure in bsd.port.mk and when generating --target arguments in port
Makefiles.
- Add entries to the plists for i386 and amd64. amd64 generally includes both
amd64-specific entries as well as i386 entries.
- Don't include the builtin float.h for i386 and amd64.
Reviewed by: bapt
Approved by: portmgr (bapt)
Differential Revision: https://reviews.freebsd.org/D16250
This fixes PLIST_SUB being too big and PLIST_SUB_SED getting bigger than
_POSIX2_LINE_MAX.
PR: 222355
Reported by: asomers
Reviewed by: asomers, mfechner
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D14014
- remove reference assemblies as a dependency: no longer required
- remove mono-addins as a dependency: shipped internally (via github)
- remove cmake as a dependency: replaced by new build system based on msbuild
- add multiple nuget feeds and move nuget dependencies into separate files
- explicitly set full path to install(1) to fix installation script
- USES=mono: read nupkg name and version from nuspec file
Differential Revision: https://reviews.freebsd.org/D16070
objdump is being removed from HEAD, make sure everything still works
when this happens.
PR: 229049
Reported by: emaste
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D15904
Enhance makenupkg to properly generate nupkg-* files when multiple feeds
provide the same package (but different versions).
Add NUGET_LAYOUT to dictate the layout of the package directory. Sometimes
msbuild (and nuget) does not work with symbolic links and cannot handle the
`legacy` layout.
Starting at ExtUtils::MakeMaker 7.31_06 and Perl 5.27.1, the base
README.pod is no longer installed. So stop installing them altogether.
PR: 229112
Reported by: many
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D15946
Otherwise, when used with BATCH defined so as to not be bothered by
config screen and all, it will almost silently reverse obsolete patches
and make you wonder why something is now broken.
Reviewed by: sbruno
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D15804
From now on, ports that depend on Qt4 will have to set
USES= qt:4
USE_QT= foo bar
ports depending on Qt5 will use
USES= qt:5
USE_QT= foo bar
PR: 229225
Exp-run by: antoine
Reviewed by: mat
Approved by: portmgr (antoine)
Differential Revision: →https://reviews.freebsd.org/D15540
When cross-building a package via a CROSS_SYSROOT, set OSVERSION,
_OSRELEASE, and OSREL to the target OS version. OSVERSION is derived
from the <sys/param.h> header in the sysroot. _OSRELEASE cannot be
easily derived from a sysroot as it is a property of a kernel, so
instead generate a "fake" _OSRELEASE from the OSVERSION, but use a
"-CROSS" branch name that will hopefully fail in any places that make
assumptions about branch names.
Approved by: portmgr (bapt)
Differential Revision: https://reviews.freebsd.org/D15812
make[5]: "/usr/ports/Mk/Uses/gecko.mk" line 48: warning: "/usr/local/bin/firefox --version 2>/dev/null" returned non-zero status
$ sudo firefox --version
Running Nightly as root in a regular user's session is not supported. ($XAUTHORITY is /home/foo/.Xauthority which is owned by foo.)
https://bugzilla.mozilla.org/show_bug.cgi?id=1323302
PR: 229064
Reported by: Vladimir Omelchuk
Analyzed by: Rainer Hurling
Submitted by: Walter Schwarzenfeld (based on)
- Add build/lib dependencies, environment variables to ports using
the backtrace-sys, freetype-sys, gettext-sys, onig_sys,
thrussh-libsodium crates instead of doing this individually for
every port.
- Add a DEV_WARNING when using libc versions < 0.2.37 to prevent
instability of Rust applications on 12.0-CURRENT [1]
- Sort cargo-crates-licenses output
Reviewed by: pizzamig, jbeich [1]
Differential Revision: https://reviews.freebsd.org/D15463
You have a single quoted string containing a backslash followed by a
linefeed (newline). Unlike double quotes or unquoted strings, this has
no special meaning. The string will contain a literal backslash and a
linefeed.
If you wanted to break the line but not add a linefeed to the string,
stop the single quote, break the line, and reopen it.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
Since files and arguments are strings passed the same way, programs
can't properly determine which is which, and rely on dashes to determine
what's what.
A file named -f (touch -- -f) will not be deleted by the problematic
code. It will instead be interpreted as a command line option, and rm
will even report success.
Using ./* will instead cause the glob to be expanded into ./-f, which no
program will treat as an option.
It is not possible to use `-f *` because -f only forces the next
argument to be a directory, a later directory named -delete would mess
things up.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
By default, read will interpret backslashes before spaces and line
feeds, and otherwise strip them. This is rarely expected or desired.
Normally you just want to read data, which is what read -r does. You
should always use -r unless you have a good reason not to.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
It's common to use A && B to run B when A is true, and A || C to run C
when A is false.
However, combining them into A && B || C is not the same as if A then B
else C.
In this case, if A is true but B is false, C will run.
If an if clause is used instead, this problem is avoided.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
When command expansions are unquoted, word splitting and globbing will
occur. This often manifests itself by breaking when filenames contain
spaces.
Trying to fix it by adding quotes or escapes to the data will not work.
Instead, quote the command substitution itself.
If the command substitution outputs multiple pieces of data, use a loop
instead.
Add an exception when using set -- where splitting is intended.
PR: 227109
Submitted by: mat
Exp-run by: antoine
Sponsored by: Absolight
that has been necessary for the GCC 4.x series and should not see any
new usage anways.
Use more current versions of GCC in examples, choosing the two most
realistic options.
Backtick command substitution `STATEMENT` is legacy syntax with several
issues.
- It has a series of undefined behaviors related to quoting in POSIX.
- It imposes a custom escaping mode with surprising results.
- It's exceptionally hard to nest.
$(STATEMENT) command substitution has none of these problems, and is
therefore strongly encouraged.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
In the original code, the return value of mycmd is ignored, and export
will instead always return true. This may prevent conditionals, set -e
and traps from working correctly.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
cd can fail for a variety of reasons: misspelled paths, missing
directories, missing permissions, broken symlinks and more.
If/when it does, the script will keep going and do all its operations in
the wrong directory. This can be messy, especially if the operations
involve creating or deleting a lot of files.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
ShellCheck has noticed that you reference a variable that is not
assigned in the script, which has a name remarkably similar to one that
is explicitly assigned. You should verify that the variable name is
spelled correctly.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
ShellCheck has detected that you have a command that just consists of a
command substitution.
This is typically done in order to try to get the shell to execute a
command, because $(..) does indeed execute commands. However, it's also
replaced by the output of that command.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
export takes a variable name, but shellcheck has noticed that you give
it an expanded variable instead. The problematic code does not export
MYVAR but a variable called foo if any.
Add exception when using indirections where the variable to extract is
actually the value of the variable.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
You have specified multiple patterns in a case statement, where one will
always override the other. The pattern being overridden is indicated
with a SC2222 warning.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
Double quotes around $@ prevents globbing and word splitting of
individual elements, while still expanding to multiple separate
arguments.
Add exceptions when splitting is the intended behavior.
PR: 227109
Submitted by: mat
Sponsored by: Absolight
The behavior when concatenating a string and array is rarely intended.
The preceeding string is prefixed to the first array element, while the
succeeding string is appended to the last one. The middle array elements
are unaffected.
For example, with the parameters foo,bar,baz, "--flag=$@" is equivalent
to the three arguments "--flag=foo" "bar" "baz".
PR: 227109
Submitted by: mat
Sponsored by: Absolight
NEWS: https://www.gnu.org/software/emacs/news/NEWS.26.1
Port changes
- Incorporate latest canna patches submitted by
TAKANO Yuji <takachan@running-dog.net>.
- Remove workarounds for Bug 227799.
- Configure succeeds whether devel/liblockfile is installed or not.
- Customize COMMENT for canna and nox flavors (reported by tobik).
- Remove legacy lldb for gud patch.
- The patch added very little over running lldb on the command line.
Moreover, gud is deprecated. Hopefully a lldb-mi will arrive soon.
Reviewed by: ashish (maintainer)
Differential Revision: https://reviews.freebsd.org/D15044
The work was done by tcberner and myself, with thanks to antoine for the
exp-run.
Not a lot to report compared to other Qt5 updates:
* net/qt5-network is still broken with LibreSSL. I said this in a commit
message ages ago but it bears repeating: upstream is open to adding support
for LibreSSL, but someone needs to step up to maintain it upstream, otherwise
things will continue to be broken all the time.
* www/qt5-webengine is a huge monster that is terrible to update, just like
www/chromium itself is. We (kde@) have decided to keep using the 5.9 series
for the time being, as it should be compatible with the rest of Qt anyway. It
was updated to 5.9.5, the latest 5.9 release at the time of writing.
PR: 228213
"ldconfig -m <path>" so the order of ldconfig search directories after
package installation is the same as after a reboot. The original command
simply appends the path to the list of directories while the ldconfig rc.d
script uses "sort -u".
Bump lang/gcc* which are known to install libraries with exactly the same
name so the library loaded at runtime depends on the order of the search
directories.
PR: 228046
Approved by: portmgr (antoine)
This is leaking LIBDIR information (which is defined in base share/mk/*) to
the build environement with a value which is not really suitable for ports
(/usr/lib) which may have an impact on some build system forcing the maintainer
to override the value.
Revealed during the update of liblz4
PR: 228059
Submitted by: bapt
Exp-run by: antoine
'strip -x', and splitting out debug symbols with objcopy, will leave
a .symtab section but will still remove the .debug_info section. file(1)
shows this distinction as well after the use of 'strip -x':
work/tcl8.7a1/unix/libtcl8.7.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, with debug_info, not stripped
work/stage/usr/local/lib/libtcl8.7.so: ELF 64-bit LSB shared object, x86-64, version 1 (FreeBSD), dynamically linked, not stripped
This fixes false-positives when using install-strip and symbol splitting.
With hat: portmgr
- When cross-building packages, set ARCH to the target arch instead of
the arch of the build host. This fixes bsd.ssp.mk on MIPS which was
trying to enable SSP on MIPS cross-built packages because the host
ARCH was amd64. A new HOST_ARCH variable is added to set the
--build triple for configure scripts, but I believe most other uses of
ARCH in ports are really about the target, not the build host so this
is the more correct general direction.
- Some updates to base/binutils and base/gcc to use ARCH as the target
architecture.
- Drop the extra arguments to GCC to set include and library paths and
only set --sysroot.
- Move the --sysroot flags into CC, CXX, CPP (which is now set to XCPP)
and LD instead of passing it in CFLAGS, etc. The base/gcc build uses
ends up using the CFLAGS when building native binaries for the build
host which fails when tripping over the --sysroot. I think this might
have accidentally worked before because the powerpc64 headers in
/usr/include/machine were "close enough" to the amd64 headers, but with
32-bit MIPS this failed hard.
- Add the GCC MIPS patch from devel/powerpc64-gcc to base/gcc to add
MIPS support to base/gcc.
- Add a MIPS plist for base/binutils.
- Set helper variables for the base/gcc plist to tag architecture-specific
headers (e.g. for intrinsincs) and use these to tag powerpc and MIPS
specific headers.
- Drop the include-fixed headers from base/gcc.
- Strip /usr/local/include from the default list of include paths for
base/gcc.
- Use libc++'s include path for C++ for base/gcc.
Reviewed by: bapt
Approved by: portmgr (bapt)
Differential Revision: https://reviews.freebsd.org/D15267
This is an import of the Plasma5 ports that we have had in the development
repository for quite some time now.
Please note:
* Plasma5 cannot be installed at the same time as KDE SC4.
* Qt5 assumes /etc/localtime to be a symlink to a tz file, not a regular file.
* To start plasma5, it is recommended to use something like
exec ck-launch-session startkde
* Powermanagement and such is not working :-)
I would like to thank all the people that have helped test it in the past years.
Reviewed by: adridg
Differential Revision: https://reviews.freebsd.org/D15096
Rationale:
- MPLAYERHQ was an alias for www[1-5].mplayerhq.hu
- www.mplayerhq.hu uses dns load balancing already
for a while, essentially rendering the above
alias futile
- At times, some of the www[1-9] instances do not
participate in the balancing while others do.
(At the time of this writing, for instance www3
does not have a dns record but www8 does. The
latter was not part of MASTER_SITE_MPLAYERHQ)
- The MPLAYERHQ alias was only used by two ports
in the tree:
multimedia/mplayer-skins
multimedia/win32-codecs
If you use the archive URL directly, you end up having non unique
distfiles named 0.9.5.tar.gz or v2.2.2.tar.gz, and soon, another port
ends up having the same version, and boom.
Reviewed by: bdrewery
Sponsored by: Absolight
Differential Revision: https://reviews.freebsd.org/D15039
* deskutils/akonadi-calendar-tools
* deskutils/akonadi-import-wizard
* deskutils/akonadiconsole
* deskutils/akregator
* deskutils/grantlee-editor
* deskutils/kaddressbook
* deskutils/kalarm
* deskutils/kcharselect
* deskutils/kdepim-addons
* deskutils/kdepim-runtime
* deskutils/keditbookmarks
* deskutils/kfind
* deskutils/kmail
* deskutils/kmail-account-wizard
* deskutils/knotes
* deskutils/kontact
* deskutils/korganizer
* deskutils/kruler
* deskutils/mbox-importer
* deskutils/pim-data-exporter
* deskutils/pim-sieve-editor
This is the current version of KDE Applications <foo>.
Note that users of KDE SC4 should stick with <foo>-kde4.
This adds a slew of KDE Pim related ports and some of their dependencies.
Note, that KDE Pim has a history of working poorly on FreeBSD.
* deskutils/grantleetheme
* deskutils/kdepim
* deskutils/kdepim-apps-libs
* deskutils/libkdepim
* net/akonadi-calendar
* net/akonadi-contacts
* net/akonadi-mime
* net/akonadi-notes
* net/akonadi-search
* net/calendarsupport
* net/eventviews
* net/incidenceeditor
* net/kalarmcal
* net/kblog
* net/kcalcore
* net/kcalutils
* net/kcontacts
* net/kdav
* net/kdenetwork-filesharing
* net/kget
* net/kidentitymanagement
* net/kimap
* net/kldap
* net/kmailtransport
* net/kmbox
* net/kmime
* net/kontactinterface
* net/kpimtextedit
* net/krdc
* net/krfb
* net/ksmtp
* net/ktnef
* net/libgravatar
* net/libkgapi
* net/libksieve
* net/mailcommon
* net/mailimporter
* net/messagelib
* net/pimcommon
* net/zeroconf-ioslave
* security/libkleo
This is the current version of KDE Applications <foo>.
Note that users of KDE SC4 should stick with <foo>-kde4.
This adds a slew of KDE Pim related ports and some of their dependencies.
Note, that KDE Pim has a history of working poorly on FreeBSD.
This is the current version of KDE Applications <foo>.
Note that users of KDE SC4 should stick with <foo>-kde4.
This one is a bit ugly: move libktorrent and ktorrent-kde4 out of the way and
readd the new ones in one go, to not have to touch the same MOVED lines in a
short time span.
Also this adds a very stripped down version of the desktuils/kdepim metaport,
which will get more and more dependencies added shortly.
This is the current version of KDE Applications <foo>.
Note that users of KDE SC4 should stick with <foo>-kde4.
Differential Revision: https://reviews.freebsd.org/D14823
This is the current version of KDE Applications <foo>.
Note that users of KDE SC4 should stick with <foo>-kde4.
Differential Revision: https://reviews.freebsd.org/D14832
* graphics/gwenview
* graphics/kamera
* graphics/kcolorchooser
* graphics/kdegraphics-mobipocket
* graphics/kdegraphics-svgpart
* graphics/kdegraphics-thumbnailers
* graphics/kimagemapeditor
* graphics/kolourpaint
* graphics/libkdcraw
* graphics/libkexiv2
* graphics/libkipi
* graphics/libksane
* graphics/okular
* graphics/spectacle
This is the current version of KDE Applications <foo>.
Note that users of KDE SC4 should stick with <foo>-kde4.
Differential Revision: https://reviews.freebsd.org/D14833
For ports that specify CATEGORIES=kde-applications, automatically add documentation to the plist.
Differential Revision: https://reviews.freebsd.org/D14821
For the qt5-* ports bsd.qt.mk sets EXTRACT_AFTER_ARGS, and
thereby does not get the normal default value of
--no-same-owner --no-same-permissions
passed when extracting. This lead to for example header files
being installed (i.e. copied), with permissions group write
permissions.
Manually append that to the bsd.qt.mk shenanigans (also do the
same in www/qt5-webchannel, which opts out of the bsd.qt.mk value)
PR: 227027
Reported by: grarpamp@gmail.com
Some ports do not honour $LD or -fuse-ld=bfd in $CFLAGS, but do invoke
ld via $PATH. Automatically set BINARY_ALIAS+=ld=${LD} when LLD_UNSAFE
is active to use ld.bfd for these ports.
Approved by: portmgr (antoine)
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D14876
It has been a while both does not depend anymore on esound, before this change
esound dependency was wrongly added to plenty of packages which actually does
not depend on it.
While here:
- audio/glame: remove esound support
- games/monkeybubble: add an explicit dependency on esound
- sysutils/gnome-schedule: add en explicit dependency on pkg-config
- comms/kb: add missing dependency on pkgconfig
- x11-toolkits/libgnomeui:
* update to 2.4.5
* use USES=localbase
