Double port: scapy

Jeremy Lavergne jeremy at lavergne.gotdns.org
Wed Jan 16 07:27:05 PST 2013


> Hello list,
> I just noticed that we have two ports for scapy, one named scapy and the other named py26-scapy. Should we:
> - create a unified portfile named py-scapy
> - delete py26-scapy
> - mark scapy replaced_by py27-scapy (since scapy is based on python27 at the moment)
> or:
> -mark py26-scapy replaced_by scapy
> 
> I personally like the second alternative, since it's an application and not just a module (it installs a script in ${prefix}/bin), but looking at ports like ipython and simpy, maybe the first is preferable.

It looks like scapy is already a (semi-incomplete) unified Portfile, while py26-scapy is not.

Feel free to look at the differences between the two, and update scapy as needed (remember to wrap things in if(subport != name) so the virtual package scapy is just a stub while pyXX-scapy install things.

Once ready to check in those changes, delete py26-scapy as well (otherwise we'll have duplicate package for py26-scapy) :-)



More information about the macports-dev mailing list