Re: [RFC] Fix udev pulling in libvolume-id-dev

[Koen Kooi <k.kooi@student.utwente.nl>]

On 15-01-09 20:20, Tom Rini wrote:
> On Thu, Jan 15, 2009 at 10:53:50AM -0800, Khem Raj wrote:
>> On Thu, Jan 15, 2009 at 3:10 AM, Koen Kooi<k.kooi@student.utwente.nl>  wrote:
>>> On 15-01-09 08:41, Khem Raj wrote:
>>>> On (15/01/09 07:56), Koen Kooi wrote:
>>>>> On 15-01-09 07:14, Denys Dmytriyenko wrote:
>>>>>
>>>>>> libvolume-id-dev does not provide the actual .so library, but it
>>>>>> contains a
>>>>>> symlink in /usr/lib, which points to /lib/libvolume.so.0 (the host one!)
>>>>>> instead of ../../lib/ one...
>>>>> That's the intended behaviours, since installing the packages will have
>>>>> it point to ${libdir}/libvolume.so.0 on your device. I'm not sure if we
>>>>> want to patch every package to use relative symlinks.
>>>> We would use -dev packages on staged area normally to compile other apps
>>>> depending on a given packge if we do not fix the symlink I think it will
>>>> try to link to wrong library.
>>> We don't use the -dev packages to populate staging :) I keep trying to
>>> convince Richard that we should use them, but he keeps coming up with good
>>> reasons not to do so :)
>> Hmm then why do we generate them ?. We do not need these packages on
>> target unless we switch to
>> native development on target.
>
> SDKs, which oddly DO let you do development vs them, so any problem
> stopping us from using them for staging is a problem here.  But that's
> all part of another thread RP and I need to start.  Or one of us does,
> at least.

You need things as shlib providers and stamps as well for 
packaged-staging, so using only -dev packages is only part of the solution.

regards,

Koen