mackup is some sort of backup application.
It creates symlinks for every application supported (mainly with dotfiles) to a single directory.
This directory can be a dropbox, git, etc.
mackup need classic confinement because mackup need to access its own .mackup.cfg file but also any other dotfile in home user dir.
The snap has already been pushed to snapcraft and is under manual review pending status
I’m going to +1 this request as it needs access beyond any of our interfaces will allow. Specifically access to numerous dotfiles in the home directory, and other arbitrary locations for backing up those dotfiles. Without classic, this snap effectively won’t work.
Ideally though, this would be better pushed upstream. Have you spoken to the upstream developers about landing the yaml there, and having them push to the store?
I’m familiar with the Mackup and used it for years so understand the request for classic. Upstream have been receptive to Linux related pull requests I’ve filed in the past so I’m sure @guilhem will have good success landing this
Good to know, I also have a patch to submit to improve bootstrapping.
git clone http://... dirsnap install mackup --classicmackup restore -f for/mackup.cfg
It seems like classic granting has been lost for Mackup, I can’t publish a new version of it:
(NEEDS REVIEW) confinement ‘classic’ not allowed. If your snap needs classic confinement to function, please make a request for this snap to use classic by creating a new topic in the forum using the ‘store-requests’ category and detail the technical reasons why classic is required. lint-snap-v2_confinement_classic What does this mean?
Sorry apparently this fell through the cracks - this is after the snap was transferred, and the thinking at the time was that the use of classic would need re-vetting under the new publisher - vetting that was apparently never done.
@Wimpress@Popey@Igor or anyone from @advocacy, could you please perhaps check that thread I linked to, and see if it’s reasonable to reinstate use of classic for mackup? either myself or @jdstrand can then action this.