All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John Willis" <John.Willis@Distant-earth.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [RFC/PATCH] Add support for XFCE 4.6.1.
Date: Sun, 25 Oct 2009 12:02:01 -0000	[thread overview]
Message-ID: <044c01ca556a$f6f3af20$e4db0d60$@Willis@Distant-earth.com> (raw)

I have added support to XFCE 4.6.1 to OpenEmbedded in a branch I am hosting
at 

http://git.openpandora.org/cgi-bin/gitweb.cgi?p=openembedded.git;a=shortlog;
h=xfce46-support

This is based on the earlier patchset I sent to the list and some feedback
Koen and Corsac (Debian's XFCE maintainer) provided. 
I have tested images made from the 2 new tasks on some of my OMAP3 boards
and all seems well.

For now it adds an xfce46.bbclass to support the builds and lives alongside
of XFCE 4.4 but in fairness I would like to propose dropping XFCE 4.4.* from
dev (and leaving it in stable/2009 for now).

I have also taken the liberty of renaming xfce to xfce-base and adding an
xfce-extras folder to house the non-core apps (gigolo, squeeze,
xfce4-notifyd, that sort of thing). I would also like to clean up the XFCE
recipes scattered around the tree but that has a bearing on if XFCE 4.4
remains supported in-tree.

Any comments?

Regards,

John

--

> What is a grue?

The grue is a sinister, lurking presence in the dark places of the earth.
Its favourite diet is adventurers, but its insatiable appetite is tempered
by its fear of light. No grue has ever been seen by the light of day, and
few have survived its fearsome jaws to tell the tale.







             reply	other threads:[~2009-10-25 12:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-25 12:02 John Willis [this message]
     [not found] <44440.3488342234$1256472302@news.gmane.org>
2009-10-25 13:29 ` [RFC/PATCH] Add support for XFCE 4.6.1 Koen Kooi

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='044c01ca556a$f6f3af20$e4db0d60$@Willis@Distant-earth.com' \
    --to=john.willis@distant-earth.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.