From: "\"Andreas Müller\"" <Schnitzeltony@gmx.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: xfwm4 themes from xfwm4-themes are not packed
Date: Thu, 11 Feb 2010 15:59:55 +0100 [thread overview]
Message-ID: <20100211145955.234260@gmx.net> (raw)
In-Reply-To: <008001caab15$c1fe4590$45fad0b0$@Willis@Distant-earth.com>
Dear John,
I got your new recipe and did bake
- with xfwm4-themes -> OK all themes could be found on target
- with specific xfwm4-theme-* -> OK only the selected themes appear in rootfs
- (minor issue & related to xfwm4 I think) with xfwm4-theme-foo: No complain..
Thanks a lot for quick mending!
Andreas
-------- Original-Nachricht --------
> Datum: Thu, 11 Feb 2010 12:28:44 -0000
> Von: "John Willis" <John.Willis@Distant-earth.com>
> An: openembedded-devel@lists.openembedded.org
> Betreff: Re: [oe] xfwm4 themes from xfwm4-themes are not packed
> Dear Andreas,
>
> > > I created a recipe for xfce/xfwm4/slim. After everything working fine
> > > so far, I tried to make it more colorful and check the xfwm4-themes.
> > > Doing so, I had to realize that all the themes coming from xfwm4-
> > > themes(-4.6.0) are not packed and are not found in rootfs
> > > /usr/share/themes. The themes included in xfwm4 can be found.
> >
> > Most of the Xfce 4.6.* work was done by myself and while I have not
> > encountered any issues with the themes for the Xfce Window Manager I
> > can see
> > after reviewing the recipes that there is some room for improvement in
> > the
> > xfwm4-themes recipe (your quite right, it's not working as it should
> > and is
> > also not very clever).
>
> To follow up on this I have done some quick refactoring of
> recipes/xfce-base/xfwm4-themes_4.6.0.bb and published the results to my
> tree
> at
> http://git.openpandora.org/cgi-bin/gitweb.cgi?p=openembedded.git;a=shortlog;
> h=op.openembedded.dev (Your already familiar with the OP trees so I assume
> you will have no issues cherry picking off the commit).
>
> The package now packs up all 80+ :-o XFWM4 extra themes correctly and also
> creates a xfwm4-themes meta package that depends on all the themes.
>
> This means that you can now add any one of the 80 odd themes to your image
> explicitly or (better) just add xfwm4-themes to your image to have it drag
> in every extra theme that is not part of the xfwm4 core package.
>
> If you could test this and report back I would appreciate it, assuming all
> looks ok I'll request this patch is pushed into OE mainline.
>
> Regards,
>
> John
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
prev parent reply other threads:[~2010-02-11 15:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 20:26 xfwm4 themes from xfwm4-themes are not packed Müller, Andreas
2010-02-10 21:05 ` John Willis
2010-02-11 8:29 ` Müller, Andreas
2010-02-11 8:39 ` Koen Kooi
2010-02-11 8:43 ` Müller, Andreas
2010-02-11 9:50 ` John Willis
2010-02-11 10:02 ` "Andreas Müller"
2010-02-11 12:28 ` John Willis
2010-02-11 14:59 ` "Andreas Müller" [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100211145955.234260@gmx.net \
--to=schnitzeltony@gmx.de \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox