[Bug 233999] [NEW PORT] security/py-exscript: Automating Telnet and SSH

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Fri Dec 14 03:13:19 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233999

Kubilay Kocak <koobs at FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |feature, needs-patch,
                   |                            |needs-qa
              Flags|                            |maintainer-feedback?(rozhuk
                   |                            |.im at gmail.com)
             Status|New                         |Open
            Summary|[NEW PORT]                  |[NEW PORT]
                   |security/py-exscript:       |security/py-exscript:
                   |Python module and a         |Automating Telnet and SSH
                   |template processor for      |
                   |automating network          |
                   |connections                 |
                 CC|                            |python at FreeBSD.org

--- Comment #2 from Kubilay Kocak <koobs at FreeBSD.org> ---
Review items:

* The canonical version scheme is x.y.z (per PyPI release), current version is
2.6.2. Update PORTVERSION accordingly. The repo does not contain a tag for this
version, ask them to create one. Identify the exact revision of the 2.6.2
release and use that, if its not the same as the one already provided.
* Add a # comment above USE_GITHUB as to why its being used (upstream does not
(yet) distribute an sdist). Ask upstream to publish a source distribution.
* COMMENT should match setup.py:description (modified to portlint compliance)
where possible.
* Makefile section ordering needs addressing (NO_ARCH, *_DEPENDS)
* Add LICENSE_FILE
* paramiko RUN_DEPENDS: FLAVOR needs to be PY_FLAVOUR
* This package provides command line scripts. For packages that do this,
package should be concurrent(installation)-safe. Use USE_PYTHON=concurrent, and
QA that there are no files that share common locations between Python 2 and 3
build locations.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the freebsd-python mailing list