static libraries' policy: possible solution

[Florian La Roche]

> I'll restate my question.  Can the client side tools available to
> developers be re-engineered or supllimented to make it possible to
> rebuild the static libraries locally and keep them updated locally as
> official updates come down the line. I'm not talking about what the
> limitations are for existing tools.  I'm asking is it worth modifying
> client tools or creating additional tools to make it easier for
> developers who need statics to rebuild them locally and keep them
> updated through normal means, so developers will not have to exclude
> updates at all. Can tools be designed so library updates trigger local
> rebuilds of static subpackages?

You could add defines into spec files to add static libs, but such
things normally break soon and often stay broken unless you enable
this by default, but then decide to remove the package for the default
repo.

regards,

Florian La Roche