From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: "David Nyström" <david.nystrom@enea.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 00/49] Rootfs/image generation refactoring (cover letter only)
Date: Tue, 4 Feb 2014 17:34:16 +0200 [thread overview]
Message-ID: <20140204153414.GD5112@lpalcu-linux> (raw)
In-Reply-To: <52F0FDF5.8000603@enea.com>
On Tue, Feb 04, 2014 at 03:49:25PM +0100, David Nyström wrote:
>
> Oops, bug on my behalf in above example, but it still fails the same
> way when using a correct IPK_FEED_URI.
>
> IPK_FEED_URIS += " \
> all##file:///media/sdb5/repo/build/tmp/deploy/ipk/all \
> ${MACHINE}##file:///media/sdb5/repo/build/tmp/deploy/ipk/${MACHINE} \
>
> ${TARGET_ARCH}##file:///media/sdb5/repo/build/tmp/deploy/ipk/${TARGET_ARCH}
> \
> "
Ok, I succeeded to check this in master. Apparently, I understood this
wrong. In my tests I was deleting the tmp/ and sstate-cache/ and I was
not expecting the target packages to be re-built. It turns out that this
entire process takes place but when the rootfs is created, the provided
feeds are used... I learned something new today! :)
Regarding the refactored code, indeed, it does not work in this case. It
always tries to create the index files in the deploy/ipk directory
before continuing with the rootfs creation. I guess a condition should
be added in the new code to check for BUILD_IMAGES_FROM_FEEDS and skip
the index creation step... Shouldn't be hard to fix.
laurentiu
next prev parent reply other threads:[~2014-02-04 15:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 11:38 [PATCH 00/49] Rootfs/image generation refactoring (cover letter only) Laurentiu Palcu
2014-02-03 11:54 ` Laurentiu Palcu
2014-02-03 14:32 ` David Nyström
2014-02-03 16:47 ` Laurentiu Palcu
2014-02-04 14:08 ` David Nyström
2014-02-04 14:49 ` David Nyström
2014-02-04 15:34 ` Laurentiu Palcu [this message]
2014-02-04 15:40 ` David Nyström
2014-02-05 10:07 ` [PATCH v2 00/50] " Laurentiu Palcu
2014-02-05 10:58 ` David Nystrom
2014-02-05 12:09 ` David Nyström
2014-02-05 14:43 ` Laurentiu Palcu
2014-02-05 18:00 ` David Nystrom
2014-02-05 15:05 ` [PATCH v3 00/51] " Laurentiu Palcu
2014-02-10 7:53 ` [PATCH v4 00/52] " Laurentiu Palcu
2014-02-10 12:15 ` [PATCH v5 00/53] " Laurentiu Palcu
2014-02-11 8:42 ` David Nyström
2014-02-11 8:50 ` Laurentiu Palcu
2014-02-11 8:56 ` David Nyström
2014-02-11 9:36 ` David Nyström
2014-02-11 14:33 ` David Nyström
2014-02-11 14:50 ` David Nyström
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=20140204153414.GD5112@lpalcu-linux \
--to=laurentiu.palcu@intel.com \
--cc=david.nystrom@enea.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox