Date: Mon, 30 Jul 2018 20:06:20 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 230023] [exp-run] Switch to use xorgproto instead of individual proto packages Message-ID: <bug-230023-7788-oB0HOACRZ0@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-230023-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-230023-7788@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=3D230023 --- Comment #16 from Niclas Zeising <zeising@FreeBSD.org> --- Hi! I just realized something. How does pkg handle port renames and so on? The problem is that xorgproto installs the same files as a bunch of old *pr= oto ports, meaning they conflict. The old ports are removed by this patch, but= if I'm not mistaken, they won't be removed from the host system? I guess one way to solve this is to keep the old *proto ports around, but h= ave them not install anything and have nothing depend on them, that way they can co-exist with the xorgproto port, and then be removed by pkg autoremove or similar. After a transition time (such as after the next quarterly branch) they can be removed. Is this a good way, or is there a way to have pkg solve this with or without human input? Perhaps this is not a problem and I'm just overly worried about breaking things, but I thought I'd bring it to the surface before pulling the trigge= r on the change. I just need a little bit of help and advice. Thank you for all help! Regards --=20 Niclas --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230023-7788-oB0HOACRZ0>