I'm guessing it would be required for the contribution permalink (clean name) on the DB, the class name, the directory and clean name in the manifest would need to be the same with the Human Name in the manifest and the Contribution being the same. It would probably be added to the MPV (Which by the looks of it would need to have a lot of what it looks for re-written).imkingdavid wrote:Ultimately, the Customisations Database should keep track of what folder name is used by each extension and disallow the submission of another extension that wants to use the same one.
Perhaps a new little tool to check to see if a name is available? (I.e. "Enter a name: ______", "Sorry, that name is taken, please try another one." or "YAY! That name is currently available. Hurry up and take it before someone else does!")
Of course that would have to be built after the CDB starts recognizing extension names.
The permalink has to be unique anyway, but we need to think of multiple repos/CDBs.
EDIT: Just a thought, maybe not MPV as that couldn't check it was the same as the permalink in titania as it works independently. It would most likely be a third check added to the submission process.
The submission process needs revamping anyway with the differences between extensions and MODs and I am guessing they would be under the same contribution type so it would need to detect which it is (or ask) when the contrib type is MOD, then it would run either the extensions admin or automatic mod installer and then either an extensions MPV or a normal MOD MPV.
EDIT: David already covered some of this while I was typing but oh well.