I’d like to request 3 automatic aliases for the ldc2 snap package, corresponding to the 3 extra commands exposed by the snap: ldmd2, ldc-profdata and ldc-prune-cache.
Requested here in accordance with guidance given in:
In line with points raised here:
the ldc2 snap is the official snap package of the LDC compiler; the compiler project is hosted at https://github.com/ldc-developers/ldc while the snap package is hosted at https://github.com/ldc-developers/ldc2.snap. See also discussion on the snapcraft mailing list and LDC forums around the time the package was set up: https://lists.ubuntu.com/archives/snapcraft/2017-January/002736.html and https://email@example.com
the 3 aliases requested are for apps that come as standard as part of the LDC compiler package (for example, the deb package in regular Ubuntu repositories includes ldmd2)
many tools in the D world will assume that the commands have these names (particularly the ldmd2 command, which provides an alternative CLI for the compiler), so it’s inconvenient to force users to use ldc2.ldmd2.
Let me know if any more info is required/would be useful.
Based on https://github.com/ldc-developers/ldc2.snap/blob/1.2/snap/snapcraft.yaml, the three aliases are for:
All of these commands seem reasonable for the ldc2 snap. Note, they exist as commands in the ‘ldc’ deb in the Ubuntu archive. Considering the described workflow for D tooling, granting the alias seems very sensible. Furthermore, the ldc2 snap is an officially maintained snap from ldc upstream.
@joseph.wakeling - can you give either give the store URL for the snap or give the name and publisher of the snap?
Not sure what you mean by the store URL, but the snap name is ldc2 and the publisher is ldc.
Thanks very much for the approval!
Note, I expect this to be approved, but I’m following (the as of now not approved) voting procedures in Process for reviewing aliases, auto-connections and track requests and as such, I only voted to approve. Pedantic, I know, but I just want to make sure your expectations align with what’s happening in our process atm.
All good. I appreciate both the process and the clarity!
+1 as well, both on the process and on the requested aliases.
FYI, the procedures are finalized in Process for reviewing aliases, auto-connections and track requests. Once a week has passed (in this case on Monday), we’ll tally the votes and perform any actions for this request.
The voting period has expired. Performing the tally:
2 votes for
0 votes against
0 votes abstained
Granted use of the aliases to https://dashboard.snapcraft.io/dev/snaps/6805/ (ldc2 snap from ldc publisher). This is now live in the store.
Thanks everyone – the support is really appreciated!
FYI, I’ve been invited to write an entry for the official blog of the D programming language about this and the other D-related snaps published recently.
One question: is it planned to have official aliases listed in the snap dashboard? I don’t see any details of them there.
Maybe, but doesn’t feel so important to be honest. Having great access to which snaps are available seems like a priority.