I fully support this. Consistency is good.
Michael Scherer wrote:
> Hi.
>
> This may not the right moment to discuss about this, but I think we
> should set up a naming policy for the rpm.
>
> To give a simple exemple, the python module.
>
> Some of them are named
> foo-python, and the others are named python-bar.
>
> example adns-python, libxslt-python
> vs python-xoltar, python-fam
>
> i suggest to stick to python-bar form, in the same way that perl modules
> are named.
>
> this can be applied to xmms modules, apache2 modules, ruby extensions
> and a lot of software.
> Most of them are maintened by the same person ( abiword => mpol , xine
> => goetz ), so, there is consistency, but, for the other, there is no
> standard
>
> In order to enforce the policy, i have coded a rpmlint extension, and i
> have send it to Frederic Lepied 2 month ago, but i was busy and forget
> to talk about the subject on the list. He said it would be present for
> the next release of rpmlint.
>
> So, i propose the policy as implemented in the rpmlint test.
>
> mainly, xmms plugin in /usr/lib/xmms/ must begin with xmms-, and the
> same for python, ruby, perm, php, fortune.
> I didn't add all the pssible test, they can be quite easily added in the
> future.
>
> I know that there is a lot of exception to be added to rpmlint, in order
> to support this test, but we will see this later.
>
>
> Wdyt ?
