Re: Symbol-based dependencies on shared libraries: some news
On Sat, Aug 04, 2007, Raphael Hertzog wrote:
> Knowing those differences, I wonder if I should offer the possibility to have
> debian/<package>.symbols.common that would complement what can be found in
> debian/<package>.symbols.<arch> or if we need something more elaborated like
> an include mechanism or a syntax to restrict a symbol on a set of architectures
> (like for dependencies in Build-Depends). Please give me your opinion on this.
I wish for an include mechanism! :)
I think this also makes sense when you have multiple flavors of the
same lib (for example libgtk versus libgtk-directfb).
Do you strip the "well known symbols" you've seen on each arch so that
one only has to specify the other symbols? Or will each maintainer
have to maintain one file per arch with arch specific symbols?