Yocto Project Discussions
 help / color / mirror / Atom feed
From: Michael Opdenacker <michael.opdenacker@rootcommit.com>
To: dspore@parraid.com
Cc: michael.opdenacker@rootcommit.com, yocto@lists.yoctoproject.org
Subject: Re: [yocto] How to install a Snap package in Image #mickledore #snapd
Date: Wed, 02 Oct 2024 13:36:11 +0000 (UTC)	[thread overview]
Message-ID: <e4142246-cf86-4dd4-884d-ef8d7561744b@rootcommit.com> (raw)
In-Reply-To: <7587.1727788883607607228@lists.yoctoproject.org>

Hi David

On 10/1/24 15:21, Spore, David wrote:
> Michael,
> Thanks for your reply!  Yes, I have deployed the snap on my target 
> machine manually after having installed snapd.


But did you check that the snap worked as expected?

> Now I am looking for a way to run snap packages during the image 
> build, as well as deploy rpm and/or deb packages.


Do you mean deploying rpm and deb packages from other distros like 
Fedora and Debian? Those are extremely likely to break, as the binaries 
were built against different C libraries. RPM and DEB are package 
formats, they don't provide binary compatibility.

>   I've deployed these packages manually on the target machine.  My 
> problem is that I don't know how to write recipes for automating these 
> tasks at build time.

I guess you should write a class which the recipes would inherit. You 
may ask the meta-snapd or meta-snappy people for advice.
Cheers
Michael.

-- 
Michael Opdenacker
Root Commit
https://rootcommit.com



      reply	other threads:[~2024-10-02 13:36 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 ` [yocto] " Michael Opdenacker
2024-10-01 13:21   ` Spore, David
2024-10-02 13:36     ` Michael Opdenacker [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=e4142246-cf86-4dd4-884d-ef8d7561744b@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox