Re: Tiny Guix (and containers)

Dave Love skribis: > Ludovic Courtès writes: > >>> It looks to me as if it would often help significantly, e.g. when a >>> pkg-config file, or something else sucks in a load of stuff that's >>> irrelevant for running the package. (Separating :lib and needing that

Re: Tiny Guix (and containers)

Ludovic Courtès writes: >> It looks to me as if it would often help significantly, e.g. when a >> pkg-config file, or something else sucks in a load of stuff that's >> irrelevant for running the package. (Separating :lib and needing that >> for building means you need to know

Re: Tiny Guix (and containers)

Ludovic Courtès writes: > Another reason is that splitting is just part of the story. Often, it’s > not moving out 10 KB of header files that really helps; rather, it’s > stripping the dependency graph. Oh, sure, and that probably isn't the reason for convention of splitting

Re: Tiny Guix (and containers)

Pjotr Prins writes: > For most software we just need the binary executable and its shared > libs. That is exactly what I package with my tool: > > For gemma the binary closure is only 18Mb. See > https://github.com/genetics-statistics/GEMMA/issues/90 > > That is small.

Re: Tiny Guix (and containers)

Heya, Dave Love skribis: > l...@gnu.org (Ludovic Courtès) writes: > >> Hi, >> >> Hartmut Goebel skribis: > >>> I'm in favor of (automatically?) splitting of "development" packages, >>> including the headers and the static libs (much like the "-devel"

Re: Tiny Guix (and containers)

Dave Love skribis: > Pjotr Prins writes: > >> But, really, I think when talking embedded systems and containers we >> all want tiny. Even HPC can benefit. Tiny containers may be an >> attractive proposition. > > Yes, containers aside, dependencies in

Re: Tiny Guix (and containers)

On Tue, Oct 31, 2017 at 02:11:36PM +, Dave Love wrote: > Pjotr Prins writes: > > > But, really, I think when talking embedded systems and containers we > > all want tiny. Even HPC can benefit. Tiny containers may be an > > attractive proposition. > > Yes,

Re: Tiny Guix (and containers)

l...@gnu.org (Ludovic Courtès) writes: > Hi, > > Hartmut Goebel skribis: >> I'm in favor of (automatically?) splitting of "development" packages, >> including the headers and the static libs (much like the "-devel" or >> "-dev" packages in other distributions. One

Re: Tiny Guix (and containers)

Pjotr Prins writes: > But, really, I think when talking embedded systems and containers we > all want tiny. Even HPC can benefit. Tiny containers may be an > attractive proposition. Yes, containers aside, dependencies in Guix are one of the reasons I'm currently

Re: Tiny Guix (and containers)

Hi, Hartmut Goebel skribis: > Am 26.10.2017 um 12:42 schrieb Pjotr Prins: >> Yes, I think that is what we should head for eventually. I vaguely >> remember a discussion about this on this ML and people were against >> separate outputs for doc, include, static-lib

Re: Tiny Guix (and containers)

Hello, Am 26.10.2017 um 12:42 schrieb Pjotr Prins: > Yes, I think that is what we should head for eventually. I vaguely > remember a discussion about this on this ML and people were against > separate outputs for doc, include, static-lib etc. What are you all > thinking now? Does it make sense

Re: Tiny Guix (and containers)

Pjotr Prins writes: >> > Now it takes forever to set up the image >> >> Have you tried disabling compression? This could be a lot faster. I >> found that tar with gzip compression is terribly slow to copy things >> from the store into a compressed tar archive.

Re: Tiny Guix (and containers)

Ricardo Wurmus skribis: >> 34M nnykzgwfy8mwh2gmxm715sjxykg8qjwn-binutils-2.28 > > “share/locale” is 9.4M. This is a cross-cutting concern. We don’t have > a way to globally filter locales to only requested locales. Even if we > split them each into a separate output

Re: Tiny Guix (and containers)

Hi Ricardo, Thanks for responding. I think this discussion belongs here. On Thu, Oct 26, 2017 at 09:02:56AM +0200, Ricardo Wurmus wrote: > > Pjotr Prins writes: > > > 22M 3x53yv4v144c9xp02rs64z7j597kkqax-gcc-5.4.0-lib > > According to “du”, this is 32M on my

Re: Tiny Guix (and containers)

Pjotr Prins writes: > 22M 3x53yv4v144c9xp02rs64z7j597kkqax-gcc-5.4.0-lib According to “du”, this is 32M on my disk. The “lib” subdir contains both shared libraries as well as ar archives for static linking; together they weigh in at 12MB. We may want to move

Re: Tiny Guix (and containers)

Another route is to create a container using just the essential dependencies, like I did here: https://gitlab.com/pjotrp/guix-relocatable-binary-packages/blob/master/README.org Binary with dependencies distribution down to 18Mb. Of course locales won't work ;) And yes, I am still using

Tiny Guix (and containers)

I have been playing around with containers to create something for a book: https://gitlab.com/pjotrp/guix-notes/blob/master/CONTAINERS.org these are (Docker) images that can be run by anyone - which is great! Only (minor) issue is the containers are 1.4GB in size. These are the biggies in