From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 3EC901391DB for ; Tue, 29 Jul 2014 11:00:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 482A9E08F5; Tue, 29 Jul 2014 11:00:18 +0000 (UTC) Received: from mail-vc0-f174.google.com (mail-vc0-f174.google.com [209.85.220.174]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 2B062E08D9 for ; Tue, 29 Jul 2014 11:00:16 +0000 (UTC) Received: by mail-vc0-f174.google.com with SMTP id la4so13284527vcb.19 for ; Tue, 29 Jul 2014 04:00:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=FIjrhQ0RKgaumbh2cZ+SEr/GrGm3NjfbGnhX5prbtcU=; b=Yqv4gN0GpBLFEbaTEEY8DtAxyXeX34//QDqLsWN2pnaTsDS/XlZSEZWxEyf/7baoWO hFo2Wr7TzZh8zroiESJMnwEEz889ufYIGLO79A37g85IKtbP3ERY0f91e90oSkMejIW5 JlilEr7A7lfs4QZH+7X1jUw2TyE3n4mxXQEAq+F4Ge7TASWulngBhJiARwzN1bVpYn48 EuUTN7Y5TcuBTlMu8KKZVs0suv8n7xSEfCgtSHTaExgpswxQplSvz6RKL1CyTL1WzS/N BcTqA7zRBDlRkwzsG+SWWygrolCOhdy/X82im11wSZgrup2w8v9e083VHfD8MtU5MU5b 7pNg== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.220.164.198 with SMTP id f6mr798143vcy.51.1406631616253; Tue, 29 Jul 2014 04:00:16 -0700 (PDT) Sender: freemanrich@gmail.com Received: by 10.52.8.229 with HTTP; Tue, 29 Jul 2014 04:00:16 -0700 (PDT) In-Reply-To: References: <20140729112936.06593412@digimed.co.uk> Date: Tue, 29 Jul 2014 07:00:16 -0400 X-Google-Sender-Auth: CPFH4wMaMJZVKwb_Af2JOOVxqzE Message-ID: Subject: Re: [gentoo-user] a question about updating process From: Rich Freeman To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: d98d7ff1-bdb9-437b-8155-9d7732afcaa9 X-Archives-Hash: d6f29dfa9a38455c67cd34be769e55e1 On Tue, Jul 29, 2014 at 6:52 AM, behrouz khosravi wrote: > well chromium was just an example. I just think that when there is a version > upgrade, a patch should be enough. For things like backports you're fairly likely to only get a patch. However, for an upstream version change (which chromium seems to have every other week) you're probably going to get a full tarball. > I have read that portage is migrating to git, but I guess I got it wrong, > because I thought that the source codes will be maintained using git too. > However why not? why not use git for source maintenance too? Portage probably will migrate to git at some point, but when it does you'll probably not notice a thing. Gentoo doesn't maintain the source to chromium - upstream does. In some cases Gentoo doesn't even redistribute the source (licensing issues). For chromium Google publishes a tarball on googleapis.com and Gentoo mirrors it. There has been talk about creating some kind of source repository for things like patches/etc, but that isn't going to really change when we distribute patches vs upstream tarballs. Generally speaking upstream tarballs are preferred over patches to keep things simple. With what we do now you know you're basically getting chromium as upstream distributes it. If we were to just mirror chrome-25 and 300 binary diffs to patch it up to the current version nobody could keep track of it all, and while you'd save some space on each upgrade your first install might involve downloading 10GB of diffs unless we went even further and had a variety of full vs incremental files. This has been discussed in terms of having portage on squashfs and just doing it for our own stuff looks to be fairly painful, let alone doing it for every upstream out there. Rich