scapy still depends on Python 2.4

[jwiegley@…]

It should depend on 25 nowadays.

[pmq@…]

Shouldn't we kill the port actually? I find it easier nowadays to just use mercurial (but still install all deps using MacPorts), because there's no 'stable' version (as in tagged as stable). What do you think, would it be a good idea to just nuke it?
Cc'ing Mike as I understand he's interested in that matter.

[blb@…]

Is 2.0.0.11 not stable? Also, you can always create a scapy-devel to checkout with hg.

[mike-savory]

As 2.0.0 versions now requires Python 2.5, there are now the 2.5 dependancy ports to match, I was intending on creating a scapy2 port and leaving scapy as the stable version 1, but I have not done anything about it. I do use it regularly.

[jwiegley@…]

One of the whole charms of MacPorts is that it installs all the dependencies for you and "just works". I would love to see the Scapy port continue, which after installation would provide a "scapy" script which could you run and everything would Do What It Should.

[mike-savory]

Yes, I'll take that as a reminder to work on something. So what do people think about keeping scapy and adding a scapy2 port? I like that scapy also picks up the MP wireshark and other tools.

[pmq@…]

Finally had some time. Questions:

• can we make it depend on Python 2.6? (it seems the 2.5 PortGroup depends on that?)
• is there a need to have some sort of +kitchensink variant that enables the dependencies on TeX and ghostscript? Been building all day. Thoughts?

Also, thanks about the "picks up the MP tools", I forgot I did these reinplaces, and you're right it justifies having it in the tree.

[mike-savory]

Unfortunately, I still have no time for at least another 2 weeks. Feel free to pick up and run in any direction....

scapy declared its dependencies as

Library Dependencies: python24, py-readline, py-pylibpcap, py-libdnet, py-crypto, py-gnuplot, py-pyx, graphviz

My thoughts on the best path was to just build a new scapy2 port that depends on python25 py25-readline py25-pylibpcap py25-libdnet py25-crypto py25-gnuplot py25-pyx py25-pygraphviz

and used the pyton port group code to install as a framework.

It seem at the moment, python on Macports has no generic way to manage the different Python versions in any dynamic way.

Philippe changed from scapy1.x to scapy2.x when he introduced the python 2.5 dependency, it just seems like we need to follow suit.

Then we need to get this page updated to cover Leopard and that we are not darwinports ​http://www.secdev.org/projects/scapy/portability.html

[(none)]

Milestone Port Bugs deleted

[nerdling (Jeremy Lavergne)]

We're trying to get ports off of python24. I move that we simply update scapy to use python25 and its version to the 2.X branch.

[nerdling (Jeremy Lavergne)]

diff using python25

[nerdling (Jeremy Lavergne)]

Cc Me!

[pmq@…]

Diff looks fine to me. Unsure wether the reinplaces still work.

[nerdling (Jeremy Lavergne)]

Committed in r54905.

[mike-savory]

Upgrade does not actually install a new scapy version.

$ sudo port   uninstall scapy
--->  Deactivating scapy @2.0.0.10_0
--->  Uninstalling scapy @2.0.0.10_0
$ sudo port   install scapy
--->  Fetching scapy
--->  Verifying checksum(s) for scapy
--->  Extracting scapy
--->  Configuring scapy
--->  Building scapy
--->  Staging scapy into destroot
--->  Installing scapy @2.0.0.10_0
--->  Activating scapy @2.0.0.10_0
--->  Cleaning scapy
$ sudo port contents  scapy
Port scapy contains:
  /opt/local/bin/scapy.py
  /opt/local/etc/ethertypes
$ sudo   /opt/local/bin/scapy.py
Password:
/opt/local/bin/scapy.py:3156: Warning: 'with' will become a reserved keyword in Python 2.6
/opt/local/bin/scapy.py:3158: Warning: 'with' will become a reserved keyword in Python 2.6
Welcome to Scapy (1.2.0.2)
>>> 

[mike-savory]

It seems I do not have permission to reopen ticket

[mike-savory]

Build log after Committed in r54905.

[nerdling (Jeremy Lavergne)]

Alrighty, I'll bump the revision.

[mike-savory]

Not sure its that simple, Scapy 2 is now a Framework install

[mike-savory]

Also looks to me that the portfile selects

distfiles ${name}.py:code ethertypes:files

so still pulls the 1.2 branch not the current 2.0 branch

[mike-savory]

OK so I started again with my local porttfile, (attached in my next post)

It Has the correct get syntax now and downloads the release (a zip file)

But the unzip stage errors out at

warning [/opt/local/var/macports/distfiles/python/scapy-2.0.0.10.zip]:  61 extra bytes at beginning or within zipfile
  (attempting to process anyway)

[mike-savory]

My draft Scapy 2 portfile

[mike-savory]

Here are the instructions for installing scapy 2 (it uses the standard distutils method)

​https://www.secdev.org/projects/scapy/doc/installation.html#installing-scapy-v2-x

[nerdling (Jeremy Lavergne)]

Updated in r54993, based on msavory's Portfile. Revision to 2.

[mike-savory]

Sorry if I was not clear, My Portfile still does not build... See failed buildlog attached to ticket

Please reopen ticket

[nerdling (Jeremy Lavergne)]

Your build log was for 2.0.0.10_0. This is 2.0.0.10_2. I tried it before I committed it; built for me.

[mike-savory]

Scapy 1.x was a single executable scapy.py source file

Scapy 2.x is a zipped framewrk build that needs to be installed using sudo python setup.py install

I would guess that the Portfile now simply doesnt install anything (check port contents scapy)

I will check the new revision when It gets here

[mike-savory]

Thanks, It looks like it does install now, The portgroup code must take care of the whole setup thing....

Thanks

I guess my portfile was better than I thought.....