Hey,

> Ok, getting dependencies "right by default" is as good a reason as any
> to support it the conceptual idea (among other because strictly-equal
> version dependencies are fine between same-source binaries).

great, that you understand what I want and why this is helpful. I have often 
problems describing my problem for others.

>   However, I am not going to fiddle with debian/shlibs.local because it
> is fragile and it would break horribly if people need that file for
> other reasons (plus it would complicating clean up).
> 
> So a prerequisite for this is that dpkg-shlibdeps support multiple
> shlibs.local files. @Guillem: What is your take on this bit?  Preference
> order would be "d/shlibs.local", "file(s) passed via this new option",
> <whatever the remaining preference order was before>.
>   If it is any easier, I am also fine with the option neutering
> d/shlibs.local as long as I can pass multiple files (so I can emulate it
> with the option).

I like your proposed solution, to be able to fix it in dpkg-shlibdeps . And 
this should be more robust than our solution with regexing in debian/
*.substvars. Also we need to think about Architecture:all/any dependency that 
are not handled correctly with our solution.

hefee

Attachment: signature.asc
Description: This is a digitally signed message part.

Reply via email to