public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dennis Schridde <devurandom@gmx.net>
To: gentoo-dev@lists.gentoo.org
Cc: Gerion Entrup <gerion.entrup@flump.de>
Subject: Re: [gentoo-dev] [RFC] multiversion ebuilds
Date: Sat, 12 May 2018 17:23:00 +0200	[thread overview]
Message-ID: <3161610.Lf3jGJQ6dy@monk> (raw)
In-Reply-To: <1796959.TKVFouW9oh@gump>

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

On Saturday, 12 May 2018 16:36:13 CEST Gerion Entrup wrote:
> Am Samstag, 12. Mai 2018, 16:21:26 CEST schrieb Ulrich Mueller:
> > >>>>> On Sat, 12 May 2018, Gerion Entrup wrote:
> > > - The size of the tree reduces.
> > 
> > I very much doubt that (or at least it remains to be proven).
> > 
> > Currently, when an ebuild is copied for a version bump, it will reuse
> > the same blob in the Git repository. With the scheme above, you would
> > have to modify the ebuild, which would add a new blob for every
> > version bump.
> 
> You are right, I've not thought about that. However, this is only true for
> the repository not for the rsync copy most(?) users have and not for a
> checkout.

As I understand it, rsync will indeed re-use blocks from existing files on the 
receiver [1], and hence copy files with the same content only once.

--Dennis

[1]: http://www.anchor.com.au/blog/2013/08/out-tridging-tridge/

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

  reply	other threads:[~2018-05-12 15:23 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 [this message]
2018-05-12 14:24 ` R0b0t1
2018-05-12 14:38   ` Gerion Entrup
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=3161610.Lf3jGJQ6dy@monk \
    --to=devurandom@gmx.net \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gerion.entrup@flump.de \
    /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