From: Intransition Date: 2010-08-06T09:10:51+09:00 Subject: Re: Project name ownership and conflict On Aug 5, 7:27 pm, James Britt wrote: > As it stands, though, it's a social/cultural issue. It a wider issue than we might realize too. Today I was looking for a name for a project, and I considered 'figleaf'. There was no gem by the name, but I discovered that their was a Python project by the name, and it just so happened that the Python script had an executable named 'figleaf', and it dawned on me that my project too would have an executable named 'figleaf', if I choose that name. In which case, there could be a conflict in a system 'sbin/ directory. A multi- lingual developer who used both Python and Ruby might run into such a problem. I am not sure there is any good solution to this. OS's would need to build namespacing directly into the PATH lookup system. It's far too annoying to be naming all one's executables 'figleaf-ruby' or 'transfire-figleaf' or what have you.