Re: Meta-packages for snaps

2017-03-29 Thread Joseph Rushton Wakeling

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 issue isn't likely 
to be so great in the grand scheme of things, whereas providing tools separately 
may allow greater freedom in updating their individual versions (these are not 
things all deriving from one repo or one release series).



If your users are likely to want more than one of these tools, I would
recommend just providing them all in one package. That way it's still
easy for them to install with a single command, and they will have
everything they might want already there.


Fair enough.  This actually dovetails quite nicely with the planned use-case, 
which is snap packages for all the core D utilities: the D core devs I'm talking 
with are probably in favour of a single snap providing all the utilities.  I 
will probably follow up on this soon :-)


Overall, though, I still think it'd be nice to have the flexibility (as a 
publisher) to choose between a single snap with multiple commands, versus a 
meta-snap that ensures multiple different independent snaps are installed.


--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Meta-packages for snaps

2017-03-26 Thread Michael Hall
On 03/24/2017 07:40 PM, Joseph Rushton Wakeling wrote:
> 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 can be provided independently,
> allowing the user to pick what bits they want (or not)?
> 
> Maybe I'm hanging on too much to the deb world, but multiple independent
> packages with a meta-package to provide the recommended collection,
> seems like a good pattern in general.  But from your answer, I take it
> that it's not currently possible?
> 

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.

If your users are likely to want more than one of these tools, I would
recommend just providing them all in one package. That way it's still
easy for them to install with a single command, and they will have
everything they might want already there.


Michael Hall
mhall...@ubuntu.com

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Meta-packages for snaps

2017-03-24 Thread Joseph Rushton Wakeling

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 can be provided independently, allowing the 
user to pick what bits they want (or not)?


Maybe I'm hanging on too much to the deb world, but multiple independent 
packages with a meta-package to provide the recommended collection, seems like a 
good pattern in general.  But from your answer, I take it that it's not 
currently possible?


--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Re: Meta-packages for snaps

2017-03-24 Thread mhall119
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?

On Mar 24, 2017 6:42 PM, "Joseph Rushton Wakeling" <
joseph.wakel...@webdrake.net> wrote:

> 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 different tool relating to
> the D programming language.
>
> Thanks & best wishes,
>
> -- Joe
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
> an/listinfo/snapcraft
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft


Meta-packages for snaps

2017-03-24 Thread Joseph Rushton Wakeling

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 different tool relating to the D 
programming language.


Thanks & best wishes,

-- Joe

--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft