Date: Mon, 08 Jul 2024 09:45:14 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 280189] sysutils/beadm-devel - beadm(1) possible deprecation? Message-ID: <bug-280189-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D280189 Bug ID: 280189 Summary: sysutils/beadm-devel - beadm(1) possible deprecation? Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: Individual Port(s) Assignee: ports-bugs@FreeBSD.org Reporter: erichanskrs@gmail.com CC: vermaden@interia.pl CC: vermaden@interia.pl Flags: maintainer-feedback?(vermaden@interia.pl) As per bug #254466, comment #20, I'm opening this PR here regarding https://www.freshports.org/sysutils/beadm https://www.freshports.org/sysutils/beadm-devel Also, trying to understand ports management:=20 Who decides when and if a port gets deprecated and removed? What's the use case for not deprecating* https://cgit.freebsd.org/ports/tree/sysutils/beadm-devel and, after an appropriate elapsed time removing it from the ports tree? No more confusion, less maintenance; perhaps I'm missing something here? ---- * The creator and maintainer (Slawomir Wojciech Wojtczak - vermaden) has responded in bug #254466, comment #6; and in bug #254466, comment #14: =E2=80=9CI think that *sysutils/beadm-devel* can be deleted as it was not u= pdated since 3 years ... =E2=80=9D last log entries https://cgit.freebsd.org/ports/log/sysutils/beadm-devel indicate merely managerial changes. There is a current active and maintained version beadm(8) - by the same creator/maintainer: https://www.freshports.org/sysutils/beadm --=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-280189-7788>