snapcraft does not handle framework-policy

Bug #1501037 reported by Jamie Strandboge
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fix Released
Sergio Schvezov
Fix Committed
Sergio Schvezov

Bug Description

Framework snaps that use snapcraft have no way to copy framework-policy in place. framework-policy is not expressed in the yaml and is instead a directory under meta/ that contains various framework policy.

What would work well is if the toplevel dir for framework-policy could be expressed in the snapcraft.yaml so that it could be copied into snap/meta/framework-policy. Other options resulting in snap/meta/framework-policy existing are of course fine.

Related branches

Changed in snapcraft:
assignee: nobody → Sergio Schvezov (sergiusens)
Changed in snapcraft:
milestone: none → 0.3
importance: Undecided → Critical
Changed in snapcraft:
status: New → Fix Committed
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

I tested tools-proposed and this seems to work well:

1. put framework-policy directory and files in ./security

2. adjust snapcraft.yaml to have:
name: wget
version: 0.1
framework-policy: security/framework-policy

3. run snapcraft

Now, snap/meta/framework-policy has everything that is in ./security/framework-policy


Changed in snapcraft:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.