huh, that should not happen. I’ll see if I can reproduce it in debian 9.7 in a vm here. 2.39.3 should absolutely be able to deal with this.
What might have happened is that you started with an older snapd, I see that stretch has 2.21, which is rather ancient and almost certainly doesn’t know about bases (I’d have to look it up to be sure). However at some point you’ve obviously downloaded the
core snap, so now you’re running 2.39: you should be able to install
snap-store without issue now. Can you try again?
I’m sorry it’s not comprehensible to you, let’s see if we can fix that. It is automatically generated from the snap tool itself, so that it’s always up to date, but it’s not meant as an introduction to all the concepts — but we’ve been wanting to add support for this kind of thing so let’s see what is needed; there’s probably something we can do (we’ve talked about adding
snap help <thing> where
<thing> are the help categories in the current output of
snap help, but I can totally see more
<thing>s we could use it for). @degville might also have input on this.
I don’t know what you mean by ‘proprietary language’, could you explain?
I don’t see the issue of the two copies of all the text, but that might be because debian insists on building things with different library versions and we’ve done quite a bit of work on upstream go-flags to get it to work nicely for our use case. I’m not sure what else we can do for that. As you now are running 2.39 from
core itself, you could do
snap help --man | man -l -, which is not pretty but should get you a better manpage.