All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: packages versioning
Date: Fri, 09 Dec 2011 18:57:15 +0000	[thread overview]
Message-ID: <4EE25A0B.7070309@googlemail.com> (raw)
In-Reply-To: <4EE23411.2060907@windriver.com>


> The creation of the filesystem image is driven by a number of 
> components. Basically it works like this:
Thanks a lot for that - a good insight into the workings of oe and 
bitbake. I was hoping there would be an easier way to configure/change 
this to what I want, but I see that it is much more complex than I 
thought initially.

> I have a spreadsheet (OpenOffice 17k, or Excel 81k) that lists all of 
> the current breakdowns.  If you are interested send me an email off list.
I am interested (excel would be nice, thanks), but don't know your email 
address (all I get when responding to 'all' is the mailing list email 
address) - if you know mine, you could send me that and I'll have a look.

I take it there isn't an easy way to see the hierarchy of all 
packages/dependencies involved in a particular image, is it (your 
spreadsheet may be good, but I suppose it is static and reflects just a 
current snapshot of a given packages/dependencies and that might change)?

If all else fails, I might use ipkg on the target system to uninstall 
the packages I don't need and install new ones - not ideal by any means, 
but this is what I'll do only as a last resort, if all else fails. 
Thanks again for the thorough response!




  reply	other threads:[~2011-12-09 19:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09  2:57 packages versioning Mr Dash Four
2011-12-09  3:17 ` Chris Larson
2011-12-09 12:59   ` Mr Dash Four
2011-12-09 13:35     ` Koen Kooi
2011-12-09 15:59       ` Mr Dash Four
2011-12-09 16:15         ` Mark Hatle
2011-12-09 18:57           ` Mr Dash Four [this message]
2011-12-09 19:06             ` Gary Thomas
2011-12-09 20:14             ` Mark Hatle
2011-12-09 20:46               ` Mr Dash Four
2011-12-10 18:29   ` Mr Dash Four

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=4EE25A0B.7070309@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --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.