public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sven Rebhan <odinshorse@googlemail.com>
To: gentoo-embedded@lists.gentoo.org
Subject: [gentoo-embedded] Reorganization of Overlay
Date: Fri, 4 Sep 2009 21:44:50 +0200	[thread overview]
Message-ID: <3dc1583f0909041244g3a7f3f86l4f4d2d3dd45098c6@mail.gmail.com> (raw)

Hello everybody,

after a nice dicussion with viridior in #neuvoo, we came up
with the following proposal for reorganizing the current
embedded overlay at overlays.gentoo.org.
The new tree should look like this:


embedded overlay
  |
  +- cross-fixes
  |   |
  |   +- python (dev-lang/python)
  |   |
  |   +- perl (dev-lang/perl)
  |   |
  |   +- ...
  |
  |
  +- profiles
  |   |
  |   +- armv4tl (profiles/embedded/armv4tl)
  |   |  |
  |   |  +- openmoko (profiles/embedded/armv4tl/openmoko)
  |   |
  |   +- armv7a (profiles/embedded/armv4tl)
  |      |
  |      +- pandora (profiles/embedded/armv7a/pandora)
  |
  +- common
  |   |
  |   +- openmoko-sources (sys-kernel/)
  |   |
  |   +- openmoko-mplayer (media-video/)
  |   |
  |   +- pandora-sources (sys-kernel/)
  |   |
  |   +- sys-mobilephone
  |   |
  |   +- ...
  |
  +- docs
  |
  +- enlightenment (temporary until submitted to respective overlay or upstream)


Right now only, openmoko ppl contribute there, which we
would like to change. The enlightenment tree will
hopefully go into the respective overlay soon and will be
removed afterwards. The split into cross- and native trees
should ensure that experimental cross-compile fixes don't
disturb others work.

What do you guys think? If you are ok with it, I'll go
forward and restructure the tree during the next week.

Best regards and thanks to viridior for the
constructive discussion!

    Sven 'sleipnir' Rebhan



                 reply	other threads:[~2009-09-04 14:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3dc1583f0909041244g3a7f3f86l4f4d2d3dd45098c6@mail.gmail.com \
    --to=odinshorse@googlemail.com \
    --cc=gentoo-embedded@lists.gentoo.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