above: add package.

[s7x]

Added the Above tool by casterbye.

[s7x]

Ping @noraj, this is why I did not want to change this package too much. With the new templates we have (using the pip version for example), this is the result:

[noraj]

Are you sure it needs scapy (cli) and not python-scapy (library)?

[noraj]

Ping @noraj, this is why I did not want to change this package too much. With the new templates we have (using the pip version for example), this is the result:

It's not your fault or the template fault, it's badly packaged upstream.

/usr/bin/above is the proper wrapper created by pip that works way better than the dirty 2 lines bash wrapper that cd /usr/share/package. But here above is poorly developed, instead of using a standard file architecture, havign separate library files than a CLI consuming the lirary, a proper pyproject.toml and a properly declared entrypoint, it's a dirty 1100 LoC one-file script, packaged with the old setup.py and wrongly declared entrypoint. /usr/bin/above.py shouldn't be there but somewhere in /usr/lib/python3.13/site-packages/above/. above_oui_dict.py is also wrongly deployed under /usr/lib/python3.13/site-packages/above_oui_dict.py instead of /usr/lib/python3.13/site-packages/above/above_oui_dict.py due to the bad setup.py.

[noraj]

/usr/bin/above.py shouldn't be there but somewhere in /usr/lib/python3.13/site-packages/above/. above_oui_dict.py is also wrongly deployed under /usr/lib/python3.13/site-packages/above_oui_dict.py instead of /usr/lib/python3.13/site-packages/above/above_oui_dict.py due to the bad setup.py.

This because it blindly uses packages=find_packages() without argument AND the python files are on the root of the directory instead of in a above folder. etc. I'll submit a package with prepare() that fix upstream mess.

[noraj]

Also you use python/PKGBUILD-python-PEP517-pip that is made for pyproject.toml instead of python/PKGBUILD-python-PEP517-setuptools that is made for setup.py.