If I pull this in, that's it? Running that command will always clone the current master from github and compile it? Or would I need to register hightail on snap's website (whatever that is)?

Currently I've registered hightail on the snap store, but it's bound to my account, not sure if that's a problem.

As you can see here, snapcraft can build the project every time an update is made, and release it to the snap store. (I think it should be automatic)

However I think since updates are all made to the main repository (which is this one), you'll have to register an account and add your repo for it to work. Or alternatively I'll pull the updates from your repo, and it should work fine.

Problem is although this is somewhat slightly better for deployment, I believe downloading the file straight from the releases page would be faster because snap may add some metadata (i'm not too sure about that).

tldr: if you are lazy, probably just ignore this pull request

Hmm. So I am indeed too lazy if I would have to do something every time master gets an update. On the other hand, if it's about doing some stuff now and being able to forget about it, then I'm up for it :)

And also, it is master, right? Or only the GitHub releases? And the version string should not be v0.9.6, I think - right now that's the latest release, but master is ahead of that, and also we're not going to update this string every time something changes. Maybe we can leave the version empty...

So what do I do?

Yeah it's a one-time setup. You just need to merge my pull request as I've got every thing setup properly in there already. Then, register an account at build.snapcraft.io/.

However one problem is I've registered the name hightail so you may have problems registering that name with your account. I'll try to get that name unregistered at the meantime.

Hey @dj3500, once you fill the registration form in https://dashboard.snapcraft.io you can add a comment to request the transfer of the name from @daniellim2000. Give it a try, the snap will be built and released automatically from https://build.snapcraft.io every time you change master. The snap will land in the edge channel, where your community and the community of ubuntu testers can give it a try and provide quick feedback. And once you are confident with a version and move it to the stable channel, it will be exposed to millions of users from the store, who can install it with one click/command, and get automatic updates.

About the version string, you can use version: git, and when you add an annotated tag to the repo to make a release, the version of the snap will take the value of the tag. But you can worry about the details later as you go, the edge channel is for experimentation. If you and your users like it, you can then maintain the stable release.

Thanks @daniellim2000 !

Thanks for the help @ElOpio .

Ok, I made a petition and merged this in. Also pushed a commit to change the version string to git.

Please let me know when it works - I don't have a Linux machine to test this on. Also, I think we can put it on the stable channel from the get go...

Alright great.

Should I also add the repo (the bit that does OAuth from GitHub etc.)? Right now I just made an account and requested rights to the hightail snap...

Alright, I added, it got released. Could one of you guys test: sudo snap install --edge hightail?
In particular, it would be good to see if hightail.config survives between sessions (i.e., whether hightail has write access to that).

And another question to the snap afficionados. If I release this version (1) as stable, that doesn't imply that any future (automatic) releases to edge will be in stable, right? Is there a way to make all new commits to master here create a new stable release? If not, I suppose I will just stay on edge forever. (But are there automatic updates then? If someone installed via install --edge, do they get the edge updates forever?)

@dj3500
Ok, I'll test it out in the next few codeforces rounds.

@dj3500 Hey I just checked. Settings is preserved.

I've been getting the following emails:

====================
A scan of this snap shows that it was built with packages from the Ubuntu
archive that have since received security updates. The following lists new USNs
for affected binary packages in each snap revision:

Revision r19 (i386; channels: edge)

• libcups2: 3713-1
• libpng12-0: 3712-1

Revision r20 (amd64; channels: edge)

• libcups2: 3713-1
• libpng12-0: 3712-1

Revision r21 (armhf; channels: edge)

• libcups2: 3713-1
• libpng12-0: 3712-1

Simply rebuilding the snap will pull in the new security updates and resolve
this. If your snap also contains vendored code, now might be a good time to
review it for any needed updates.

Thank you for your snap and for attending to this matter.

References:

• https://usn.ubuntu.com/3712-1/
• https://usn.ubuntu.com/3713-1/
  ====================

When I received this about the previously latest commit, I made a trivial commit to the repo to make the snap rebuild, but now I got this again. How to fix this?

Hey there, the emails you received may have been referring to different packages, so there were a few. But you should only get one email per security update.

So you should just trigger a rebuild again and it should be fine.

Hi Daniel, could you please take a look at issue #110 and check whether it's buggy now, or advise the person somehow?

Hi, I'm busy until the end of the month. Would it be fine if I look into this after that?

Sure.

Ping, then ;)

Not sure what updates there were for snapcraft that caused the original snapcraft.yaml to not work. I'm working on it but have yet to succeed.

Ping again?

Let me ping this :)

Hi sorry actually I've not done any snap related stuff for over a year. The last time I tried it seems like things have changed that I'm unsure of. I think it's better to ask in the snapcraft forums to check with the snapcraft developers. I can do that if you want.

Hmm, would be nice if you could. I think currently it still doesn't work (i.e. didn't fix itself :) ).