On Tue, 2014-12-09 at 11:41 +0100, Łukasz Stelmach wrote:
> It was <2014-12-08 pon 17:01>, when Patrick Ohly wrote:
> > I think what you show here is that gbs has some overrides that prefer
> > locally-built packages over remote ones. That part is working.
>
> That's the point. It works just fine. (So why replace it?)
We still seem to have a misunderstanding about the problem. See below.
It doesn't matter much, because this would be just a small improvement
over gbs and certainly not important enough to switch.
> > It is more problematic to install the resulting .rpm on a real image. At
> > least I always end up with several trial-and-error runs involving
> > --install vs. --upgrade, with and without --replacefiles --replacepkgs.
>
> --local-pkgs-path=${HOME}/GBS-ROOT/local/repos/tizen_common/armv7l/RPMS
I am talking about installing packages with rpm after copying .rpm files
to the target. rpm doesn't have this --local-pkgs-path. It's probably a
gbs thing (I checked gbs --help, but that doesn't show all options, so I
am not sure).
> > Some things that MIC does (loop-mounting the disk image to partition and
> > format it) require root privileges and thus cannot be done in recipes.
>
> So how does yocto create images without mounting files via loopback?
> There are no etools like mtools to copy files to ext filesystems. I've
> been grepping yocto for a while and I couldn't sport the script that
> creates image files.
As far as I know, ext3 tools work with plain files. Yocto uses wic to
create images, see poky/scripts/wic and
http://www.yoctoproject.org/docs/current/mega-manual/mega-manual.html#creating-partitioned-images
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev
