Date: Fri, 24 Aug 2018 16:58:07 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 230837] x11-servers/xorg-server: make install fails for xorg-server-1.18.4_9,1 Message-ID: <bug-230837-7141-jKbD3EnzOy@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230837-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-230837-7141@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=3D230837 --- Comment #6 from rkoberman@gmail.com --- (In reply to Adrian Bocaniciu from comment #4) I already understood the general cause of your problem. That is why I point= ed you to the UPDATING entry. While it is now too late to undo the damage, the real issue was that the pkg delete command, by default, will delete the specified package AND ALL PORTS THAT DEPEND ON IT. I think that this is a p= oor default, but it does often make sense and you are given a list of what will= be removed with the chance to reject it. In the case where you are deleting a package and plnning on immediately installing a replacement, the '-f' option is appropriate and is used in the UPDATING entry. When '-f' is specified, only the specified package or packa= ges will be delete with packages dependent on it or them left alone. I do believe UPDATING is newer than the ports you describe. It is /usr/ports/UPDATING and provides information on cases, like the consolidati= on of the various Xorg proto ports, where special actions need to be taken. Wh= en the updating for ports fails, always look there first. I also would suggest using packages instead of building ports unless there = is a good reason to do so. Unless you have customized ports in your ports tree (= not custom options, but cases where there are private ports added or you have m= ade edits of you own to ports, think about switching to portsnap to keep your p= orts tree current. --=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-230837-7141-jKbD3EnzOy>