opensourcemirror
/
opnsense-ports
mirror of https://github.com/opnsense/ports.git
1
0
Fork 0
Code Issues Releases Wiki Activity

Framework: sync with upstream 

Taken from: HardenedBSD
This commit is contained in:
Franco Fichtner 2019-03-01 06:50:08 +01:00
parent 6981345428
commit 1facc4f170
5 changed files with 4 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
CHANGES
View File

@ -282,7 +282,6 @@ AUTHOR: kde@FreeBSD.org
to to
USES=cmake:<args>,noninja USES=cmake:<args>,noninja
20170417: 20170417:
AUTHOR: kwm@FreeBSD.org AUTHOR: kwm@FreeBSD.org
@ -1882,7 +1881,6 @@ AUTHOR: makc@FreeBSD.org
In-source build (equivalent to plain USE_CMAKE=yes) can be used if In-source build (equivalent to plain USE_CMAKE=yes) can be used if
project doesn't support out-of-source build. project doesn't support out-of-source build.
20130319: 20130319:
AUTHOR: bapt@FreeBSD.org AUTHOR: bapt@FreeBSD.org
@ -2806,7 +2804,6 @@ AUTHOR: edwin@FreeBSD.org
Use "make -V MASTER_SITES" to see the differences. Use "make -V MASTER_SITES" to see the differences.
20050313: 20050313:
AUTHOR: ahze@FreeBSD.org, kwm@FreeBSD.org AUTHOR: ahze@FreeBSD.org, kwm@FreeBSD.org
The following changes were committed: The following changes were committed:
@ -3416,7 +3413,6 @@ AUTHOR: gnome@FreeBSD.org
Hopefully galeon2 can catch up to peoples' expectations from Hopefully galeon2 can catch up to peoples' expectations from
galeon1 soon, and we can remove the GTK1 ports altogether. galeon1 soon, and we can remove the GTK1 ports altogether.
20040204: 20040204:
AUTHOR: portmgr@FreeBSD.org AUTHOR: portmgr@FreeBSD.org
The bsd.php.mk file has been moved out of the lang/php4 port The bsd.php.mk file has been moved out of the lang/php4 port

1
MOVED
View File

@ -11644,3 +11644,4 @@ net/ceph|net/ceph12|2019-02-27|Make room for other ceph versions
devel/rubygem-grape0|devel/rubygem-grape|2019-02-28|Has expired: Use devel/rubygem-grape instead devel/rubygem-grape0|devel/rubygem-grape|2019-02-28|Has expired: Use devel/rubygem-grape instead
www/rubygem-jwt1|www/rubygem-jwt|2019-02-28|Has expired: Use www/rubygem-jwt instead www/rubygem-jwt1|www/rubygem-jwt|2019-02-28|Has expired: Use www/rubygem-jwt instead
www/rubygem-rack-cors0|www/rubygem-rack-cors|2019-02-28|Has expired: Use www/rubygem-rack-cors instead www/rubygem-rack-cors0|www/rubygem-rack-cors|2019-02-28|Has expired: Use www/rubygem-rack-cors instead
databases/py-sqlparse01|databases/py-sqlparse020|2019-02-28|Removed: Use databases/py-sqlparse020, if you need sqlparse for py-twext

2
Mk/bsd.sites.mk
View File

@ -365,7 +365,7 @@ DEV_WARNING+= "MASTER_SITES contains ${MASTER_SITES:M*/github.com/*/archive/*},
# GH_TAGNAME - name of the tag to download (2.0.1, hash, ...) # GH_TAGNAME - name of the tag to download (2.0.1, hash, ...)
# Using the name of a branch here is incorrect. It is # Using the name of a branch here is incorrect. It is
# possible to do GH_TAGNAME= GIT_HASH to do a snapshot. # possible to do GH_TAGNAME= GIT_HASH to do a snapshot.
# default: ${DISTVERSION} # default: ${DISTVERSIONFULL}
# #
# GH_SUBDIR - directory relative to WRKSRC where to move this distfile's # GH_SUBDIR - directory relative to WRKSRC where to move this distfile's
# content after extracting. # content after extracting.

2
README
View File

@ -16,7 +16,6 @@ These will explain how to use ports and packages.
If you would like to search for a port, you can do so easily by If you would like to search for a port, you can do so easily by
saying (in /usr/ports): saying (in /usr/ports):
make search name="<name>" make search name="<name>"
or: or:
make search key="<keyword>" make search key="<keyword>"
@ -37,4 +36,3 @@ and the individual ports will also use up lots of space in their work
subdirectories unless you remember to "make clean" after you're done subdirectories unless you remember to "make clean" after you're done
building a given port. /usr/ports/distfiles can also be periodically building a given port. /usr/ports/distfiles can also be periodically
cleaned without ill-effect. cleaned without ill-effect.

