Repository files navigation

This is the unofficial snap packaging forMari0: Community Edition,Snaps are universal Linux packages.

Refersnap/README.md for user-oriented information.

Snapcrafters (join us) are working to land snap install documentation and thesnapcraft.yaml upstream so Mari0: Community Edition can authoritatively publish future releases.

• Import theSnapcrafters Template Plus repository to your own GitHub account and name it assnap_name-snap (or any valid name you prefer) using GitHub'sImport repository feature
  • It is recommended toavoid forking the template repository unless you're working on the template itself because you can only fork a repository once
• Update the description of the repository
• Update logos and references toMari0: Community Edition,mari0-ce and other placeholder names inREADME.md,snap/README.md, andsnap/snapcraft.yaml
• Add upstream contact information to thisREADME.md
• Create a snap that runs indevmode,or inclassic confinement if that's not possible
  • If the snap must be packaged underclassic confinement, file aclassic confinement request topic in the Snapcraft Forum, under thestore topic category -template -link
• Add a screenshot tosnap/README.md
• Register the snap in the Snap Store,using the preferred upstream name(i.e. without custom postfix). If the preferred upstream name is not available or reserved,file a request to take over the preferred upstream name and temporary use a name with personal postfix instead.
• Setupbuild.snapcraft.io and publish thedevmode snap in the Snap Store edge channel
• Add the provided Snapcraft build badge tosnap/README.md
• Update snap's metadata, icons and screenshots on thedashboard
• Add install instructions tosnap/README.md
• File an Intent-To-Package issue/bug to the upstream's contact or issue/bug tracker to consolidate and let the upstream acknowledge the effort -template -link
• Convert the snap tostrict confinement, orclassic confinement if it qualifies
• Publish the confined snap in the Snap Store beta channel
• Update the install instructions insnap/README.md
• Post a call for testing on theSnapcraft Forum -template -link
• Publish the snap in the Snap Store stable channel
• Update the install instructions insnap/README.md
• Post an announcement in theSnapcraft Forum -template -link
• Submit a pull request or patch upstream that adds thesnapcraft.yaml and any required assets/launchers -example -link
• Submit a pull request or patch upstream that adds snap install documentation -example -link

If the upstream accepts the PRsAND willing to maintain the package on the Snap Store:

• Request upstream create a Snap Store developer account
• Create a topicunder thestore category in the Snapcrafters Forum to request the snap be transferred to upstream -template -link

If the upstream rejects the offer:

• Ask aSnapcrafters admin to fork your/upstream's repo into github.com/snapcrafters, transfer the snap name from you to snapcrafters, and configure the repo for automatic publishing into edge on commit -template -link

Finally:

• Ask the Snap Advocacy team to celebrate the snap -explanation -link

If you have any questions,post in the Snapcraft forum.

Packager	Upstream
林博仁 Buo-ren, Lin	Issues · Mari0-CE/Mari0-Community-Edition