[oe] [RFC] Fix udev pulling in libvolume-id-dev

[Denys Dmytriyenko]

On Thu, Jan 15, 2009 at 07:57:02PM +0100, Koen Kooi wrote:
> On 15-01-09 19:53, Khem Raj wrote:
>> On Thu, Jan 15, 2009 at 3:10 AM, Koen Kooi<k.kooi at 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 and as you say native development (which is getting quite popular with 
> the beagleboard folks).

Ok, I'm bringing up this old topic, because as was correctly stated, SKDs use 
-dev packages and if we don't fix the symlink pointing to /lib/libvolume.so.0, 
it breaks those SDKs. There is also another side-effect - libvolume-id-dev.ipk 
misses the automatic dependency on libvolume-id0.ipk so the SDK cannot just 
refer to the -dev package and expect the actual library to be installed. In 
that case only the broken link gets installed...

So, if nobody objects, I'm going to apply my first patch from this thread 
against the udev recipe, fixing .so symlink to be relative.

-- 
Denys