Date: Wed, 28 Jul 2021 02:32:52 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 238368] devel/mercurial: hg-ssh is not executable, and not available Message-ID: <bug-238368-21822-Y59QfjZOoo@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-238368-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-238368-21822@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=238368 Kubilay Kocak <koobs@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|maintainer-feedback?(python |maintainer-feedback+ |@FreeBSD.org) | Assignee|python@FreeBSD.org |koobs@FreeBSD.org Status|New |Closed Resolution|--- |Works As Intended --- Comment #1 from Kubilay Kocak <koobs@FreeBSD.org> --- Apologies for the delay responding to this issue. Mercurials setup.py doesn't include contrib/hg-ssh in its 'scripts' list, which is what tells setuptools to install things in LOCALBASE/bin. My take on this is that things in contrib/* are 'extra' conveniences, to be used directly by end users, and not necessary to be installed in an integrated manner on end user systems in the same manner 'hg' is. In this case you are able at any time to invoke hg-ssh from the location it is installed, and my understanding of the `env python3` shebang is that is it is the appropriate PEP-394 compatible invocation. Users may install the lang/python3 port to install the Python convenience symlinks. If you believe hg-ssh warrants inclusion as a 'scripts' for integrated installation like `hg`, I'd suggest opening an issue upstream and making that case -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-238368-21822-Y59QfjZOoo>