Classic confinement and core_dynamic_linker

Hello all, Hearing about classic confinement was rather exciting given that it seems tailor-made for the use-cases of my current WiP snaps for the ldc2 D compiler and the dub D build system: https://github.com/WebDrake/ldc2.snap/pull/1 https://github.com/WebDrake/dub.snap/pull/1 However, I'm

Re: Classic confinement and core_dynamic_linker

On 13/01/17 23:18, Kyle Fazzari wrote: Since you're using cleanbuild, you would actually need the core snap installed in the lxc container being used, which I don't think is currently possible in lxc (though maybe it is nowadays, I know work was being done in that area). Have you tried _not_ doi

Re: Classic confinement and core_dynamic_linker

On 14/01/17 03:26, Sergio Schvezov wrote: A generic solution for build systems and CI is being worked on. Thanks for taking notice. Ah, OK, thanks. Please do ping me if there is work-in-progress I can help to test. I'd be happy to help out if I can. Can you shed light on the reason for th

Re: Classic confinement and core_dynamic_linker

On 17/01/17 22:22, Sergio Schvezov wrote: For classic confined snaps to link, they either need to be part of core or staged into your snap. On system libraries are ignored completely to ensure you have a working snap in the end. Is that a work in progress constraint, or is it the intended lon

Re: Classic confinement and core_dynamic_linker

On 18/01/17 02:21, Sergio Schvezov wrote: The logic is still run, but the resulting binary in classic uses rpath and no dynamic loading so there is no resolution to a on-system library we can pick up. I guess we can do some magic, but it feels it might be either fragile or make the build proce

Re: Classic confinement and core_dynamic_linker

On 18/01/17 13:12, Sergio Schvezov wrote: After a quick but thorough conversation with Gustavo we agreed that this is the wrong path to take as it might not be deterministic or people might get surprised about things included that shouldn't have been. There needs to be a clear line between `bu

Re: Classic confinement and core_dynamic_linker

On 19/01/17 16:56, Joe Talbott wrote: 'snapcraft build' only builds the part. You'd need to run 'snapcraft stage' to get files into the stage directory and 'snapcraft prime' to get files into the prime directory. 'snapcraft prime' will do a 'snapcraft stage' as part of its lifecycle. :-\ I'

Classic confinement success for LDC D compiler

On 13/01/17 21:46, Joseph Rushton Wakeling wrote: Hearing about classic confinement was rather exciting given that it seems tailor-made for the use-cases of my current WiP snaps for the ldc2 D compiler and the dub D build system: https://github.com/WebDrake/ldc2.snap/pull/1 https://github.com

Re: Classic confinement success for LDC D compiler

