Want automatic workaround for conflicting files

[bkauler-2]

I'm doing a T2 build, thinking that it might be the basis for Puppy5.
Anyway, compiling stops (I have set it to stop on package fail in stage 5)
when 'librsvg' is compiled, as var/adm/flists/gtk+ has a line:

gtk+: etc/gtk-2.0/gdk-pixbuf.loaders

but librsvg has the same file. My manual fix is to edit
var/adm/flists/gtk+ and rename that line, to say:

gtk+: etc/gtk-2.0/gdk-pixbuf.loadersHIDE

...then restore it after librsvg has finished compiling and installing.

The thing is, it is really ok. librsvg reads the previous
gdk-pixbuf.loaders file, adds its own information.

So, how can I add an instruction in the pkg_librsvg.conf in my
target/puppy5, so that there is no fail? It's probably really easy to do,
I just can't see how.

Regards,
Barry Kauler



-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

[René Rebe]

Hi Barry,

nice to see you around!

On 06.04.2009, at 16:30, bkauler@... wrote:

> I'm doing a T2 build, thinking that it might be the basis for Puppy5.
> Anyway, compiling stops (I have set it to stop on package fail in  
> stage 5)
> when 'librsvg' is compiled, as var/adm/flists/gtk+ has a line:
>
> gtk+: etc/gtk-2.0/gdk-pixbuf.loaders
>
> but librsvg has the same file. My manual fix is to edit
> var/adm/flists/gtk+ and rename that line, to say:
>
> gtk+: etc/gtk-2.0/gdk-pixbuf.loadersHIDE
>
> ...then restore it after librsvg has finished compiling and  
> installing.
>
> The thing is, it is really ok. librsvg reads the previous
> gdk-pixbuf.loaders file, adds its own information.
>
> So, how can I add an instruction in the pkg_librsvg.conf in my
> target/puppy5, so that there is no fail? It's probably really easy  
> to do,
> I just can't see how.
>

I wonder why I do not see this conflict in our builds, strange.
Which T2 version / tree are you using?

Normally we solve such problems by modifying the packages not
to update such "cache" / "registration" files and instead run the
caching / registration at post-install time: that is after a classic
installer installation or the time a livecd / embedded system is
created and compressed.

--
   René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
   http://exactcode.de | http://t2-project.org | http://rene.rebe.name


-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

[bkauler-2]

>> I'm doing a T2 build, thinking that it might be the basis for Puppy5.
>> Anyway, compiling stops (I have set it to stop on package fail in
>> stage 5)
>> when 'librsvg' is compiled, as var/adm/flists/gtk+ has a line:
>>
>> gtk+: etc/gtk-2.0/gdk-pixbuf.loaders
>>
>> but librsvg has the same file. My manual fix is to edit
>> var/adm/flists/gtk+ and rename that line, to say:
>>
>> gtk+: etc/gtk-2.0/gdk-pixbuf.loadersHIDE
>>
>> ...then restore it after librsvg has finished compiling and
>> installing.
>>
>> The thing is, it is really ok. librsvg reads the previous
>> gdk-pixbuf.loaders file, adds its own information.
>>
>> So, how can I add an instruction in the pkg_librsvg.conf in my
>> target/puppy5, so that there is no fail? It's probably really easy
>> to do,
>> I just can't see how.
>>
>
> I wonder why I do not see this conflict in our builds, strange.
> Which T2 version / tree are you using?
>
> Normally we solve such problems by modifying the packages not
> to update such "cache" / "registration" files and instead run the
> caching / registration at post-install time: that is after a classic
> installer installation or the time a livecd / embedded system is
> created and compressed.
>
> --
>    René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
>    http://exactcode.de | http://t2-project.org | http://rene.rebe.name
>

Rene,
I got it from trunk, cvs on 4th April.

I have always had this problem, and always solved it manually. Right back
in December 2007 when I built the base packages for Puppy 4.00, I
documented the problem and the manual solution on this web page:

http://www.puppylinux.com/pfs/

...look down the page to "Step 6B". Note, the other two problems reported
on that page are no longer occurring.

Regards,
Barry Kauler



-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

[bkauler-2]

