On Tue, 2008-12-16 at 19:11 -0800, Maluku wrote: > On 17 Dez., 03:36, Malcolm Tredinnick <malc...@pointy-stick.com> > wrote: > > It's very easy: you just don't call it that. Why does it require > > "change"? > > I have discussed this with the perl naming people here: > http://www.nntp.perl.org/group/perl.modules/2008/12/msg63533.html
So the problem that you are now mentioning is that you registered the name first and decided to ask check if there might be a problem only afterwards. I'm really not trying to be a hard-ass here, but that's not a motivating factor. The solution is still simple. You just don't upload anything. You pick a better, different name and use that. You tell the CPAN guys you made a mistake in registering the original name. What happens if somebody makes a typo in the name of their package, for example? There must be plenty of cases of accidental registration. > > Choose a different name for it. If you > > implement a web server in Perl are you going to call it "Apache::*", if > > it does some of the same things as Apache (e.g. using the HTTP > > protocol)? No, you're going to find a proper name and then mention in > > the docs that it does some of the same things as Apache, or in similar > > ways to Apache. That avoids any confusion between your product and the > > actual Apache product. > It called it that, because it provides a template language like > Django, but if this is a problem I will call it something else. > Apache is a bad example, since many modules that _use_ Apache are also > in the Apache:: Namespace, like Apache::Template and such. No, Apache is a good example and I chose it with good reason. You are not writing something that uses Django or wraps Django to provide a Perl interface or is used in conjunction to extend Django. You are reimplementing it entirely independently, just as if you writing a different webserver. It just happens to use the same syntax. > So where would you look for a template system to work with your > existing Django templates? In Django. Why would I have Django templates and then want to switch to Perl, would be the more relevant question. I doubt the cross-over audience is you primary base here. Not having Django in the name is not the show-stopper for searches in any case. Any decent search engine is going to index the description that will include sentences like "uses a syntax similar to Django templates". As I said, I don't really have any power of decision here. I'd be disappointed if the name Django was used in the Perl module name and there are precisely no technical reasons why it's required. Malcolm --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
