Addon Packages General Naming policy

[Michael Schwendt]

https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_...

| If a new package is considered an "addon" package that enhances or adds a
| new functionality to an existing Fedora package without being useful on
| its own, its name should reflect this fact.
|
| The new package ("child") should prepend the "parent" package in its
name,
| in the format: %{parent}-%{child}.

It's a simple naming scheme. Yet it seems that this part of the Naming
Guidelines is either not known widely enough, or some packagers and reviewers
think they don't need to adhere to this policy without asking this list
for feedback. And it's a "should" not a "must".

What's up with "vim" add-on packages? IMO, it's a confusing mess if some
of
them start with vim- while others don't. Also, how to know whether/when a package
has been renamed to follow the guidelines? Packages like "gap-vim" and
"uzbl-vim"
don't extend "gap" or "uzbl", but vim.

# yum list \*-vim-\*
Loaded plugins: langpacks, refresh-packagekit
Available Packages
fluxbox-vim-syntax.noarch           1.3.5-1.fc19                         fedora 
gap-vim.noarch                      4.6.4-2.fc19                         fedora 
golang-vim.noarch                   1.1.1-5.fc19                         updates
protobuf-vim.x86_64                 2.5.0-4.fc19                         fedora 
texlive-context-vim.noarch          3:svn29984.0-0.1.fc19                updates
texlive-context-vim-doc.noarch      3:svn29984.0-0.1.fc19                updates
uzbl-vim.x86_64                     0-0.31.20120514228bc38cbd.fc19       fedora 
wklej-vim.noarch                    0.1.7-6.fc19                         fedora 

# yum info \*-vim-\*|grep '^\(Name\|Desc\)'
Name        : fluxbox-vim-syntax
Description : Enable vim syntax highlighting support for fluxbox configuration
Name        : gap-vim
Description : This package provides VIM add-on files to support editing GAP
Name        : golang-vim
Description : Vim plugins for Go.
Name        : protobuf-vim
Description : This package contains syntax highlighting for Google Protocol
Name        : texlive-context-vim
Description : ConTeXt has excellent pretty printing capabilities for many
Name        : texlive-context-vim-doc
Description : Documentation for context-vim
Name        : uzbl-vim
Description : Highlighting files for uzbl's configuration.
Name        : wklej-vim
Description : A wklej.org submitter plugin for vim.

On the contrary:

# yum list vim-\*
Loaded plugins: langpacks, refresh-packagekit
Installed Packages
vim-minimal.x86_64          2:7.3.1314-1.fc19                           @updates
Available Packages
vim-X11.x86_64              2:7.3.1314-1.fc19                           updates 
vim-clustershell.noarch     1.6-3.fc19                                  fedora  
vim-command-t.x86_64        1.4-4.fc19                                  fedora  
vim-common.x86_64           2:7.3.1314-1.fc19                           updates 
vim-enhanced.x86_64         2:7.3.1314-1.fc19                           updates 
vim-filesystem.x86_64       2:7.3.1314-1.fc19                           updates 
vim-halibut.noarch          1.0-7.20120803svn9601.fc19                  fedora  
vim-jedi.noarch             0.5.0-5.fc19                                fedora  
vim-latex.noarch            1.8.23-11.20130116.788.git2ef9956.fc19      fedora  
vim-latex-doc.noarch        1.8.23-11.20130116.788.git2ef9956.fc19      fedora  
vim-nerdtree.noarch         4.2.0-9.fc19                                fedora  
vim-perl-support.noarch     5.0.1-3.fc19                                fedora  
vim-taglist.noarch          4.6-5.fc19                                  fedora  
vim-vimoutliner.noarch      0.3.6-3.fc19                                fedora

[Christopher Meng]

They both add -vim as sub package

IMO if a syntax file is shipped in pkg, pkg-vim is OK.

Sent from Note I

[T.C. Hollingsworth]

On Fri, Aug 9, 2013 at 4:48 PM, Christopher Meng <cickumqt(a)gmail.com&gt; wrote:
>  They both add -vim as sub package
>
>  IMO if a syntax file is shipped in pkg, pkg-vim is OK. 
I disagree.  This is the same reasoning that gives us crap like
"rpm-python" when every other Python library is "python-foo".

The entire point of using prefixes like these is that it makes
libraries/add-ons for specific languages/programs easier to find.
That becomes pointless if half the relevant packages do it one way and
half the other packages do it the other way.  :-(

Package names are for users, and users don't know/care what SRPM a
package comes from.

-T.C.

[Matthias Runge]

On 10/08/13 01:48, Christopher Meng wrote:
>  They both add -vim as sub package
>  
>  IMO if a syntax file is shipped in pkg, pkg-vim is OK.
>  
>  Sent from Note I 
Please don't remove the context. This is just annying; also,
I'm not
interested in your mailing program.

I disagree. IMHO, it's the same like for python- perl- etc. packages.
Nothing restricts one to use sane names like vim-foo, which would be a
vim extension to use foo.

Matthias
-- 
Matthias Runge <mrunge(a)matthias-runge.de&gt;