Re: kde-sunset: gtk-engines-qt build failure

V. Ram wrote:
> I was able to get past this issue by using the attached patch that I
> created (hopefully it stays attached during distribution to the list).
> I'm running ~ Firefox 7 with this and the engine works.
>
> For anyone else that might struggle with the issue (until such time that
> this patch or similar get applied to the official kde-sunset repo), you
> can do the following:
>
> 1. In your kde-sunset repo copy (by default these days it would be in
> /var/lib/layman/kde-sunset), go to the x11-themes/gtk-engines-qt
> directory.
>
> 2. Copy the current .ebuild file to a new .ebuild, changing the r<X>  to
> your own version number, higher than the official version, e.g. r99.
> Complete example:
> /var/lib/layman/kde-sunset/x11-themes/gtk-engines-qt $ cp
> gtk-engines-qt-0.8-r4.ebuild gtk-engines-qt-0.8-r99.ebuild
>
> 3. Put the attached patch into the files subdirectory.  You can rename
> it if you like.
>
> 4. Edit the new .ebuild file created in step 2.  In the PATCHES=
> section, before the closing ")", add a new line following the format of
> the previous line.  The new line should read
> "${FILESDIR}/undef_signals_cpp.patch" (or if you decided to rename the
> patch, use your chosen filename).  Save and exit.
>
> 5. Legitimize the ebuild in the eyes of Portage.  At the command-line
> and still in the gtk-engines-qt dir, run "ebuild
> gtk-engines-qt-0.8-r99.ebuild digest" .
>
> 6. Now when you "emerge gtk-engines-qt", it should pick up your new
> local version and proceed successfully through compilation.  If not,
> perhaps the original ebuild was marked as testing (0.8-r4 is stable as
> of this writing, so this was not an issue for me), in which case you can
> keyword the package.
>
> 7. Remember that a sync operation can blow away these files.  Back up at
> least your .ebuild and patch file.  You may want to be more aggressive,
> and backup the whole
> /var/lib/layman/kde-sunset/x11-themes/gtk-engines-qt directory as well.
>
> I disclaim copyright on the patch since it's so trivial.
>
> V. Ram.
>

Maybe one of the kde sunset guys can apply the fix to the overlay too.  
Then everyone can use it without any hacking.

I suspect this will be done too.  They are good at this sort of thing.

Dale

:-)  :-)