I have successfully created a snap for gitoxide which also includes a second binary called ein
.
apps:
gitoxide:
command: bin/gix
environment:
PATH: $SNAP/bin/:$PATH
plugs:
- network
- home
ein:
command: bin/ein
environment:
PATH: $SNAP/bin/:$PATH
plugs:
- network
- home
I’ve included the binary in the list of apps
, but it won’t run. I am wondering if this would require special permissions from the review team?
Here are the two commands I’m requesting be aliased:
gitoxide --> gix
gitoxide.ein --> ein
The binaries runs this way…
snap run <snap_name>.gitoxide
and snap run <snap_name>.ein
This is not needed when both snap_name and app name is same
The snap name and the app name are not the same. The suite is called gitoxide, and the two commands that are to be run are gix
and ein
.
@advocacy, would I be able to request an official alias for each of those commands?
gix
and gitoxide.ein
so that users wouldn’t have to add them, or run them in this “clunkly” sort of way?
Yes you’d be able to request an alias for both, it’s not advocacy you need though, alias’s are just a standard review (i.e not super-privileged).
You’ve not made it 100% explicit what you’re asking for aliasing but I’m assuming it’s
gitoxide.gix--> gix
gitoxide.ein --> ein
(I ain’t a reviewer, but they should pick up on this soon)
2 Likes
+1 from me for the requested gix
and ein
auto-aliases since I don’t see any major conflict with other apps. Can other @reviewers please vote?
1 Like
Thanks @emitorino - I know there was some back and forth, and I’ve edited my OP to provide the aliases I should’ve asked for in the first place.
Just for clarification, I’m asking for the following:
gitoxide --> gix
gitoxide.ein --> ein
cav
8
+1 from for granting the gix
and ein
aliases. I don’t see any conflict with an existing application and it makes sense for the application.
cav
9
+2 votes for, 0 against. Granted aliases gix
for gitoxide
and ein
for gitoxide.ein
. This is now live.
1 Like