On 20/01/17 13:58, Mark Shuttleworth wrote: Congrats! What's the best way to get the D community aware of this? Sounds like it would be a nice way for them to keep up to date. Thanks Mark :-) I'm going to be in touch with the LDC devs directly in the next days (they know me, and they have kno

Snap install apparmor error: 'profile has merged rule with conflicting x modifiers'

Hello folks, With my LDC snap seemingly sorted, I'm now turning attention to my snap for the DUB build system: https://github.com/WebDrake/dub.snap/pull/1/files I've been able to get this to build as a classic snap with minimal tweaks (just switching `strict` => `classic` confinement and addi

Re: Snap install apparmor error: 'profile has merged rule with conflicting x modifiers'

On 21/01/17 00:14, Joseph Rushton Wakeling wrote: All builds fine, but when I try to install with sudo snap install --classic --dangerous dub_1.1.1_amd64.snap I get an error message: Hmm, I should have dug a bit deeper before writing. Turns out if I remove `network` from the list of

Version numbers for snap packages

Hello all, Quick question about version numbering (as in, the `version:` field of `snapcraft.yaml`). The logical choice here is to use the version of the app being packaged, but what's the recommended way to handle changes to the snap package alone that don't change the version of the underly

Re: Classic confinement success for LDC D compiler

On 20/01/17 13:58, Mark Shuttleworth wrote: Congrats! What's the best way to get the D community aware of this? Sounds like it would be a nice way for them to keep up to date. Just to follow up on this: the LDC devs have agreed to allow me to move forward with this in the name of the project.

Re: Classic confinement success for LDC D compiler

On 26/01/17 22:36, Mark Shuttleworth wrote: The plan is that there will be a mechanism for the publisher to list accounts that can push and release revisions. For now I would suggest you use your own account until we have that, then we can move to something more representative. Ack, I already

Snap package licenses

Hello all, I'm just about to upload the ldc2 snap, but have one last question first. LDC itself is released under the terms of the BSD license, but some components it links to are released under other licenses (Boost, Artistic License and LGPL). All of this is covered under the setup/license.

Re: Classic confinement success for LDC D compiler

On 26/01/17 23:04, Joseph Rushton Wakeling wrote: The `ldc2` name is apparently reserved (I requested it); if I temporarily choose a different name, will I wind up with the issue of all my programs being called something like my-temporary-snap-name.ldc2 etc.? ... no need: permission was

Re: Classic confinement success for LDC D compiler

On 26/01/17 23:31, Bret A. Barker wrote: We just added a feature to notify us on new name requests and it caught me before EOD. Well, thank you VERY much. Your advice and support has been great. You should be good to go now, but please reach out here or in the #snapcraft channel if you nee

Classic snap for D reference compiler DMD

Hello all, Following successes snapping LDC (the LLVM-based D compiler) and DUB (a build and package manager for D projects), I decided to turn my attention to the D programming language's reference compiler, DMD. This is in principle a rather trickier project: while LDC uses a very nice and

Re: Classic snap for D reference compiler DMD

On 29/01/17 21:37, Michael Hudson-Doyle wrote: You can do this just using yaml features: Great, thanks! Exactly what I was looking for. :-) -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft

LDC snap published in edge channel

On 26/01/17 22:04, Joseph Rushton Wakeling wrote: Just to follow up on this: the LDC devs have agreed to allow me to move forward with this in the name of the project. The new git repo is available at: https://github.com/ldc-developers/ldc2.snap The snap packaged passed manual review today

Using docker for clean builds of classic snaps

Hello all, Curious question. Since snapcraft cleanbuild support is still a work-in-progress for classic snaps, has anyone tried using Docker to provide a clean build environment for them? If so -- can you advise on what you did? I'm not super Docker-experienced, so while I imagine setting u

Re: snapd available in Trusty Tahr

On 31/01/17 14:01, Jamie Bennett wrote: Hi, The team are pleased to announce that, after extensive testing in proposed, snapd is officially available in the Trusty Tahr updates archive [1]. If you are running a 14.04 system we encourage you to give it a try and report any issues [2]. Thanks t

Re: Using docker for clean builds of classic snaps

On 02/02/17 14:40, Jamie Bennett wrote: We have this page that explains how to build using Docker containers (the url name is wrong but the contents are right). * https://snapcraft.io/docs/build-snaps/trusty Hi Jamie -- thanks for the pointer. Unfortunately it doesn't work with classic sn

Re: snapcraft 2.26 has been released

On 03/02/17 12:57, Sergio Schvezov wrote: Hello snapcrafters! We are pleased to announce the release of version `2.26` of snapcraft has been released: https://launchpad.net/snapcraft/+milestone/2.26 Congratulations! :-) All the snapcraft specific asset handling has been moved to the `snap` d

Re: Using docker for clean builds of classic snaps

On 02/02/17 22:35, Loïc Minier wrote: There are a bunch of Docker images providing snapcraft , unfortunately they are all behind. These should be autobuilt instead of manually updated, in the mea

Re: Using docker for clean builds of classic snaps

On 05/02/17 19:33, Loïc Minier wrote: I dont think "snapd" is in the "ubuntu" Docker image which is trimmed down a bit Yes, I gathered that much, which is why my own Dockerfile attempt ensured that snapd would be installed with this line: RUN apt-get --assume-yes install snapd snapcraft

Re: snapcraft 2.26 has been released

On 06/02/17 00:00, Sergio Schvezov wrote: Where did you see this documented? We removed all traces of license.txt from our documentation months ago as snapd made no use of it. That said you are free to drop license file inside the snap wherever you want. I didn't see it documented anywhere -- I

Re: snapcraft 2.26 has been released

On 06/02/17 00:04, Joseph Rushton Wakeling wrote: On 06/02/17 00:00, Sergio Schvezov wrote: Where did you see this documented? We removed all traces of license.txt from our documentation months ago as snapd made no use of it. That said you are free to drop license file inside the snap wherever

license.txt and snap/ directory

On 06/02/17 00:00, Sergio Schvezov wrote: We removed all traces of license.txt from our documentation months ago as snapd made no use of it. That said you are free to drop license file inside the snap wherever you want. Just to follow up a little here: I'm honestly not sure I like this change.

Re: license.txt and snap/ directory

On 06/02/17 23:40, Sergio Schvezov wrote: If it is not defined anywhere though, this is just a de-facto standard as it really is upto each person creating there snap about where to put it. Well, that's what I'm saying -- IMO it should be defined (as I believe it used to be). Files owned by

Re: license.txt and snap/ directory

On 07/02/17 00:24, Kyle Fazzari wrote: The fact that an empty directory is created here is a bug[1]. It should only create that directory if there's something to put in there. What Sergio is saying is this: Snapcraft-specific things, like hooks from snapcraft parts, command wrappers (eventually,

Re: license.txt and snap/ directory

On 07/02/17 00:24, Kyle Fazzari wrote: The fact that an empty directory is created here is a bug[1]. [1]: https://bugs.launchpad.net/snapcraft/+bug/1660890 BTW, talking of empty directories, it's not the only example I've come across: in my ldc2 snap, I wind up with an empty dir: usr/li

Re: snapd available in Trusty Tahr

On 07/02/17 21:17, Thomas Voß wrote: https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724 was released to the updates pocket today. Thanks! I'll hopefully be able to report back to you tomorrow whether all works as expected. -- Snapcraft mailing list Snapcraft@list

Re: license.txt and snap/ directory

On 07/02/17 11:26, Sergio Schvezov wrote: Can you log a bug against snapd? https://bugs.launchpad.net/snapd/+filebug Done :-) https://bugs.launchpad.net/snapd/+bug/1662951 -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm

Re: license.txt and snap/ directory

On 08/02/17 17:52, Gustavo Niemeyer wrote: The discussion above felt like painting an incorrect picture of what we're aiming at. We *definitely* want to track license information inside the snap format in a proper location. We want to support both basic cases such as just listing a well known nam

Re: launchpad snap recipe fails with classic confinement

On 09/02/17 18:09, Sergio Schvezov wrote: El jueves, 9 de febrero de 2017 13h'40:03 ART, knitzsche escribió: Is building a snap with *classic* confinement from a recipe supported on lp? I created a snap recipe for my imported git branch and tried to build, and the builds fail with: Even thou

Re: snapd available in Trusty Tahr

On 08/02/17 17:15, Joseph Rushton Wakeling wrote: On 07/02/17 21:17, Thomas Voß wrote: https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724 was released to the updates pocket today. Thanks! I'll hopefully be able to report back to you tomorrow whether all wor

LDC compiler snap issues on 14.04 (ABI compatibility?)

Hi all, So, earlier today I tried out my ldc2 snap on an Ubuntu 14.04 system for the first time. sudo snap install --classic --edge ldc2 worked just fine, but I ran into problems as soon as I tried to compile a simple 'hello world' program: void main() { import std.stdi

Re: LDC compiler snap issues on 14.04 (ABI compatibility?)

On 10/02/17 21:41, Joseph Rushton Wakeling wrote: Running `ldc -v` for verbose output, the precise call that segfaulted was: /usr/bin/gcc hello.o -o hello -L/snap/ldc2/3/bin/../lib -lphobos2-ldc -ldruntime-ldc -Wl,--gc-sections -lrt -ldl -lpthread -lm -m64 My suspicion is that that `libphobos2

Re: LDC compiler snap issues on 14.04 (ABI compatibility?)

On 11/02/17 00:48, Seth Arnold wrote: Hi Joe, can you grab the dmesg output that might include DENIED lines as well as the kernel's segfault report? Sure -- thanks for the thought! :-) I just reproduced the issue in a VirtualBox install of 14.04 to get these details. Kernel report in kern.lo

Re: LDC compiler snap issues on 14.04 (ABI compatibility?)

On 11/02/17 17:31, Joseph Rushton Wakeling wrote: And `dmesg | grep -i gcc` gave this output: Slightly more detailed dmesg output from `dmesg | grep -e "gcc" -e "ldc2"`: [0.00] Linux version 4.4.0-62-generic (buildd@lcy01-33) (gcc version 4.8.4 (Ubuntu 4.8.4-2ub

Re: LDC compiler snap issues on 14.04 (ABI compatibility?)

On 11/02/17 17:31, Joseph Rushton Wakeling wrote: I just reproduced the issue in a VirtualBox install of 14.04 to get these details. Kernel report in kern.log: Feb 11 17:16:19 vb1404 kernel: [ 534.781526] traps: gcc[6209] general protection ip:7f6632d1b1ee sp:7fff0a09e2f0 error:0 in libc-2.23

Re: pro tip: use scriptlets instead of custom plugins

On 17/02/17 00:11, Leo Arias wrote: This week I've been cleaning a few of my old snaps, using some of the new features in more recent versions of snapcraft. At first I wasn't convinced about scriptlets, but now I think they are great. Take a look at this diff: Thanks so much for that tip -- the

Re: snapcraft 2.27 has been released

On 17/02/17 13:49, Sergio Schvezov wrote: ## classic confinement Improvements have been made to the experimental `classic` confinement build setup to be more robust and reliable. These improvements allow to build `classic` confined snaps that work across a wider set of OS releases (particular

Re: snapcraft 2.27 has been released

On 18/02/17 17:58, Sergio Schvezov wrote: The bad news is that running the snapped applications seems to run into trouble. I'm presuming this is a snapcraft issue rather than snapd since already-installed classic snaps built with snapcraft 2.26 seem fine. This is due to the fact that we are n

Re: LDC compiler snap issues on 14.04 (ABI compatibility?)

On 16/02/17 05:10, Sergio Schvezov wrote: I'll check your snap first thing once I am at a computer again. From experience with classic confinement though, stage-packages to provide runnables are most of the time the root cause. There was discusssion on having ld set --library-path in be core sna

Re: Determining the set of snapd capabilities

On 19/02/17 12:21, Mark Shuttleworth wrote: We have a nice mechanism to ensure that snaps which use newer capabilities don't end up on systems with older snapd's that don't support those capabilities, which is the 'assumes' keyword. This email is a proposal to make that usable. This would be su

Re: Determining the set of snapd capabilities

On 19/02/17 15:26, Sergio Schvezov wrote: It was my intention to fully document this. I just did half of the job as I only added information about it under the python plugin update. Sorry about this. I have updated the release notes[1] so the next person doesn't fall into this time sync trap!

Position-independent code and Ubuntu 16.10

Hello all, Turns out my ldc2 compiler snap fails to work correctly on Ubuntu 16.10. When linking programs it falls over with the following message: /usr/bin/ld: /snap/ldc2/4/bin/../lib/libdruntime-ldc.a(errno.c.o): relocation R_X86_64_PC32 against symbol `__errno_location@@GLIBC_2.2.5' can n

Re: Position-independent code and Ubuntu 16.10

On 21/02/17 22:47, Seth Arnold wrote: On Mon, Feb 20, 2017 at 10:12:25PM +0100, Joseph Rushton Wakeling wrote: First, I'd thought that Ubuntu 16.04's GCC already generated position-independent code by default, but was this in fact only introduced with 16.10 ... ? Correct, this was c

Re: Position-independent code and Ubuntu 16.10

On 22/02/17 00:08, Seth Arnold wrote: Libraries are usually compiled as position independent code; this has not changed. OK, fair enough. In my case I think it was the C-library parts of the D standard library that were being compiled without PIC. Seems OK to assume this may have been a pro

Re: Position-independent code and Ubuntu 16.10

On 22/02/17 00:39, Joseph Rushton Wakeling wrote: OK, fair enough. In my case I think it was the C-library parts of the D standard library that were being compiled without PIC. Seems OK to assume this may have been a project-specific thing, then (which is now fixed upstream). Just for the

Further ABI-related issues for ldc2 snap on 14.04 ... ?

Hello all, I've encountered a couple of further issues with the ldc2 compiler snap when it's installed on a 14.04 system. I'm sharing here to confirm if these are indeed ABI issues which might be fixable in terms of how snapcraft constructs the package. The first [1] relates to zlib, which

Creating and running tests for a snapcraft plugin

Hello all, I have started working on a snapcraft plugin for dub, a build/package manager for the D programming language. The plugin itself is ready (at least in a working draft), and now I'm working on the tests. Is there a simple way to run the tests for a single plugin, rather than the wh

Re: Snap refresh or new install stuck at 'Run configure hook of "core" snap if present'

On 24/02/17 14:08, Martin Winter wrote: Curious if anyone has seen the same. All my Ubuntu 16.04 Servers have this issue. (Approx 10 Servers which are part of my CI system) Saw the same on a Debian Sid install that I was using to test my ldc2 snap package a couple of days ago. However, it di

Re: Further ABI-related issues for ldc2 snap on 14.04 ... ?

On 05/03/17 14:10, Sergio Schvezov wrote: I think you have come to a cross roads where you will need to choose to either always use the linker from the core snap and link to things from your snap or provide multiple zlib targets for different versions of glibc (or any other library you want to li

Removing an unreleased package revision

Hello folks, Is there a mechanism for removing an unreleased package revision from the store? I'd like to get rid of revision 7 of the ldc2 snap, which has some issues on 16.10 that make it unsuitable for release (even to the Edge channel). Thanks & best wishes, -- Joe -- Snapcraft mai

Status of snapd on Arch Linux

Hello folks, Is there anyone here working on snapd on Arch? I ask because I recently tried it out on a fresh Arch install and ran into some issues. Installing snaps works fine in itself, and snap list is able to find the installed snaps. However, these issues arose as soon as I started tryi

build.snapcraft.io and GitHub groups

Hello all, I thought I'd give build.snapcraft.io a go for my ldc2 snap. Signing in was fine, and I was asked to give permission both for accessing my account and the ldc-developers group which I'm part of (where the ldc2 snap is managed). However, when being asked to choose a GitHub repo, I

Re: build.snapcraft.io and GitHub groups

On 18/03/17 01:29, Mark Shuttleworth wrote: On 17/03/17 16:49, Joseph Rushton Wakeling wrote: ... but is it possible to do this via a project registered on behalf of a team, instead of an individual user account? It *should* be, so if it isn't, thanks for the bug report :) It's a

Re: build.snapcraft.io and GitHub groups

On 18/03/17 02:42, Colin Watson wrote: As others have mentioned, this is definitely in our backlog. It's tricky to map the different models together in a way that doesn't end up locking people out just because (e.g.) a previous administrator of their GitHub organisation once created a snap for a

git clone and Launchpad build system

Is there an issue with using git source for parts of snap packages when using the Launchpad build system? I'm having consistent build failures for this; originally I tried switching from `git://` URLS to `https://`, but I'm still seeing the same errors, see e.g. https://launchpadlibrarian.net/

Re: git clone and Launchpad build system

On 18/03/17 14:46, Joseph Rushton Wakeling wrote: Is there an issue with using git source for parts of snap packages when using the Launchpad build system? I'm having consistent build failures for this; originally I tried switching from `git://` URLS to `https://`, but I'm still seein

Re: git clone and Launchpad build system

On 18/03/17 21:28, Joseph Rushton Wakeling wrote: On 18/03/17 14:46, Joseph Rushton Wakeling wrote: Is there an issue with using git source for parts of snap packages when using the Launchpad build system? I'm having consistent build failures for this; originally I tried switching from

Re: git clone and Launchpad build system

On 18/03/17 22:11, Gregory Lutostanski wrote: Launchpad builders have an issue with git where they do not proxy that connection, only https. Here the issue is that that github repo has submodules specified with the git: url schema (and its doing a recursive checkout of the source). The bug is ht

Re: Status of snapd on Arch Linux

On 20/03/17 20:21, Sergio Schvezov wrote: Does it work if you create a symlink of /var/lib/snapd/snap to /snap? One of the things classic confined snaps require is a fixed path to ld in core Unfortunately not: still 'execv failed: No such file or directory' :-( -- Snapcraft mailing list Snapc

Re: Triggering CI/snap builds on changes to snapcraft parts

On 20/03/17 11:37, Evan Dandrea wrote: Do you need better than day-level resolution? If not, I'd suggest using Travis' cron feature to create nightly builds: https://docs.travis-ci.com/user/cron-jobs/ Does that actually solve the problem described, though? I ask because as Loïc stated it, it'

Setting environment variables from within snapcraft.yaml

Hello folks, Is it possible to set environment variables to be used when creating a part of a snap? I guess one could use the `prepare:` scriptlet to do something like `export MY_VAR=whatever` but I'd like the environment variable to be set before I even pull the source. (If you're wonderin

Re: Status of snapd on Arch Linux

On 20/03/17 21:39, Gustavo Niemeyer wrote: * installing my ldc2 snap (`snap install --classic --candidate ldc2`) worked fine (it shows up in `snap list` as expected) but if I try to run /var/lib/snapd/snap/bin/ldc2 directly I get an error message: execv failed: No such file or

Re: Status of snapd on Arch Linux

On 20/03/17 23:14, Gustavo Niemeyer wrote: Most likely the snap was partly configured to run elsewhere, but not entirely. We really need to have someone looking into this package, preferably just restoring the standard /snap path. Can you rebuild the package and try that out? Would be a nice d

Meta-packages for snaps

Hello folks, Is it possible -- or are there plans for -- snap 'meta-packages' whose only job is to make sure that multiple related snap packages get installed together? The use-case I'm thinking of is a collective 'dlang' meta-package that would install a group of snaps each providing a diffe

Defining multiple (external) snap packages in a single git repo

Hello all, I've been discussing with some of the D language developers about how to move forward with snap packages for the core D tools. The D language project has a dedicated git repo for building packages for various targets [1] and the obvious place to define snap packages would be there

Re: Meta-packages for snaps

On 25/03/17 00:27, mhall119 wrote: Usually you would include all related tools in the same snap. Is there a need to having them separate if they all need to be installed together? Mostly that they don't technically _need_ to all be together. I mean, why not split stuff up if its components ca

Re: Defining multiple (external) snap packages in a single git repo

On 25/03/17 10:00, Mark Shuttleworth wrote: We could host multiple snapcraft.yamls in a repo, using some sort of snapcraft.*.yaml scheme, for example. So: snapcraft builds all snaps snapcraft snap foo builds snapcraft.foo.yaml Hmm, to be honest, I was thinking of a simpler se

Reserved project names and cooperative transfer of ownership

... yes, more questions :-) First, how problematic is it to organize a cooperative transfer of ownership of a reserved name between one snap publisher and another? I'm thinking of a case where a package might start as a 3rd-party project (read: yours truly) and then be made official later.

Re: Reserved project names and cooperative transfer of ownership

On 27/03/17 04:46, Michael Hall wrote: Good news, that's already there! In each appname section in your "apps:" definitions you can add a property names "aliases" that takes a yaml list of names you want to use. For example: name: snapname apps: appname: command: foo aliases:

Re: Meta-packages for snaps

On 27/03/17 04:33, Michael Hall wrote: Because your snap is going to pull in all of your dependencies, doing one snap per tool will likely result in more duplication and thus more disk space than providing it all as a single package. That's a very good point. On the other hand, the disk space

Re: ANN: snapcraft 2.28 has been released

On 30/03/17 21:54, Sergio Schvezov wrote: Prettier version of the release notes can be found on https://github.com/snapcore/snapcraft/releases/tag/2.28 Big thanks for this one! More specifically ... ### classic confinement With this release it should be now possible to use launchpad builde

Architecture-specific settings for snapcraft parts

Hello all, Recently I tried some ARM builds of the LDC snap package, and came across some issues where one of the custom C flags used were not supported: https://launchpadlibrarian.net/313662608/buildlog_snap_ubuntu_xenial_armhf_ldc2_BUILDING.txt.gz Is there any way to customize the settings f

Error with Launchpad uploading 403 Client Error: Forbidden

Hello all, Recently I was able to successfully set up Launchpad builds for my ldc2 snap. However, auto-upload to the store failed with a 403 Client Error: Forbidden. The error messages are no more informative than this, so anyone have any idea what's going on? Note that I haven't specified

Tracks for ldc2 snap package

Hello all, If I understand https://snapcraft.io/docs/reference/channels right, I'm supposed to ask here about this -- please let me know if I'm wrong :-) Could I please request for two tracks, named 1.1 and 1.2, to be enabled for the ldc2 snap package? Thanks and best wishes, -- Joe -

Re: Tracks for ldc2 snap package

On 06/04/17 14:55, Bret A. Barker wrote: I've added these tracks for you, let me know if you have any troubles or questions. All seems good! Thank you very much :-) -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/li

Snap packages as build dependencies of other snaps

Hello folks, Is it possible to specify an existing snap package (by track and release channel) as a build dependency of a part of another snap package? I'm interested specifically in the case of using an existing snap package to provide a compiler used to build another snap. From what I unde

Re: Snap packages as build dependencies of other snaps

On 09/04/17 01:24, XiaoGuo Liu wrote: can you do it by remote parts? you can find more info by: $ snapcraft update $ snapcraft search There are a number of existing parts there already. You can publish your own. That's a cool thing to know about. I'd consider it, but since the package I wan

Re: Snap packages as build dependencies of other snaps

On 09/04/17 05:19, Stuart Bishop wrote: This is tracked at https://bugs.launchpad.net/bugs/1677974 I don't know the time frame. I'm primarily interested in Launchpad building my snaps, which will also need updating once snapcraft can somehow handle snap package build dependencies. Thanks for t

Re: Architecture-specific settings for snapcraft parts

On 03/04/17 21:18, Joseph Rushton Wakeling wrote: Recently I tried some ARM builds of the LDC snap package, and came across some issues where one of the custom C flags used were not supported: https://launchpadlibrarian.net/313662608/buildlog_snap_ubuntu_xenial_armhf_ldc2_BUILDING.txt.gz Is

Re: Architecture-specific settings for snapcraft parts

On 09/04/17 16:12, Sergio Schvezov wrote: We have a grammar engine for stage-packages in place which I wish to propose to extend every key attribute in snapcraft. Sounds cool! Will look forward to trying it out when it lands :-) -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify se

Snapping LDC (LLVM-based D compiler)

Hello all, I thought I'd have a go at making a snap of LDC, the LLVM-based compiler for the D programming language. I recognize that snapping a compiler might be jumping ahead of the current intended use-case(s), but it's fun to see what could be possible -- and besides, D's compilers are upd

Re: Snapping LDC (LLVM-based D compiler)

On 28.08.2016 00:05, Mark Shuttleworth wrote: On 27/08/16 16:45, Joseph Rushton Wakeling wrote: It's been very exciting to see how straightforward most things are to get set up, Yeah, it's been fun here too working on a few holiday snaps :) Just the weekend, in my case, bu

Re: Snapping LDC (LLVM-based D compiler)

On 28.08.2016 18:28, Mark Shuttleworth wrote: Try $SNAP for the location of the snap root, and there are a few others like $SNAP_DATA and $SNAP_COMMON and $SNAP_USER_DATA and $SNAP_USER_COMMON which are writable directories (the COMMON ones are unversioned the others get snapshotted on update). T

Re: Snapping LDC (LLVM-based D compiler)

On 28.08.2016 23:21, Joseph Rushton Wakeling wrote: Just to make sure I don't head off in completely the wrong direction, is there a straightforward (or at least, advisable) way to include gcc and the C standard libraries in a snap, perhaps deriving from existing Ubuntu packages? I imagine

Re: Snapping LDC (LLVM-based D compiler)

On 29.08.2016 03:38, Andrew Wilkins wrote: I've been looking into doing this too, for llgo (Go compiler frontend for LLVM). Nice! :-) You need libc6-dev also. After including that, I was then met with another issue: libc.so is a linker script, and that uses absolute paths to point at the real

Re: Snapping LDC (LLVM-based D compiler)

On 30.08.2016 06:18, Andrew Wilkins wrote: Actually, editing the files isn't necessary at all. You can just pass the --sysroot option to gcc. I just hacked up a quick gcc snap which works: https://gist.github.com/axw/1d4b0206e11ff46a26439244224a4cc9 Cool stuff. As a gcc snap, this works fo

Re: Snapping LDC (LLVM-based D compiler)

On 31.08.2016 21:35, Joseph Rushton Wakeling wrote: First things first, run `snapcraft stage`. Then edit the auto-generated stage/etc/ldc2.conf and replace it with this: https://gist.github.com/WebDrake/229645efeca14fa54b0b1c82bcbb6477 ... which as you can see includes a compiler flag: `-gcc

Re: Snapping LDC (LLVM-based D compiler)

On 01.09.2016 23:18, Sergio Schvezov wrote: El 01/09/16 a las 18:06, Joseph Rushton Wakeling escribió: On 31.08.2016 21:35, Joseph Rushton Wakeling wrote: First things first, run `snapcraft stage`. Then edit the auto-generated stage/etc/ldc2.conf and replace it with this: https

Re: Snapping LDC (LLVM-based D compiler)

On 27.08.2016 22:45, Joseph Rushton Wakeling wrote: I thought I'd have a go at making a snap of LDC, the LLVM-based compiler for the D programming language. I recognize that snapping a compiler might be jumping ahead of the current intended use-case(s), but it's fun to see wha

Re: Snapping LDC (LLVM-based D compiler)

On 01.09.2016 23:52, Joseph Rushton Wakeling wrote: Now create a file `prime/bin/gcc.wrapper` with the following contents: https://gist.github.com/WebDrake/0081628d70b61e271006c9b8fa3454ef (This is basically the command-gcc.wrapper that would be generated if I were exposing the gcc command

DEPRECATED: 'license' defined in snapcraft.yaml

Just got the above error message as I was finishing up my LDC snap. What's the recommended way to include license information? I ask because the 'snapcraft syntax' page on snapcraft.io lists the `licence` attribute without any mention of deprecation or an alternative for it: http://snapcraft.

Working LDC snap [was: Re: Snapping LDC (LLVM-based D compiler)]

On 27/08/16 22:45, Joseph Rushton Wakeling wrote: I thought I'd have a go at making a snap of LDC, the LLVM-based compiler for the D programming language. A "final first draft" of the working snap is available here: https://github.com/WebDrake/ldc2.snap/pull/1 Obviously ev

Re: Working LDC snap [was: Re: Snapping LDC (LLVM-based D compiler)]

On 04/09/16 13:55, Joseph Rushton Wakeling wrote: On 27/08/16 22:45, Joseph Rushton Wakeling wrote: I thought I'd have a go at making a snap of LDC, the LLVM-based compiler for the D programming language. A "final first draft" of the working snap is available here: https://gith

  1   2   >