| 2022-06-04 15:17:55 |
Rudra Saraswat |
description |
It would be great if support for removal of packages was supported in chroots, like installation is supported through seeds.
This is going to prevent us from releasing Ubuntu Web 22.04's Brave edition. We want to remove the Firefox snap from it, but looks like packages can't be removed from a seed.yaml file (to replace it with the Brave snap). Are there any plans to implement option 2? (basic support for installation and removal of snap packages inside a chroot, other operations don't need to be supported for most usecases inside a chroot, like mounting and running snaps).
This doesn't only affect flavors and remixes like Ubuntu Unity, Ubuntu Web, Ubuntu Cinnamon etc, but also affects people who
1) build ISOs with tools like the Ubuntu Remix Builder (https://gitlab.com/ubuntu-unity/ubuntu-remixes) and @PJSingh5000's Cubic project for their regular setups
2) develop downstream distros which remove snap packages when building inside a chroot
3) build images for their embedded devices using their own builders (not Ubuntu's builder) which build inside a chroot
I think this issue is really important and should be re-opened. (seed.yaml is only a temporary workaround for very few usecases) |
It would be great if support for removal of packages was supported in chroots, like installation is supported through seeds.
This is going to prevent us from releasing Ubuntu Web 22.04's Brave edition. We want to remove the Firefox snap from it, but looks like packages can't be removed from a seed.yaml file (to replace it with the Brave snap).
This doesn't only affect flavors and remixes like Ubuntu Unity, Ubuntu Web, Ubuntu Cinnamon etc, but also affects people who
1) build ISOs with tools like the Ubuntu Remix Builder (https://gitlab.com/ubuntu-unity/ubuntu-remixes) and @PJSingh5000's Cubic project for their regular setups
2) develop downstream distros which remove snap packages when building inside a chroot
3) build images for their embedded devices using their own builders (not Ubuntu's builder) which build inside a chroot
I think this issue is really important and should be re-opened. (seed.yaml is only a temporary workaround for very few usecases) |
|
