All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Schuster <theBohemian@gmx.net>
To: Using OE <openembedded-users@lists.openembedded.org>,
	 openembedded-devel@lists.openembedded.org
Subject: add midpath 0.3 soon and then dump midpath 0.1
Date: Thu, 08 May 2008 14:43:27 +0200	[thread overview]
Message-ID: <4822F56F.4010304@gmx.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

Hi,
I was helping Guillaume Legris with their build script. This work will
make it trivial to write proper recipes in OE.

I would like to include MIDPath 0.3 when it is released and get rid of
version 0.1. The reason is that the midpath recipes are effectively
rewriting the its build system and are a nightmare to maintain. This
would be worse when we have eg. midpath-cldc_0.1 and midpath-cldc_0.3
which would look very different.

Please speak out loudly if you are against removing midpath 0.1 from the
development branch of OE (I will move the 0.1 recipes (and patches) to
obsolete/ first, of course.).

Btw: There are midpath 0.2 recipes in our Jalimo overlay. I did not
manage to merge those into OE because they are also very complicated
(but more structured) and I could not get agreement on removing 0.1 for
them. The good news is that the things I learned while doing the 0.2
recipes have been applied when changing the upstream build script. So
from 0.3 on it will be much easier to maintain midpath recipes.

Regards
Robert


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

             reply	other threads:[~2008-05-08 12:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-08 12:43 Robert Schuster [this message]
2008-05-08 14:48 ` add midpath 0.3 soon and then dump midpath 0.1 Henning Heinold

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=4822F56F.4010304@gmx.net \
    --to=thebohemian@gmx.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-users@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.