Alias request for age

store-requests aliases
1
  • name: age-encryption
  • description: age (file encryption tool)
  • snapcraft: age-snap/snap/snapcraft.yaml at main · nooreldeensalah/age-snap · GitHub
  • aliases:
    • alias1: age-encryption.age → age
    • alias2: age-encryption.age-keygen → age-keygen
    • alias3: age-encryption.age-inspect → age-inspect
    • reasoning: Non-snap installations has these these commands age, age-keygen, and age-inspect, currently, they have to be prefixed with age-encryption. So it would be a better UX to match the aliases/commands from a non-snap installation

To the best of my knowledge, there is no existing snap alias already granted or a well-known Linux application conflicting with the aliases requested here.

2

This request has been added to the queue for review by the @reviewers team.

3

Hi @nooreldeensalah!

If I am not mistaken giving snaps the same aliases with non-snap installations may result in conflicts. What do other @reviewers think?

4

Hi @yomonokio!

My intent is making this snap provide the same UX as a non-snap installation. For example, installing the Flutter SDK snap lets users invoke flutter exactly as documented for manual installs.

In this case, the age snap name was unavailable, so I chose age-encryption. The goal of the requested aliases is simply to expose the upstream commands (age, age-keygen, age-inspect) and match the experience of the listed non-snap installation methods.

5

I think it is fine for the snap to conflict with other non-snap installations - given these are the same underlying applications then that should be expected IMO that if a user installs both that they would get a conflict.

As such, +1 from me (#voteFor) for these aliases for age-encryption.

6

Hello! This is a +1(#voteFor) from me as well for granting the three requested aliases for the age-encryption snap. My quick research supports that the specified upstream would be the expected and most popular provider of the age command.