From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: yocto@lists.yoctoproject.org, dspore@parraid.com
Cc: michael.opdenacker@rootcommit.com
Subject: Re: [yocto] How to install a Snap package in Image #mickledore #snapd
Date: Tue, 01 Oct 2024 04:50:56 +0000 (UTC) [thread overview]
Message-ID: <7c6729c4-c102-440d-9b00-b00692a4c347@rootcommit.com> (raw)
In-Reply-To: <4AAy.1727720529418877126.OAb7@lists.yoctoproject.org>
[-- Attachment #1: Type: text/plain, Size: 1219 bytes --]
Hi David,
On 9/30/24 20:22, Spore, David wrote:
> Hello,
> I have a snap package provided by a vendor that I would like to
> include in my Debian Bookworm 12 image (built with Yocto). How do I
> create a recipe that can run Snapd to install a pre-built snap
> package? Are there any examples of how to deploy a pre-built snap
> package during the image build process? I want to avoid having to
> manually run snap on the package after the image is deployed.
> DART-MX8M-PLUS - Debian Bookworm 12.5 based on Yocto Mickledore 4.2
> with NXP BSP L6.1.36_2.1.0
For my understanding, have you tried manually first to prove that it
could work? I guess you already built snapd using meta-snapd or
meta-snappy
(https://layers.openembedded.org/layerindex/branch/master/recipes/?q=snapd)
By the way, trying to install Debian packages won't work, or at least
the installed binaries are not expected to work because they were built
against different libraries. However, this might work with a snap
container if all the library prerequisites are indeed included, in
particular the standard C library.
Cheers
Michael.
--
Michael Opdenacker
Root Commit
https://rootcommit.com
[-- Attachment #2: Type: text/html, Size: 2746 bytes --]
next prev parent reply other threads:[~2024-10-01 4:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 18:22 How to install a Snap package in Image #mickledore #snapd Spore, David
2024-10-01 4:50 ` Michael Opdenacker [this message]
2024-10-01 13:21 ` [yocto] " Spore, David
2024-10-02 13:36 ` Michael Opdenacker
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=7c6729c4-c102-440d-9b00-b00692a4c347@rootcommit.com \
--to=michael.opdenacker@rootcommit.com \
--cc=dspore@parraid.com \
--cc=yocto@lists.yoctoproject.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.