Bug 280189 - sysutils/beadm-devel - beadm(1) possible deprecation?
Summary: sysutils/beadm-devel - beadm(1) possible deprecation?
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Some People
Assignee: Joel Bodenmann
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-08 09:45 UTC by Eric
Modified: 2024-07-15 14:09 UTC (History)
3 users (show)

See Also:
vermaden: maintainer-feedback+


Attachments
patch (982 bytes, patch)
2024-07-14 14:31 UTC, Joel Bodenmann
jbo: maintainer-approval+
Details | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description Eric 2024-07-08 09:45:14 UTC
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: 
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:
“I think that *sysutils/beadm-devel* can be deleted as it was not updated since 3 years ...
”
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
Comment 1 Slawomir Wojciech Wojtczak 2024-07-08 09:51:43 UTC
I did not touched 'beadm-devel' for years and 'beadm' is mostly complete and bug free.

IMHO we should deprecation/remove 'beadm-devel' port.

Regards,
ver
Comment 2 Eric 2024-07-08 11:16:34 UTC
(In reply to Slawomir Wojciech Wojtczak from comment #1)

Thanks for replying.

Based on
https://www.freebsd.org/portmgr/
https://docs.freebsd.org/en/books/porters-handbook/book/

my guess is that a port committer has to "commit" the deprecation and final removal from the ports tree, if that is the action that will taken.

Probably, portmgr (Ports Management Team) will take the lead in the core  decision.

I've taken the liberty in adding portmgr to the CC list.


P.S.
Searching
https://docs.freebsd.org/en/books/porters-handbook/book/
I could not find any specific reference for this kind of deprecation request.
Comment 3 Joel Bodenmann freebsd_committer freebsd_triage 2024-07-14 14:31:01 UTC
Created attachment 252047 [details]
patch
Comment 4 Joel Bodenmann freebsd_committer freebsd_triage 2024-07-14 14:35:12 UTC
Probably unnecessary but: Asking for explicit maintainer-approval for completeness.
Comment 5 Slawomir Wojciech Wojtczak 2024-07-14 21:24:13 UTC
Comment on attachment 252047 [details]
patch

I approve.
Comment 6 commit-hook freebsd_committer freebsd_triage 2024-07-15 14:09:15 UTC
A commit in branch main references this bug:

URL: https://cgit.FreeBSD.org/ports/commit/?id=ed0b9deff1b1ac3d92a63da654d455fdf8781c45

commit ed0b9deff1b1ac3d92a63da654d455fdf8781c45
Author:     Joel Bodenmann <jbo@FreeBSD.org>
AuthorDate: 2024-07-14 14:26:23 +0000
Commit:     Joel Bodenmann <jbo@FreeBSD.org>
CommitDate: 2024-07-15 14:08:17 +0000

    sysutils/beadm-devel: Deprecate and set expiration date to 2024-08-15

    This port (sysutils/beadm-devel) has not been updated in years and the
    corresponding main port (sysutils/beadm) is known to be stable.

    PR:                     280189
    Approved by:            tcberner (mentor), vermaden@interia.pl (maintainer)
    Differential Revision:  https://reviews.freebsd.org/D45977

 sysutils/beadm-devel/Makefile | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)
Comment 7 Joel Bodenmann freebsd_committer freebsd_triage 2024-07-15 14:09:31 UTC
Done - Thank you guys!