I understand, I was just confused as to why Ads20000 brought up contacting the developers as I am new to this and I thought that it wasn’t a big deal, that they can be contacted at any point.
1 Like
additionally I have not had coffee and i’m very confused in general, after reading a few other calls for testing I put together my post the best I could 
Ah sorry it’s my bad I guess please don’t worry about it! I didn’t realise that it will be fairly easy to transfer ownership of the Snappy Store app to the original developers later. You’re doing the right thing, try and get an initial snapcraft.yaml working and then hopefully they can integrate it into their build process later (thus making updates faster because we don’t need to do the updating ourselves).
please don’t use my calls for testing as a strong guideline of how to do them. I tend to talk a lot about a lot of random stuff, I’ve been told.
Only the steps for how to help are required. The rest is free form.
Short and to the point is a nice goal that I try to apply everyday, and fail.
Elopio, thank you for clarifying, I know as we go along it will become easier for me a bit more and I can make everything up as I go along 
Ads20000 I’m sorry for being a bit “snappy” !!
So far I have had a few tests and all good feedback. I’m looking forward to making more snaps! Thank you to the community for helping me feel so welcome!
1 Like
What isn’t working with the snap atm?
it’s so simple so not much can get wrong, eh? Also, I cheated and had elopio check it first 
1 Like
8 downloads is close enough for testing moving it over to stable now. Thank you! Let me know if there are any errors though or any ideas.
I opened an issue here: https://github.com/redacted/XKCD-password-generator/issues/66 to see if the developer would like to maintain the snap on their own. Wasn’t sure what to say or how to go about asking. Posted the link to this posting just in case they couldn’t contact me if they decide to maintain it later on.
2 Likes
Oh cool, could you write a new snapcraft.yaml which uses a released version of xkcdpass (just needs to be the same as this one, but with a different source)? Does the Python plugin allow you to point to a release .tar.gz of the app (give it a go)? You could then push that to beta (and candidate and even stable if there’s no bugs!) and have your Git source one in edge.
I think it would be a separate snapcraft.yaml but the same Snap. You would push the one pointing to the GitHub repository to the edge channel and the one pointing to a release to beta, candidate, and eventually stable.
Hello, I’m back!
snapcraft is flexible enough to let you do (almost) anything. So you could use a released tar.gz as the source without problems. However, that’s not the approach I would use.
Now that everybody seems to be happy with the quality of the snap, and @roxd explored the features available in snapcraft, I would recommend to contact upstream to see if they are interested in maintaining it. If so, after the transfer they can just hook their CI system to make continuous delivery following the instructions here: https://snapcraft.io/docs/build-snaps/ci-integration
Whenever they make a new stable release, that will get immediately to the store and can be made available to all the users in the stable channel.
If they are not interested in maintaining it, this snap repo can also be hooked to the daily cron from travis, so it’s extremely low maintenance for roxd and she can use her time in something more interesting like new snaps or other types of contributions.
I think there’s no need for a different snapcraft.yaml here. And I’d be happy to help in any of the two cases. Let me know how it goes.
pura vida
1 Like
Did I take the wrong approach here (with Corebird) then? I’m guessing I can still recommend they use build.snapcraft.io but that instead they just use the master snapcraft.yaml and wait for a new stable release before releasing a stable Snap?
There is no wrong, as I said, all these tools are made flexible to fit any preference. But in corebird, I would have just started to push to edge until a new release is tagged.
I’ve edited the description accordingly, the only issue with that approach is that there may not be a stable Snap until a new release is made, which could be a while (or it might not be)!
I’m glad that there’s a stable Snap up for xkcdpass (only just noticed), good job @roxd!
Yes this would probably be the way to go then. I’ve already opened up an “issue” in github explaining the snapcraft situation and haven’t heard back. I can do this until if/when the developer decides to take over.
thank you @elopio and @Ads20000 for the input. as my first snap, I don’t know all these small details!
OK, I’m a newbie to snaps to pardon my ignorance.
I’m writing a snap that has a database and I’m wanting to generate a random db password as part of the install process.
I was hoping to just include this snap inside my snap or make my snap dependant on it.
I tried using
after: [xkcdpass]
but snapcraft says its not in the store (ubuntu)
So what is the correct method of using this snap within my own snap?
I’m not sure after is what you want here, that may be trying to pull Debs from Ubuntu? You should be depending on other snaps by using interfaces and I’ve asked @niemeyer for a syntax example for what he said here.
From the documentation about after:
Specifies any parts that should be built before this part, which Snapcraft then stages before trying to build this part. This is useful when a part needs a library or build tool built by another part. If the part defined in after is not defined locally, the part will be searched for in the parts repository.
That means your other snap does not qualify, because 1) it’s a snap, not a part; and 2) it’s not included in the remote parts repository.
To use another snap at runtime you need to use interfaces - plugs and sockets - to link the other snap into yours when your snap gets installed.
To use a snap at build-time there has been mention of a then-undefined build-snaps stanza, which was talked about as potentially working like build-packages. I don’t know whether that was settled-upon, included in any releases, or abandoned as a silly idea, so I might be sending you on a wild goose hunt by mentioning it
1 Like