On Thu, Dec 5, 2013 at 4:21 PM, Jeffrey Johnson <[email protected]> wrote:
>
> On Dec 5, 2013, at 7:48 AM, Denis Silakov wrote:
>
>> Hi all,
>>
>> In Prague, we have discussed with Robert that it would be nice to have 
>> packaging policies in OMV wiki. Currently we have this page: 
>> https://wiki.openmandriva.org/en/Linux_System_packaging_guidelines
>> but this can be considered as a quick start guide, not the detailed policy.
>>
>> I suggest to import packaging policies from ROSA wiki:
>> http://wiki.rosalab.ru/en/index.php/Category:Packaging_Policies
>>
>> they are based on old MDV documents, but most of them are adopted for modern 
>> reality. Some of them can be outdated and should be rechecked, but at least 
>> the following ones should be imported:
>> * Libraries policy
>> * Perl policy
>> * Python policy
>> * Ruby policy
>> * Web application policy
>>
>> I wonder what is the best place in OMV wiki for such documents? And does 
>> anybody want to perform translation of this policy from ROSA to OMV wiki?
>>
>
> While there is nothing wrong with clear/accurate/maintained packaging 
> policies on
> a wiki page, there is a need to also describe the means/procedures by which
>         1) the policy can be modified/amended/clarified
>         2) the policy is detected/enforced
>
> rpmlint is/was a healthy start but looks only at single packages, with a 
> rather
> lenient/loose metric. Many policy violations have a much larger distro scope 
> that
> cannot be implemented in rpmlint meaningfully.
In fact. Many distros policies are not well defined, even today. And
often they rely on a packaging review, or some tool not so well know
to everyone.

It is not efficient, but it works somehow.


Best regards
>
> The current means of detection is left to (mostly) casual inspection, and
> the current means of enforcement (mostly) is left to rather energetic
> negotiations on e-mail lists and (likely, I don't know) irc channels.
>
> hth
>
> 73 de Jeff
>
>> --
>> Denis Silakov, ROSA Laboratory.
>> www.rosalab.ru
>>
>>
>
>

Reply via email to