Created attachment 224777 [details] [patch] update porttools to chase freebsd ports tree svn->git transition The skreuzer porttools repo on upstream github has updates to accomodate the freebsd ports tree switch from svn to git. Attached is an update for a tentative 1.10 version that includes those changes. I don't see any way to have a 'pull request' on github.com for just putting a tag in place. The patch attached references the specific commit id (GH_TAGNAME). If a 1.10 tag appears in the upstream repo (hint, hint), the GH_TAGNAME in the patch can be removed (and probably re-run 'make makesum').
Comment on attachment 224777 [details] [patch] update porttools to chase freebsd ports tree svn->git transition Steven, if you add a 1.10 tag on github, tweak patch accordingly.
Created attachment 224778 [details] [patch] update porttools to chase freebsd ports tree svn->git transition [v2] Forgot to change run dep from svn to git.
A commit in branch main references this bug: URL: https://cgit.FreeBSD.org/ports/commit/?id=b8e3cc36b68c00893c39a8ec64c373d87be62c0e commit b8e3cc36b68c00893c39a8ec64c373d87be62c0e Author: Steven Kreuzer <skreuzer@FreeBSD.org> AuthorDate: 2021-05-14 15:41:49 +0000 Commit: Steven Kreuzer <skreuzer@FreeBSD.org> CommitDate: 2021-05-14 15:44:11 +0000 ports-mgmt/porttools: Update to version 1.10 Update port to version 1.10, which adds support for working with git repos PR: 255713 Reported by: John Hein <jcfyecrayz@liamekaens.com> ports-mgmt/porttools/Makefile | 5 +++-- ports-mgmt/porttools/distinfo | 6 +++--- 2 files changed, 6 insertions(+), 5 deletions(-)
Committed! Thanks
(In reply to Steven Kreuzer from comment #4) Thanks. Is there any reason not to push a 1.10 tag upstream?
(In reply to John Hein from comment #5) It looks like a 1.10 tag was added in github.com (thanks), although it is not an annotated tag, so who knows when it was added. <side comment>And there's no history tracking if it ever changes (true whether it's annotated or not). I really hate tags in git it might even be worse than cvs in many ways as far as lack of history. You need to write down the commit id out of band to know if a tag changes because there's no way in git of knowing if/when it changes (maybe for a short while before garbage collection removes the ephemeral history of any such change(s)).</side comment> Anyway, the GH_TAGNAME could be removed (and re-run 'make makesum'). But maybe it's better to just keep the tag info because of git's tag history weakness. Less thrash in the port, too. I guess I wouldn't bother removing the GH_TAGNAME.