When a providing snap is installed, snapd will 
generate security policy that will allow it to 
listen on the well-known DBus name on the specified 
bus. If the system bus is specified, snapd will also 
generate DBus bus policy that allows ‘root’ to own 
the name and any user to communicate with the 
service. Non-snap processes are allowed to 
communicate with the providing snap following 
traditional permissions checks. Other (consuming) 
snaps may only communicate with the providing 
snap by connecting the snaps’ interface.

Parts

This section defines the sources required to
assemble the snap.

Parts can be downloaded and built automatically using plugins.
Similar to extensions, snapcraft can use various plugins
(like Python, C, Java, Ruby, etc) to assist in the
building process. Snapcraft also has some special plugins.

Performs no action and the actual build process is
handled using a manual override.