Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 18 Dec 2016 15:17:44 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-doc@FreeBSD.org
Subject:   [Bug 214679] "Recommendation" for portmaster and portupgrade needs to be removed
Message-ID:  <bug-214679-9-4DJRTdCgkN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-214679-9@https.bugs.freebsd.org/bugzilla/>
References:  <bug-214679-9@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214679

--- Comment #3 from Baptiste Daroussin <bapt@FreeBSD.org> ---
I'm not portmgr anymore, so I would share what was discussed long ago.

While it is true portmaster and portupgrade are still in ports, none of them
are still in active maintenance. We discussed a lot between portmgr about
removing portmaster/portupgrade from the handbook.

Beside some drawbacks of those tools which yes could be documented as
"pro/cons" for true, no active maintenance is also a problem regarding some
evolution that are planned in the ports tree for very long: subpackages and
alternative/flavours. which will break the design around which portupgrade =
and
portmaster are built: a port is unique via its origin.

portmaster took years to catch up on pkg_install -> pkg transition (portupg=
rade
was a bit faster to catch up due to active maintenance from bdrewery on
portupgrade at the time).

I would vote on removing documentation of both tools in the handbook

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214679-9-4DJRTdCgkN>