public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: any way to list *all* possible sources across the current layers?
Date: Mon, 11 Feb 2013 13:22:18 +0000	[thread overview]
Message-ID: <1360588938.6793.60.camel@ted> (raw)
In-Reply-To: <20130210123255.51643nyx1esfqeck@crashcourse.ca>

On Sun, 2013-02-10 at 12:32 -0500, Robert P. J. Day wrote:
>    hoping this question makes sense -- i use own-mirrors.bbclass to point
> at a sizable directory of tarballs (almost 12G worth) that i've been
> collecting over many months and, after every OE layer upgrade, whatever
> newer sources are pulled in, will generate the corresponding tarball and
> i'll copy that into my tarballs directory.
> 
>    predictably, at this point, there's a *lot* of old, irrelevant cruft in
> that directory, but i know of no automated way to get rid of any of it.
> for instance, i currently have five versions of automake (1.11.2, 1.12.1,
> 1.12.3, 1.12.5 and 1.12.6) taking up space.  doesn't hurt, of course, but
> it would be handy to be able to generate a list of all possible,
> potentially necessary versions of a source -- that is, any version for
> which any recipe still lists it as PREFERRED_VERSION.
> 
>    does that make sense?  obviously, that would have to be done in the
> context of a given set of layers and all the corresponding recipes in
> those layers.  is there a way to do that already?  if not, i'm sure i
> could whip up a simple script that would do the job.  thanks.

The original idea was that you could do a "bitbake world -c fetch" and
it would touch the .done stamps of anything it used in DL_DIR.

You could then age out entries in there based on the timestamp of
the .done files.

I appreciate there is an issue with some files not being pulled in by
do_fetchall at the moment. I have some ideas related to that which would
fix it but haven't written the code yet, hopefully will get there soon. 

Cheers,

Richard




      parent reply	other threads:[~2013-02-11 13:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10 17:32 any way to list *all* possible sources across the current layers? Robert P. J. Day
2013-02-10 22:10 ` Chris Larson
2013-02-11 13:22 ` Richard Purdie [this message]

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=1360588938.6793.60.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=rpjday@crashcourse.ca \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox