« Return to Thread: Want automatic workaround for conflicting files

Re: Want automatic workaround for conflicting files

by Rene Rebe :: Rate this Message:

Reply to Author | View in Thread

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

 « Return to Thread: Want automatic workaround for conflicting files