[Bug 233423] Review Request: mecab-python - Python binding for MeCab

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request:  mecab-python - Python binding for MeCab


https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=233423





------- Additional Comments From j.w.r.degoede at hhs.nl  2007-03-31 12:33 EST -------
(In reply to comment #3)
> Well,
> 
> * This is a Python binding for MeCab, so the main package is
>   mecab, not python. i.e. This is rather a subpackage of mecab
>   and very similar with paragui-python.
> 
>   And... actually for ruby-mecab:
> --------------------------------------------------------
> These naming guidelines only apply to ruby packages whose main purpose is
> providing a Ruby library; packages that mainly provide user-level tools that
> happen to be written in Ruby do not need to follow these naming guidelines,
> and should follow the general  NamingGuidelines instead.
> ---------------------------------------------------------
>   so.. IMO I have to rename from ruby-mecab to mecab-ruby...
>

No,

The part quoted from the ruby guidelines, is identical for python. In both cases
the exception is for applications, since an application shouldn't be called
python-fee just because its written in python. In this case we are talking about
bindings, iow they make mecabs functionality available to applications written
in python/ruby. Thus they should be called python-mecab and ruby-mecab, this is
so that people looking for python "libs" can find them easily by doing "yum list
'py*'" .

About paragui, things are different there as the binding is in the main lib
package, and the correct name for the main package obviously is paragui, thus a
python subpackage automatically becomes paragui-python, this is an exception I
think. But maybe even there it should get called python-paragui by using
"%package -n python-paragui" instead of "%package python"

In this however these are seperate packages from the main package and thus must
be called python-mecab and ruby-mecab according to my reading of the guidelines,
if you disagree, please discuss this on the list.

> * If mecab-python should be renamed to python-mecab, so are
>   mecab-perl, mecab-java? I think it is quite questionable.

Yes, the same goes for perl modules according to:
http://fedoraproject.org/wiki/Packaging/NamingGuidelines#head-8756a3bce652c376d7ba3908461b638784b6952d

And I cannot find anything for java, so choose what you like I guess.


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.