Snap packages as build dependencies of other snaps

2017-04-08 Thread Joseph Rushton Wakeling
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

2017-04-08 Thread XiaoGuo Liu
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. Best regards, XiaoGuo On Sun, Apr 9, 2017 at 12:51 AM, Joseph Rushton Wakeling < joseph.wakel...@webdrake.net> wrote: >

Re: Snap packages as build dependencies of other snaps

2017-04-08 Thread Joseph Rushton Wakeling
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

2017-04-08 Thread Stuart Bishop
On 9 April 2017 at 10:06, Joseph Rushton Wakeling wrote: > On 09/04/17 01:24, XiaoGuo Liu wrote: > The particular reason I would like to actually be able to use an existing > snap package as a build package is really that it seems like a waste of > effort to rebuild something that's already built

Re: Exposing commands

2017-04-08 Thread Stuart Bishop
On 7 April 2017 at 08:15, Bruno Rogerio Fernandes wrote: > There are one problem here: > I cannot expose some binaries like demux.pl or do_dssp as they both have > invalid characters on name, namely "." and "_" respectively. > What should I do in that case? I have to expose all that commands, and