[maemo-developers] Autobuilder problem with optified library

From: Julius Luukko julle.luukko at quicknet.inet.fi
Date: Tue Oct 20 11:12:56 EEST 2009
Marius Vollmer wrote:
> ext Faheem Pervez <trippin1 at gmail.com> writes:
>> On Tue, Oct 20, 2009 at 7:03 AM, Marius Vollmer
>> <marius.vollmer at nokia.com> wrote:
>>> ext Yves-Alexis Perez <corsac at debian.org> writes:
>>>> On lun., 2009-10-19 at 22:26 +0300, Kamen Bundev wrote:
>>>>> Well, on the device and probably in autobuilder the /opt folder is
>>>>> actually a symlink to /home/opt... On the other hand maemo-optify
>>>>> produces direct /opt folder.
>>>> That's the problem, dpkg won't replace a symlink by a real folder.
>>> If that would be true, wouldn't all optified packages be broken in the
>>> same way?  They clearly aren't, so something else must be going on...
>> The difference here is that these optified packages are being
>> installed as a build dependency of something else.
> The difference is that they are installed into the build environment and
> not into a N900.
> But the point being made was that the buildbot and the N900
> _both_ have the /opt -> /home/opt symlink and that this symlink is
> causing dpkg to not install a optified package.  That can't be true.
> There clearly is something different about the buildbot which is causing
> trouble, but it doesn't look like it is dpkg having trouble with
> symlinks and directories.
> _______________________________________________

FWIW I call maemo-optify with

maemo-optify libgtkextra-x11-2.0-1

since I only want to optify the library, not the development files. But 
this shouldn't make any difference to the optification, should it?

More information about the maemo-developers mailing list