Date: Tue, 17 Jan 2017 21:15:47 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 216193] sysutils/py-iocage, sysutils/iocage, sysutils/iocage-devel naming and confliction. Message-ID: <bug-216193-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216193 Bug ID: 216193 Summary: sysutils/py-iocage, sysutils/iocage, sysutils/iocage-devel naming and confliction. Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: kmoore@FreeBSD.org Reporter: brandon.freebsd@gmail.com Assignee: kmoore@FreeBSD.org Flags: maintainer-feedback?(kmoore@FreeBSD.org) Hello! I'm the author of iocage, and we recently did a rewrite. The ports have a couple issues: 1 - All 3 ports need to conflict with each other. They are not intended to = be running at the same time. 2 - The sysutils/iocage port needs to be renamed to iocage_legacy, not simp= ly point at that repo. We want it crystal clear the supported status. If that's not possible, removing the port is fine as well, it really doesn't have a future from us. 3 - sysutils/py-iocage is currently in /usr/local/bin. It should be in /usr/local/sbin as it is an administration tool, just as the current sysutils/iocage is located. Thanks! - Brandon --=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-216193-13>