Date: Wed, 20 Sep 2023 14:06:43 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 273841] net-p2p/transmission: -utils and -daemon conflict after update to 4.0 Message-ID: <bug-273841-7788-X9xlWaorVZ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-273841-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-273841-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=3D273841 --- Comment #8 from Robert Clausecker <fuz@FreeBSD.org> --- (In reply to Rafe from comment #6) Thank you for the clarification. The point of using a metaport is that it makes things easier for binary pac= kage users. For example, consider something else pulls in transmission as a dependency, but say it only needs the daemon bits, so it depends on net-p2p/transmission@daemon. But you want all the bits and so have net-p2p/transmission@default installed, and suddenly there is a conflict despite you having a dependency that works. A metaport makes it so that when you install net-p2p/transmission@default, = it simply depends on net-p2p/transmission@daemon, meaning that the dependency = can be satisfied. It also means users can easily install or deinstall componen= ts of transmission without having to go through a full install/deinstall. But at the end of the day, it's your decision and I'm fine with it either w= ay. --=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-273841-7788-X9xlWaorVZ>