Comment 42 for bug 312898

@Reinhard: i now tried it without the unstripped package and i am able to compile the plugin (even though i haven't tested it yet). but i had to trick the configure script so it the if conditions regarding checking for the non free codec in avcodec simply always says yes to compiling it, this of course means the check doesn't go on with the stripped one. for more details i can send you the specific part of the configure script or you grab it from the opal package under plugins (HAVE_H263P is the magic word), but so far it seems you're not doing things very insane ;) i also found an alternative for my case as the discrete plugin directories have make files in them, so i just need to call make directly there and don't have to care about forcing configure's decision. so thank you very much for helping me to understand the whole issue, as i am now able to do the packages on Soyuz :)

@all: to clarify this all means even if the software we compile or package needs the unstripped packages at runtime, it don't or shouldn't need them when compiling. so we only need to make sure the configure stuff doesn't disable compiling of the needed features because we have the stripped packages installed at compiling/building or we have to compile them "manually" some how. for packagers this means you need the dev packages at build-depends and the unstripped at the normal depends in debian/control, so you make sure you at least have the unstripped stuff at runtime.

great i finally got it :) but i would still feel comfortable with letting the dev package optionally depend on the unstripped libs, in case this won't make any unintended troubles.