Enhancement request: cleanup recipe names

Description

Having worked to get requirements correct, users find the recipe names are different for no apparent reason. WTF?!

And scrolling the recipes directory, looking for a clue, is a challenge because there are also libraries and misnamed items in there.

Its confusing.

Cleanup the names, and in p4a implement a lookup table for backwards compatibility. Or create alias recipes like pil.

Wrong name wrt Pypi

dateutil        is python-dateutil
mysqldb         is mysql-python       - this claims to only support Python2
ndghttpsclient  is ndg-httpsclient
opencv          is opencv-python
opencv_extras   is opencv-contrib-python
protobuf_cpp    is protobuf-python
pyleveldb       is leveldb
spine           is spine-cython

Conflicting Pypi name:

av recipe is not av package, correct name is pyav , av is a different package

Some oddballs, not clear how a user would know what these are (or how to use them)

audiostream
cymunk
pil
vlc

Libs that are not named libXXXX (perhaps all the libs could be in a different directory?)

freetype 
harfbuzz
ifaddrs
jepd
openal
openssl
sqlite3

Commencez par examiner le répertoire recipes et le point d’entrée de recherche des recipes de p4a, en utilisant comme périmètre les noms incohérents, contradictoires et atypiques répertoriés. Déterminez si des recipes renommées ou des alias préservent mieux les noms existants, puis vérifiez que les anciens noms continuent d’être résolus tandis que les noms des répertoires correspondent aux packages et bibliothèques prévus.