Hope you don't mind a request for clarification, all can answer
I by far prefer to use the upstream package and binary name, preferably using lower case letters. I definitely think we should at least be free to use the upstream name.
But in the past I have received instructions to keep the existing name convention, when the source is named something else
I will name this one as it shows an example of mixed upper and lowercase
libportaudio.tcz........an existing name
upstream url
http://www.portaudio.com/and from license link
PortAudio Portable Real-Time Audio Library
No I am not trying to rename this tcz just providing an example to see, as I use eyes (sometimes) better than abstraction examples
Question
######
Any reason why we can't used mixed upper and lower case in new tcz submissions?
If there are good reasons ----either way-----I would like to add it to the extensions wiki
IMHO, any new submission "ideally" should respect the upstream naming convention. But that could lead to mixed case?
cheers
Gordon