static libraries' policy

[Dmitry Butskoy]

Tom 'spot' Callaway wrote:

>Right now, there is not a "no static libs permitted" policy. The policy
>states that they should be avoided wherever possible. I could change
>this to a "no static libs unless you have a darned good reason, which
>you will need to document in the spec file" policy, since some apps are
>just too dumb to work with out them (unless the maintainer is willing to
>do what amounts to their own fork of the code).
>
>The consensus that I'm hearing here is that a policy change would be
>welcomed for FC5+, does anyone dissent?
>  
>
Do you mean "after FC5 will be released" ?

Is it correlate with Core's state (where a half of such packages are not 
changed too) ?


~buc