Date: Wed, 15 Jan 2025 17:16:13 +0000 From: bugzilla-noreply@freebsd.org To: pkg@FreeBSD.org Subject: [Bug 284054] ports-mgmt/pkg: Does not recognize .pkg as a valid suffix (triggered by portupgrade) Message-ID: <bug-284054-32340-dvUtungpZs@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-284054-32340@https.bugs.freebsd.org/bugzilla/> References: <bug-284054-32340@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=3D284054 --- Comment #18 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Terry Kennedy from comment #13) QUOTE since portupgrade will be around for at least nearly 4 years (remaining life of 14) and perhaps longer if it goes through the normal deprecation (15) and removal (16) cycle. END QUOTE You seem to be confusing procedures for: https://cgit.freebsd.org/src/ and the related branch and release handling with the procedures for: https://cgit.freebsd.org/ports/ and port depreciation. ports-mgmt/portupgrade is not part of FreeBSD and FreeBSD, of itself, makes no use of ports-mgmt/portupgrade . Similarly, the FreeBSD package builders do not use ports-mgmt/portupgrade . No FreeBSD infrastructure uses ports-mgmt/portupgrade as far as I can tell. ports-mgmt/portupgrade is not part of any FreeBSD release and not required by any either. Mentioning or describing a port's use in the handbook or elsewhere does not change that status unless explicitly indicated somewhere or the port having the status of FreeBSD or its infrastructure directly using the port. --=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-284054-32340-dvUtungpZs>