>
>>> I'm doing a T2 build, thinking that it might be the basis for Puppy5.
>>> Anyway, compiling stops (I have set it to stop on package fail in
>>> stage 5)
>>> when 'librsvg' is compiled, as var/adm/flists/gtk+ has a line:
>>>
>>> gtk+: etc/gtk-2.0/gdk-pixbuf.loaders
>>>
>>> but librsvg has the same file. My manual fix is to edit
>>> var/adm/flists/gtk+ and rename that line, to say:
>>>
>>> gtk+: etc/gtk-2.0/gdk-pixbuf.loadersHIDE
>>>
>>> ...then restore it after librsvg has finished compiling and
>>> installing.
>>>
>>> The thing is, it is really ok. librsvg reads the previous
>>> gdk-pixbuf.loaders file, adds its own information.
>>>
>>> So, how can I add an instruction in the pkg_librsvg.conf in my
>>> target/puppy5, so that there is no fail? It's probably really easy
>>> to do,
>>> I just can't see how.
>>>
>>
>> I wonder why I do not see this conflict in our builds, strange.
>> Which T2 version / tree are you using?
>>
>> Normally we solve such problems by modifying the packages not
>> to update such "cache" / "registration" files and instead run the
>> caching / registration at post-install time: that is after a classic
>> installer installation or the time a livecd / embedded system is
>> created and compressed.
>>
>> --
>>    René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
>>    http://exactcode.de | http://t2-project.org | http://rene.rebe.name
>>
>
> Rene,
> I got it from trunk, cvs on 4th April.
>
> I have always had this problem, and always solved it manually. Right back
> in December 2007 when I built the base packages for Puppy 4.00, I
> documented the problem and the manual solution on this web page:
>
> http://www.puppylinux.com/pfs/
>
> ...look down the page to "Step 6B". Note, the other two problems reported
> on that page are no longer occurring.
>

Ah, I think I know why you don't have the problem.

I set gnome apps to install to prefix /usr.

Using /opt (or whatever) for gtk+ probably confuses librsvg and you
probably end up with two 'gdk-pixbuf.loaders' files in two different
places.

When configuring T2, I set as much as possible to '/usr' prefix, in line
with most distros these days. Unfortunately I can't do this with Xorg --
would really like to. One thing I would like is a global setting to put
everything in /usr.

Regards,
Barry Kauler



-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2

[bkauler-2]

>
>>> I'm doing a T2 build, thinking that it might be the basis for Puppy5.
>>> Anyway, compiling stops (I have set it to stop on package fail in
>>> stage 5)
>>> when 'librsvg' is compiled, as var/adm/flists/gtk+ has a line:
>>>
>>> gtk+: etc/gtk-2.0/gdk-pixbuf.loaders
>>>
>>> but librsvg has the same file. My manual fix is to edit
>>> var/adm/flists/gtk+ and rename that line, to say:
>>>
>>> gtk+: etc/gtk-2.0/gdk-pixbuf.loadersHIDE
>>>
>>> ...then restore it after librsvg has finished compiling and
>>> installing.
>>>
>>> The thing is, it is really ok. librsvg reads the previous
>>> gdk-pixbuf.loaders file, adds its own information.
>>>
>>> So, how can I add an instruction in the pkg_librsvg.conf in my
>>> target/puppy5, so that there is no fail? It's probably really easy
>>> to do,
>>> I just can't see how.
>>>
>>
>> I wonder why I do not see this conflict in our builds, strange.
>> Which T2 version / tree are you using?
>>
>> Normally we solve such problems by modifying the packages not
>> to update such "cache" / "registration" files and instead run the
>> caching / registration at post-install time: that is after a classic
>> installer installation or the time a livecd / embedded system is
>> created and compressed.
>>
>> --
>>    René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
>>    http://exactcode.de | http://t2-project.org | http://rene.rebe.name
>>
>
> Rene,
> I got it from trunk, cvs on 4th April.
>
> I have always had this problem, and always solved it manually. Right back
> in December 2007 when I built the base packages for Puppy 4.00, I
> documented the problem and the manual solution on this web page:
>
> http://www.puppylinux.com/pfs/
>
> ...look down the page to "Step 6B". Note, the other two problems reported
> on that page are no longer occurring.
>

Ah, I think I know why you don't have the problem.

I set gnome apps to install to prefix /usr.

Using /opt (or whatever) for gtk+ probably confuses librsvg and you
probably end up with two 'gdk-pixbuf.loaders' files in two different
places.

When configuring T2, I set as much as possible to '/usr' prefix, in line
with most distros these days. Unfortunately I can't do this with Xorg --
would really like to. One thing I would like is a global setting to put
everything in /usr.

Regards,
Barry Kauler



-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
lists@... with a subject of: unsubscribe t2