[Bug 191750] archivers/xz -> 5.0.5, MAINTAINERSHIP, MIRROR
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Jul 26 20:11:45 UTC 2014
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191750
--- Comment #5 from jharris at widomaker.com ---
Steve, sorry if my wisecrack offended you; it was only meant to make everyone
reading it question the status quo.
Specifically, the repochurn from ports/archivers/xz's removal means I can't
easily see, via "svn log" (in a resurrected version), when the port was
deleted. I had to 'svn annotate' ports/MOVED, assume the commits to the port
and ports/MOVED were done at the same time - not always the case, and do some
more hunting to get the port back in my tree.
In the future, if absolutely needed to prevent a hard collision between ports
and BASE, it would be cleaner to use IGNORE (e.g., 9.2-RELEASE, until
EoL/2015):
%make
===> xz-5.0.5 may conflict with "xz (XZ Utils) 5.0.4" in the base system.
This would prevent further churn caused by creating a -devel port, waiting for
all supported FreeBSD base trees to catch up, probably deleting the -devel port
if it stagnates for a while, and, if so, perhaps losing its easily-found
history (svn log).
Thanks.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list