Re: Re: Re: Prefixes for packages according to every

Quoted from Martin J. >While I understand the rationale behind this idea, I do not like that >approach. Having the ability to choose from a pool of possible >prefixes even in one category has always been a convenient thing and I >would really like to keep it that way. > >Why don't we just settle on forcing packages to have a prefix, but >still allowing multiple prefixes per category? This way we keep the >advantages of the status quo, while at the same time keeping the >"namespace" clean. Here you can see why i was suggestion few more prefixes for We bServices Quoted from Toby >Won't several prefixes mean several installation folders? IIRC currently we >have a dir called "Net" for categorie "Networking". That would mean >directories "Websvc" and "Webserv" for the categorie >"Webservices". I you look at the Web Services category then you see only 2x of the packages there sure any prefix of at all, actully XML_RPC uses a prefix ... this might be misleeding to have a package with the prefix XML_ in Web Services package. I *know* that the package name is XML RPC but this might look to other people like a prefix and thus this should be in the XML category. I'm in favor of having like Stefan said a list of prefixes people should use, but it would also be a good idea to put togather a list of strongly recommended prefixes that each packages should use, and if the person doesn't want to use any prefix then it would be up to the QA team to rule wether it's okey or not. Might be a usefull clause in the manual. -- Regards Helgi