All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Sokolovsky <pmiscml@gmail.com>
To: "Nelson Castillo" <nelson@emqbit.com>
Cc: Stefano Parusso <stefano@ir3arp.net>,
	openembedded-devel@lists.openembedded.org
Subject: Re: Stable versions of OE
Date: Mon, 29 Jan 2007 22:20:27 +0200	[thread overview]
Message-ID: <1618752295.20070129222027@gmail.com> (raw)
In-Reply-To: <2accc2ff0701290940nbdceb0dkf25db7ea19826895@mail.gmail.com>

Hello Nelson,

Monday, January 29, 2007, 7:40:11 PM, you wrote:

> Hi.

> I've been following this document
> (http://wiki.emqbit.com//openembedded)
> by Stefano Parusso that explains how to build OE for a ARM board[1].

> It works for the snapshot for November the 7th and not for the most recent
> one. I read in the Getting Started wiki page[3]:

>   Once you have a "known good" version that works well on your
>   system, keep it! To update, clone a new copy; don't overwrite
>   that working version until it's known to be safe.

> So, I guess it means I should stay with the old metadata.

> My questions are:

>   * Does OE ever do "stable" releases?

    OE is a kind of "meta-distribution". To the large part, it leaves
definition of what is stable to specific distributions which are based
on it.

>   * If not, how do you make "stable" releases for yur plataforms?

    By creating branches for specific distributions. For example,
there's a branch for OpenZaurus. As OE uses distributed SCM, you more
or less easily can create and maintain your own private branch, merge
to it from .dev only what you consider stable for you. Even without
creating branch, you can get reasonable level of stability by
pinpointing versions of packages you like to use (in this case you
however at least depend on those versions not being removed, and old
stuff is regularly cleaned up from .dev)

> Regards,
> Nelson.-



-- 
Best regards,
 Paul                            mailto:pmiscml@gmail.com




  parent reply	other threads:[~2007-01-29 20:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-29 17:40 Stable versions of OE Nelson Castillo
2007-01-29 19:26 ` Cliff Brake
2007-01-29 21:08   ` Holger Freyther
2007-01-29 20:20 ` Paul Sokolovsky [this message]
2007-01-29 22:13 ` Michael 'Mickey' Lauer
2007-01-30  4:03   ` Nelson Castillo

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=1618752295.20070129222027@gmail.com \
    --to=pmiscml@gmail.com \
    --cc=nelson@emqbit.com \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=stefano@ir3arp.net \
    /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.