11
UPDATING
View File

@ -111,9 +111,9 @@ you update your ports collection, before attempting any port upgrades.
in the FreeBSD ports tree. It will also replace the previous 2.18 LTR in the FreeBSD ports tree. It will also replace the previous 2.18 LTR
in the QGIS package repositories in February 2019 [1]. in the QGIS package repositories in February 2019 [1].
Beside, the latest QT4 version 4.8.7 has been EOL since December 2015 Beside, the latest Qt4 version 4.8.7 has been EOL since December 2015
and its expiration date on FreeBSD is set to March, 15th 2019. and its expiration date on FreeBSD is set to March, 15th 2019.
Because QGIS 2 is based on QT4 and Python2, it was decided to not create Because QGIS 2 is based on Qt4 and Python2, it was decided to not create
a legacy port for QGIS 2, after graphics/qgis changed to QGIS 3. a legacy port for QGIS 2, after graphics/qgis changed to QGIS 3.
For users moving over from the 2.18 LTR there is a huge list of new For users moving over from the 2.18 LTR there is a huge list of new
@ -123,7 +123,6 @@ you update your ports collection, before attempting any port upgrades.
done so, take a look at the changelogs from versions 3.0, 3.2, and done so, take a look at the changelogs from versions 3.0, 3.2, and
3.4 [2][3][4] to understand the full scope of changes in the 3.x release. 3.4 [2][3][4] to understand the full scope of changes in the 3.x release.
[1] https://qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule [1] https://qgis.org/en/site/getinvolved/development/roadmap.html#release-schedule
[2] http://changelog.qgis.org/en/qgis/version/3.0.0/ [2] http://changelog.qgis.org/en/qgis/version/3.0.0/
[3] http://changelog.qgis.org/en/qgis/version/3.2.0/ [3] http://changelog.qgis.org/en/qgis/version/3.2.0/
@ -660,7 +659,6 @@ you update your ports collection, before attempting any port upgrades.
Application key [base64:P62La9V........qw=] set successfully. Application key [base64:P62La9V........qw=] set successfully.
20180901: 20180901:
AFFECTS: users of samba46 AFFECTS: users of samba46
AUTHOR: antoine@FreeBSD.org AUTHOR: antoine@FreeBSD.org
@ -2689,7 +2687,6 @@ you update your ports collection, before attempting any port upgrades.
version of OpenSSL or LibreSSL that supports the AES256 and SHA256 version of OpenSSL or LibreSSL that supports the AES256 and SHA256
algorithms. algorithms.
20170120: 20170120:
AFFECTS: users of databases/mysql56-server AFFECTS: users of databases/mysql56-server
AUTHOR: feld@FreeBSD.org AUTHOR: feld@FreeBSD.org
@ -5708,7 +5705,6 @@ you update your ports collection, before attempting any port upgrades.
This is all that is needed to continue using an existing Fedora 10 Linux base This is all that is needed to continue using an existing Fedora 10 Linux base
and userland. and userland.
20141208: 20141208:
AFFECTS: users of ports-mgmt/poudriere, ports-mgmt/poudriere-devel AFFECTS: users of ports-mgmt/poudriere, ports-mgmt/poudriere-devel
AUTHOR: bdrewery@FreeBSD.org AUTHOR: bdrewery@FreeBSD.org
@ -9422,7 +9418,6 @@ you update your ports collection, before attempting any port upgrades.
or or
# pkg install -fR lang/ghc # pkg install -fR lang/ghc
20121218: 20121218:
AFFECTS: users of icu AFFECTS: users of icu
AUTHOR: bapt@FreeBSD.org AUTHOR: bapt@FreeBSD.org
@ -10461,7 +10456,6 @@ you update your ports collection, before attempting any port upgrades.
or or
# portupgrade -fr lang/ghc # portupgrade -fr lang/ghc
20120531: 20120531:
AFFECTS: users of graphics/png AFFECTS: users of graphics/png
AUTHOR: dinoex@FreeBSD.org AUTHOR: dinoex@FreeBSD.org
@ -12306,7 +12300,6 @@ or
the library with "FETCH" support, this would cause libldap to depend on the library with "FETCH" support, this would cause libldap to depend on
FreeBSD's libfetch.so library. FreeBSD's libfetch.so library.
As of 20110402, a local change have been introduced so OpenLDAP libraries As of 20110402, a local change have been introduced so OpenLDAP libraries
link against libfetch.so when FETCH is enabled. Normally, no further user link against libfetch.so when FETCH is enabled. Normally, no further user
interaction would be required. interaction would be required.