On 04/17/2012 09:12 AM, Darren Hart wrote:
>
>
> On 04/17/2012 06:19 AM, Richard Purdie wrote:
>> On Mon, 2012-04-16 at 20:32 -0700, Darren Hart wrote:
>>> I'm trying to address a symlink naming issue in the bzip2 package when
>>> used with Chrome. Chrome is looking for a specific soname, which
On 04/17/2012 06:19 AM, Richard Purdie wrote:
> On Mon, 2012-04-16 at 20:32 -0700, Darren Hart wrote:
>> I'm trying to address a symlink naming issue in the bzip2 package when
>> used with Chrome. Chrome is looking for a specific soname, which the
>> default install of bzip2 doesn't setup. I can
On Tue, 2012-04-17 at 10:32 +0100, Paul Eggleton wrote:
> On Monday 16 April 2012 20:32:25 Darren Hart wrote:
> > I'm trying to address a symlink naming issue in the bzip2 package when
> > used with Chrome. Chrome is looking for a specific soname, which the
> > default install of bzip2 doesn't setu
On Mon, 2012-04-16 at 20:32 -0700, Darren Hart wrote:
> I'm trying to address a symlink naming issue in the bzip2 package when
> used with Chrome. Chrome is looking for a specific soname, which the
> default install of bzip2 doesn't setup. I can address this easily by
> adding the symlink via a bzi
On Monday 16 April 2012 20:32:25 Darren Hart wrote:
> I'm trying to address a symlink naming issue in the bzip2 package when
> used with Chrome. Chrome is looking for a specific soname, which the
> default install of bzip2 doesn't setup. I can address this easily by
> adding the symlink via a bzip2
I'm trying to address a symlink naming issue in the bzip2 package when
used with Chrome. Chrome is looking for a specific soname, which the
default install of bzip2 doesn't setup. I can address this easily by
adding the symlink via a bzip2 bbappend in do_install_append().
Unfortunately, this fails