the included snapcraft.yaml means i need to have the whole tree locally
on disk, as someone who maintains a ton of community images for
UbuntuCore i prefer to just have the snapcraft.yaml locally so the disk
is only cluttered during build. along with that i am trying to build the
eoan tree for the core18 Pi4 image i provide, the wlan firmware is not
in the linux-firmware package in bionic, so i need overrides ... beyond
this, a lot of config options that i require to be builtin are modules
and the initramfs handling in snapcraft is still a mess, so i prefer to
build in MMC support and USB disk support... along with this we have a
good bunch of customers building custom kernels with out-of-tree
snapcraft file and brand stores so it helps to know what they
experience.
:)
note that once we have an official core image for the Pi4 i'll drop this
work anyway ...
closing the bug as invalid ...
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851233
Title:
building a snap from the eoan tree using the raspi2 defconfig results
in gigantic snap package
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1851233/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
