All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael 'Mickey' Lauer <mickey@vanille-media.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Questions regarding DISTRO = "minimal"
Date: Wed, 08 Jul 2009 08:20:15 +0200	[thread overview]
Message-ID: <1247034015.4669.25.camel@opal> (raw)
In-Reply-To: <200907021504.13248.holger+oe@freyther.de>

Hi Holger,

> I'm currently toying with creating a "minimal" uclibc image and while using 
> minimal-uclibc I got several questions in #oe along the line claiming 
> "minimal" is current unmaintained.

Not really, it's just falling under my temporary (until we have a TSC in
place) org.oe.dev boycott.

> I have some questions to help me building a opinion regarding "minimal". What 
> is the differentiation between minimal and micro, minimal and angstrom. What 
> niche is minimal trying to solve? And is minimal the right name for it?

Here's the story:

First, there was the "generic" distro -- an attempt to create a simple
distro config that builds for a few very common targets without
including too many policies, so that people could understand it and use
it as a starting point when they felt the need to create an own distro
config.

Alas, people misunderstood that, thinking that 'generic' meant it would
build for all targets and complained. To make it more clear that it was
about a minimal amount of distro policies, it had been renamed to
'minimal' (sic!).

A bit later, when Angstrom started to become the best maintained distro
in OE, I was worrying about the quality of our metadata. Angstrom
included many configurations that hided actual bugs in our metadata
(such as inconsistent versioning and bogus default providers etc.)
At some point of time, before Angstrom would be the _only_ distro that
built in OE (thus compromising an important distinction), I took the
plunge and refactored many (good) settings from Angstrom into generic
include and configuration files, so that all distros would benefit from
the toolchain knowledge that went into Angstrom.

There was the hope that eventually the Angstrom folks would realize the
benefit of that and would also move to more reusable config files. Alas,
due to the social problems in our community this didn't happend and will
probably never.

The question now is how do we move from here? We could rename minimal
back to generic -- in fact that's what it was for right from the start.

Whatever we decide on, it's important that we do not rely on one distro
to rule them all -- this will inevitably lower the metadata quality
hence the usability of OE.

Cheers,

:M:




  parent reply	other threads:[~2009-07-08  6:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02 13:04 Questions regarding DISTRO = "minimal" Holger Hans Peter Freyther
2009-07-02 18:34 ` Phil Blundell
2009-07-08  6:20 ` Michael 'Mickey' Lauer [this message]
2009-07-08  8:09   ` Graeme Gregory
2009-07-08 11:30     ` Philip Balister
2009-07-08 16:04     ` Michael 'Mickey' Lauer
2009-07-08 12:10   ` Rolf Leggewie
2009-07-08 14:03   ` Phil Blundell
2009-07-08 16:05     ` Michael 'Mickey' Lauer

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=1247034015.4669.25.camel@opal \
    --to=mickey@vanille-media.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 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.