=== JoshStrobl is now known as JoshStrobl|zzz [06:18] PR snapcraft#1594 opened: code style: remove the extra quotes in the dedent example [06:58] PR snapcraft#1595 opened: tests: fix the skip of snapd integration tests in armhf [07:07] PR core#60 closed: Fix handling of secondary addresses [07:10] PR snapcraft#1596 opened: tests: move ruby demo test to snapd integration suite === JoshStrobl|zzz is now known as JoshStrobl [17:47] PR snapcraft#1594 closed: code style: remove the extra quotes in the dedent example [19:52] I'm setting up to publish a snap but need to select a "developer namespace". can anyone explain to me what this is? [19:52] I can, apparently, only set it once and I don't want to get it wrong [19:54] the docs state: "This namespace will represent you as a publisher in the Snap Store and you won’t be able to change it afterwards" [19:54] represent me? how? [19:54] I have an account name. so can I have my account name the same as the namespace? [20:25] ekkis, yes [20:25] ekkis, your namespace will show up in `snap list` as the publisher of the snap [20:27] ekkis: right [20:27] ekkis: so essentially this is your publisher nickname [20:27] ekkis: if you say "my namespace is ekkis" [20:27] oh... I see. it's because my "account" doesn't have an account name, like in most other systems [20:27] ekkis: then if someone "snap install thatfancyapp" [20:27] ekkis: then they will get it from "ekkis" [20:27] ekkis: I agree the word namespace is not clear here [20:28] so they don't have to run `snap install ekkis/thatfancyapp`? [20:31] ekkis: that's right [20:31] ekkis: users install snaps [20:31] ekkis: snaps have names [20:31] ekkis: and users search by name, not by developer IDs or similar things [20:31] thanks mate [20:31] my pleasure :) [20:31] kyrofa is the time off getting too boring? :-P [20:31] I'm building my first [20:32] sergiusens, haha, no, I just tend to idle here even when I'm not working and noticed a question :) [20:32] nothing like the feeling of building one's first snap :) [20:33] I can specify the `source` field as a url to a tarball. can I also point it to a github repo? [20:33] ekkis: snaps give developers the power to publish to users [20:33] ekkis: yes [20:33] do I use the .git url? [20:33] ekkis: there are lots of possible schemes, sergiusens and kyrofa can tell you all about that [20:34] for example, for Einsteinium (which I'm trying to package), the Clone or Download button indicates: https://github.com/emc2foundation/einsteinium.git [20:34] can I use this url? [20:34] ekkis, indeed you can [20:34] zyga-solus does content interface work with classic snaps? [20:35] kyrofa++ [20:39] suppose that my project has a bunch of dependencies. the build doc indicates I should install them using apt-get. how do I express these in the `parts:` section? [20:39] I presume these parts are snaps? [20:39] so I have to find the equivalent snaps? or? [20:40] which also begs the question, do I have to declare all the building tools? [20:40] most of the dependencies are developer-level [20:42] in other words there are dependence packages that don't need to be included in the snap [20:44] ekkis, there are three keywords that will be of interest: build-packages, stage-packages, and build-snaps [20:44] oh... let me read up on those then [20:44] build-packages are debs that are installed on the host (builder). Build tools might fit into this section [20:44] stage-packages are debs that are fetched from the archive and unpacked into the snap [20:45] build-snaps are snaps that are installed on the host (e.g. perhaps your build tools are snapped) [20:45] it's not part of the `parts` section I see [20:46] ekkis, I'm not sure which docs you're reading [20:46] Link? [20:46] I see in the different part of the docs it talks about these 3 keywords [20:47] so for example, the command `sudo apt-get install build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils` in the instructions requires I have all those tools for building [20:47] that means I have to find snaps of them correct? [20:47] ekkis, no, those would be build-packages [20:48] so do I just declare `build-packages: build-essential libtool autotools-dev automake pkg-config libssl-dev libevent-dev bsdmainutils` ? [20:49] Something like that. It needs to be a YAML list, but you have the right idea [20:49] ah. ok [20:49] and Snapcraft knows to do an apt-get for each [20:49] and if snap is running on Fedora it will do a `yum install`? (or whatever it is now) [20:50] ekkis, not yet, support for other distros in snapcraft is coming [20:51] ah, but at least theoreticallly [20:51] at present I'm only concerned with Ubuntu [20:51] I used to package stuff in RPM form for Redhat and later Fedora [20:51] so having a cross-distro packager is great! [20:55] ekkis, note that, while Snapcraft currently only runs on Ubuntu, the snaps it produces should run everywhere [20:58] oh. anywhere so long as `snap` is available on the platform [21:01] ekkis, you got it [21:01] ekkis, fedora has snapd, for example [21:04] ekkis support for rpm distros is coming through dnf support, you can probably get more detailed information from Son_Goku on that aspect [21:05] * Son_Goku waves [21:06] kyrofa since you are here, mind quickly glancing at snapcraft#1597 ? [21:06] PR snapcraft#1597: pluginhandler: warn about migrated system libraries [21:08] ekkis: if you want to build RPM-based snaps, you can do it by hand right now [21:08] though it's a pain to do [21:08] kyrofa and kalikiana have been helping me with getting different aspects of Snapcraft running on Fedora [21:08] PR snapcraft#1597 opened: pluginhandler: warn about migrated system libraries [21:14] Son_Goku: I may want to. I'm building my first snap so I'll stick to the Ubuntu variant but I may come back to you [21:14] Son_Goku: I was a redhat/fedora guy for a decade years ago [21:17] the main problem is describing the security stuff [21:17] otherwise, it's really easy [21:23] * Son_Goku grumbles [21:24] crap Wi-Fi sucks [21:24] does it matter what I call parts? I think I only have one part so I could just call it `main`? [21:27] kyrofa: "A set of Ubuntu packages to be downloaded and unpacked to join the part before it’s built" -- what does "join" mean? [21:30] guys, I've looked through the docs but it's not at all clear to me where I actually run the commands to build my app [21:31] I need to run autogen, configure, make and make install [21:32] oh.... I can use `plugin: autotools` [21:32] PR snapcraft#1574 closed: Add Dotnet plugin and a sample snap for integration test [21:32] so I just need to figure out how to configure the plugin [21:43] ekkis: part names don't matter [21:43] ok, cool [21:43] ekkis: snapcraft has nice built in help I think [21:43] including help for particular plugins [21:44] # snapcraft --help autotools? [21:44] snapcraft help autotools [21:44] not quite I think, try snapcraft help and look from there [21:44] I think snapcraft help plugins or something like that talks about it but I don't remember [21:45] thank you sergiusens [21:46] the help is for commands to snapcraft [21:47] but I'm looking at the web for help. the docs are not very clear [21:49] ekkis https://docs.snapcraft.io/build-snaps/your-first-snap [21:50] yes, I'm reading through that doc [21:51] my network is wonky, so I cannot verify what I am sending over your way ekkis but this might be useful https://tutorials.ubuntu.com/tutorial/create-your-first-snap [23:58] Hello === buzz_ is now known as Guest93864 [23:59] Hello [23:59] Anyone hoe [23:59] Anyone home