2009/4/28 Karsten Wade <kwade(a)redhat.com>:
On Tue, Apr 28, 2009 at 01:40:17PM -0400, loupgaroublond(a)gmail.com
wrote:
> Hey List,
>
> We have a minor naming conflict issue to figure out. There is another package in
Fedora called ekg. I want to figure out what we should call the python package.
>
> We have a few choices, i think
> 1) python-ekg (makes sense compared to virtualenv which also includes scripts)
> 2) ekg-scanner (since it's really an application and not necessarily a library)
> 3) rename ekg to something else
> 4) other
>
> I'm leaning heavily towards door #1, but i just wanted to hear if
> there are any good reasons why we don't want to do that.
I don't understand the first example. How is our EKG Python specific,
and how does it relate to the nature of the package?
#2 works if this is just a scanner component in a larger set. For
example, if we added ekg-grapher as a stand-alone graphing tool, etc.?
#1 works because there's a precedent that applications that are really just
entrypoints into python library code should be named like a library. If nothing else,
there would be a definite 'python-ekg' package no matter what. I could split it
off with subpackages too.
-Yaakov