public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Gerion Entrup <gerion.entrup@flump.de>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [RFC] multiversion ebuilds
Date: Sat, 12 May 2018 16:38:52 +0200	[thread overview]
Message-ID: <28267496.CN8iVfeXth@gump> (raw)
In-Reply-To: <CAAD4mYg5K0onfb72uRoiVLQp4iAE7Ag+mUJ_NQP3gL0peh_nSg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 557 bytes --]

Am Samstag, 12. Mai 2018, 16:24:00 CEST schrieb R0b0t1:
> On Sat, May 12, 2018 at 7:20 AM, Gerion Entrup <gerion.entrup@flump.de> wrote:
> > - The size of the tree reduces.
> >
> 
> If this is a big concern you may be able to mount the portage tree
> under a compressed loopback filesystem. It may even be worth
> considering that as a recommended-by-handbook default as the benefit
> for compressing the ebuilds is likely huge anyway.
This seems reasonable. However, first duplicating code and then deduplicate it at file system level seems weird.

Gerion

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

  reply	other threads:[~2018-05-12 14:38 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-12 12:20 [gentoo-dev] [RFC] multiversion ebuilds Gerion Entrup
2018-05-12 13:47 ` Rich Freeman
2018-05-12 14:13   ` Gerion Entrup
2018-05-12 14:21 ` Ulrich Mueller
2018-05-12 14:36   ` Gerion Entrup
2018-05-12 15:23     ` Dennis Schridde
2018-05-12 14:24 ` R0b0t1
2018-05-12 14:38   ` Gerion Entrup [this message]
2018-05-12 19:49 ` Georgy Yakovlev
2018-05-15  9:32 ` Mathy Vanvoorden
2018-05-16  4:15   ` [gentoo-dev] " Duncan
2018-05-16  4:22     ` R0b0t1
2018-05-16  6:15       ` Martin Vaeth
2018-05-16  6:26 ` [gentoo-dev] " Paweł Hajdan, Jr.
2018-05-16  6:46   ` Ulrich Mueller
2018-05-16  7:12     ` Ulrich Mueller
2018-05-16  7:38 ` Michał Górny
2018-05-16 23:33   ` R0b0t1
2018-05-17 15:44   ` Gerion Entrup
2018-05-17 16:16     ` Rich Freeman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=28267496.CN8iVfeXth@gump \
    --to=gerion.entrup@flump.de \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox