Alias requests for chocolate-doom-jdstrand


#1

I request the following aliases for https://snapcraft.io/chocolate-doom-jdstrand:

  • chocolate-doom
  • chocolate-doom-setup
  • chocolate-heretic
  • chocolate-heretic-setup
  • chocolate-server
  • chocolate-strife
  • chocolate-strife-setup

These are the common executable names known to chocolate-doom users.


#2

why the -jdstrand suffix?


#3

IIRC (quite some time ago) someone said they were working on a snap for chocolate-doom. I didn’t see the snap in the store and just did the snap for myself as a fun side project and thought others would enjoy. I’m not upstream and I have no affiliation with upstream and suspect I may eventually have functionality that diverges from pure upstream (but not for the commands I requested aliases for).


#4

@reviewers - can two or more of you vote on this request?


#5

If / when upstream creates the “official” chocolate-doom snap and they want the same aliases will this be a problem? Would the two conflict if they are both installed and both have the same aliases?


#6

I am :+1: on the aliases.

We don’t advocate for the use of -myname suffixes these days since it is easier to hand over a snap to upstream and not impact existing users of the snap.


#7

Sure. My point is perhaps I don’t want to hand it over :wink:


#8

snapd knows how to handle snaps that declare the same interfaces. I don’t recall the specific details but believe that both are installable and the the first installed gets the alias.


#9

(assuming you meant “the same aliases” there)
indeed, that’s what snap install --unaliased and snap prefer help with.


#10

I of course meant “the same aliases”.


#11

FWIW one thing with aliases is that you can’t have an alias that is the name of a snap


#12

@jdstrand, I’ve updated the snap declaration to include these aliases.