Hi!
Ummm, isn't this legally dangerous? Stamping a piece of code with Microsoft's name can be interpreted as counterfeiting.
Maybe a better choice would be to add a configure option --with-company-name and let the users set it to... whatever...
Paul Chitescu
On 3/7/07, Paul Chitescu paulc@voip.null.ro wrote:
Hi!
Ummm, isn't this legally dangerous? Stamping a piece of code with Microsoft's name can be interpreted as counterfeiting.
Maybe a better choice would be to add a configure option --with-company-name and let the users set it to... whatever...
Paul Chitescu
A registry option would be nicer.
Jesse
"Paul Chitescu" paulc@voip.null.ro wrote:
Ummm, isn't this legally dangerous? Stamping a piece of code with Microsoft's name can be interpreted as counterfeiting.
Since obviously some app depends on that it should be deemed a reasonable choice of action IMHO.
Maybe a better choice would be to add a configure option --with-company-name and let the users set it to... whatever...
A better choice would be to sue that company for tieing its product to a monopolistic platform, but unfortunately we have no resources for that.
Paul Chitescu paulc@voip.null.ro writes:
Ummm, isn't this legally dangerous? Stamping a piece of code with Microsoft's name can be interpreted as counterfeiting.
Not really, it's just providing a string that apps require to behave properly. The LegalCopyright field still says it's been written by the Wine authors. It's similar to IE pretending to be Mozilla in its user-agent string...