Hi
I did a snap (pandoc-researchhacking) for Pandoc and need two aliases:
- pandoc-researchhacking.pandoc → pandoc
- pandoc-researchhacking.pandoc-citeproc → pandoc-citeproc
Thank you 
bump
What is the reason why you didn’t call your snap pandoc? Then you wouldn’t need an alias. In general using prefixes or suffixes is discouraged unless you actually make changes to the software itself.
The only downside of using the regular name is that the pandoc project can take over your snap if they wish so, but that shouldn’t be a problem if your goal is simply to have pandoc in the snap store.
Note: I’m a community member, don’t take this as an official response.
Thank you for the suggestion. My understanding was that I had to name it something else, but you have a good point – I can just hand over the snap if the Pandoc project is interested.
The snapcraft tool is confusing about this. I created this issue to track that: https://bugs.launchpad.net/snapcraft/+bug/1886223
If you find any documentation which states otherwise, please let me know so I can update it.
That is exactly it. That question “Would you say that MOST users will expect ‘ikbestani’ to come from you, and be the software you intend to publish there?” confused me. So I just decided it was better to have a suffix. But this was before I realized that the snap name would end up in the PATH (or whatever it does) and not the app -> name stated in the YAML file.
But https://snapcraft.io/docs/registering-your-app-name actually explains the options fairly well. Maybe not explicit enough, but there are two options: Either “name should be owned and published by members of the relevant project” or publish the snap under snapcrafters. In the second option I gees that there is a procedure for handing over the name to upstream. And the doc also states: “Do not prefix or suffix the name, for instance with your username or “-snap.”” – and that is the the compete opposite to the question in the snapcraft tool.