scapy + py26-scapy

Savory Michael msavory1 at
Mon May 9 10:13:25 PDT 2011


Scapy 1.0 is stuck requiring python 2.5 and Scapy 2.0 is current, the old scapy port was meant to be kept for scapy 1.0 but then got upgraded anyway. It is probably of little importance and could now be merged. 

If upgrading to 2.2.0 then this fix in tip from 5 weeks ago would be good to include.


On May 9, 2011, at 3:27 AM, Ryan Schmidt wrote:

> On May 9, 2011, at 03:40, Joshua Root wrote:
>> Why do we have 'scapy' (which uses python25) and also 'py26-scapy'? It
>> looks like Scapy is an application that happens to use python, so there
>> should only be one port (possibly with variants to select a python
>> version if there's a good reason to want to change.)
>> The py25-foo, py26-foo etc. naming convention should be used for ports
>> that install a python module that will be used by other things,
>> potentially using different python versions.
> Sounds right to me. Mark py26-scapy as replaced_by scapy, update scapy to 2.2.0 and use python27 or provide python variants if necessary.
> See also:

More information about the macports-dev mailing list