All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@debian.org>
To: openembedded-devel@lists.openembedded.org
Cc: openembedded-devel@openembedded.org
Subject: Re: Machine config generator (FOSDEM idea)
Date: Fri, 13 Feb 2009 13:39:32 -0200	[thread overview]
Message-ID: <87r622firv.fsf@neumann.lab.ossystems.com.br> (raw)
In-Reply-To: <200902131525.34787.openembedded@haerwu.biz> (Marcin Juszkiewicz's message of "Fri, 13 Feb 2009 15:25:33 +0100")

Marcin Juszkiewicz <openembedded@haerwu.biz> writes:

> Hi
>
> I was talking during FOSDEM with some developers and one of things which 
> I was asked about was 'how to create machine config' (usually question 
> was other but had this sense).
>
> OE developers usually know that machine config is simple but tell that 
> to Joe Random who only knows that his board use s3c2443 etc. So idea was 
> to create simple few steps wizard which will ask few questions and 
> produce machine config as result. More work would be required on 
> creating kernel recipe because kernel can be from svn/cvs/git or tarball 
> + quilt patchset etc...
>
> Thats only beginning of idea - I hope that someone will provide 
> feedback.

I see the pros for it but I also think it will not help too much; the
most difficult problem is to understand OE as a whole and how the
packages can affect each other.

It takes a while to identify the failures and to cook up a fix for those
problems.

What will be the use of a machine definition without a kernel config for
it? And let's be real, if the person knows how to compile the kernel for
it then I'm absolute sure that the machine definition won't be problem.

What I do think could be useful is a more detailed set of "Quick Start
Guide" having one for each really common task. The set of tasks I
believe are common for regular users are:

 - adding a new package version
 - adding a new package
 - creating a distribution based in another
 - adding a new machine

This small set solves 90% of problems people usually have and as a plus
help the end user to understand OE in more deep; as a bonus we can end
up having more people giving back the generated changes.

My 2c.

-- 
        O T A V I O    S A L V A D O R
---------------------------------------------
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
 you the whole house."



  parent reply	other threads:[~2009-02-13 15:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-13 14:25 Machine config generator (FOSDEM idea) Marcin Juszkiewicz
2009-02-13  9:57 ` Ken Gilmer
2009-02-13 15:04 ` Sledz, Steffen
2009-02-13 15:12 ` Ulf Samuelsson
2009-02-13 15:16 ` Yuri Bushmelev
2009-02-13 15:39 ` Otavio Salvador [this message]
2009-02-13 16:21 ` Phil Blundell
2009-03-03 17:02   ` GNUtoo

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=87r622firv.fsf@neumann.lab.ossystems.com.br \
    --to=otavio@debian.org \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.