Page MenuHomeFreeBSD
Files F104113161

D14203.id38877.diff
No OneTemporary
Actions

D14203.id38877.diff
View Options

Index: UPDATING
===================================================================
--- UPDATING
+++ UPDATING
@@ -5,6 +5,40 @@
You should get into the habit of checking this file for changes each time
you update your ports collection, before attempting any port upgrades.
+20180205:
+ AFFECTS: users of lang/ruby23
+ AUTHOR: ???
+
+ The default ruby version has been updated from 2.3 to 2.4.
+
+ If you compile your own ports you may keep 2.3 as the default version by
+ adding the following lines to your /etc/make.conf file:
+
+ #
+ # Keep ruby 2.3 as default version
+ #
+ DEFAULT_VERSIONS+=ruby=2.3
+
+ If you wish to update to the new default version, you need to first stop any
+ software that uses ruby. Then, you will need to follow these steps, depending
+ upon how you manage your system.
+
+ If you use pkgng, simply upgrade:
+ # pkg upgrade
+
+ If you use portmaster, install new ruby, then rebuild all ports that depend
+ on ruby:
+ # portmaster -o lang/ruby24 lang/ruby23
+ # portmaster -R -r ruby-2.4
+
+ If you use portupgrade, install new ruby, then rebuild all ports that depend
+ on ruby:
+
+ # pkg delete -f ruby portupgrade
+ # make -C /usr/ports/ports-mgmt/portupgrade install clean
+ # pkg set -o lang/ruby23:lang/ruby24
+ # portupgrade -x ruby-2.4.\* -fr lang/ruby24
+
20180201:
AFFECTS: users of editors/emacs* and all ports using Emacs via USES=emacs
AUTHOR: jrm@FreeBSD.org
@@ -54,9 +88,9 @@
AFFECTS: users of x11-toolkits/kf5-kirigami2 and x11/kf5-plasma-framework
AUTHOR: kde@FreeBSD.org
- Files that were previously installed by kf5-kirigami2 are now installed
+ Files that were previously installed by kf5-kirigami2 are now installed
by kf5-plasma-framework. This can lead to a conflict during the upgrade
- of the packages.
+ of the packages.
It is recommended to first remove the package kf5-kirigami2.
20180115
@@ -135,7 +169,7 @@
AFFECTS: users of net-im/ejabberd
AUTHOR: ashish@FreeBSD.org
- If you are building ejabberd 17.11 on a host, which already has an older
+ If you are building ejabberd 17.11 on a host, which already has an older
version of ejabberd installed, then build process will fail with "unknown type
specifier" errors. As a workaround, please uninstall ejabberd before building
ejabberd.
@@ -360,7 +394,7 @@
20171107:
AFFECTS: users of www/node
- AUTHOR: bhughes@FreeBSD.org
+ AUTHOR: bhughes@FreeBSD.org
The www/node port has been updated to node.js v9.0.0, the latest
upstream release. A new port, www/node8, has been created for the
@@ -410,7 +444,7 @@
AUTHOR: brnrd@FreeBSD.org
The configuration of mod_rpaf2 has been heavily modified since version
- 0.6. Have a look at https://github.com/gnif/mod_rpaf/tree/v0.8.4 to
+ 0.6. Have a look at https://github.com/gnif/mod_rpaf/tree/v0.8.4 to
determine what you need to change in your configuration.
20171031:
@@ -540,7 +574,7 @@
Users should delete the devel/cmake-modules package and then
upgrade or reinstall devel/cmake.
-
+
All ports have been updated to depend only on CMake.
20170904

File Metadata

Mime Type
text/plain
Expires
Wed, Dec 4, 5:30 PM (7 h, 30 s)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
15028190
Default Alt Text
D14203.id38877.diff (3 KB)

Event Timeline