[Bug 230110] net/scapy: Update to 2.4.0

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Sat Jul 28 14:22:16 UTC 2018


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

            Bug ID: 230110
           Summary: net/scapy: Update to 2.4.0
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: vanhu at FreeBSD.org
          Reporter: freebsd_ports at k-worx.org
                CC: python at FreeBSD.org, vanhu at FreeBSD.org
             Flags: maintainer-feedback?(vanhu at FreeBSD.org)
          Assignee: vanhu at FreeBSD.org
 Attachment #195532 maintainer-approval?(vanhu at FreeBSD.org)
             Flags:
                CC: vanhu at FreeBSD.org

Created attachment 195532
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=195532&action=edit
scapy-2.4.0.patch

Hello,

attached is the patch that updates net/scapy to 2.4.0 . This release introduces
support for Python 3 but some dependent ports in the ports tree aren't ready
for Python 3, yet.

So this version still sticks to Python 2.7.

Changes by upstream:
- https://github.com/secdev/scapy/releases/tag/v2.4.0

Changes to the port:
- added LICENSE_FILE
- sorted variables according to the PHB
- added noflavors
- added back the SOX option (dependencies were available but the option was
omitted)
- changed ${PYTHON_SITELIBDIR} to ${PYTHON_PKGNAMEPREFIX}
- fixed dependencies for the PYX option
- added IPYTHON option
- made post-patch target a bit more readable
- reformatted pkg-plist to make it more readable

QA:
~~~
- poudriere (10.4-, 11.1-, 11.2-RELEASE, 12.0-CURRENT @r336739) for each amd64
+ i386 archs -> OK
- portlint -> OK


Note:
Before this update can be committed the graphics/py-PyX12 port must be
downgraded to 0.12.1 (see also PR #230109 ->
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=230109)

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list