public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] a question about updating process
Date: Tue, 29 Jul 2014 13:25:13 +0200	[thread overview]
Message-ID: <53D78499.8000703@gmail.com> (raw)
In-Reply-To: <CAO5-k+p87b9N5WXZj1F3zWMaC-U=aQCwyWoh_YuH4D7Ux+vCbQ@mail.gmail.com>

On 29/07/2014 12:52, behrouz khosravi wrote:
> well chromium was just an example. I just think that when there is a
> version upgrade, a patch should be enough.
> 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?

The tree will OneDayRealSoonNow(TM)IPromise[1] be hosted in git.

Source tarballs? No. They belong to upstream and gentoo will do as
gentoo always has - follow upstream.

The downsides to running gentoo are

1. Lots of compiling
2. Lots of downloading

There is nothing we can do to reduce these downsides - that is the price
of the amazing flexibility from USE.

If you can't afford the downloads, you must switch to another distro, or
use a proxy. But it's not something Gentoo can solve



[1] Excuse the sarcasm, it's a gentoo in-joke how long this is taking
(or if it will ever be complete at all)



> 
> regards.
> 
> 
> On Tue, Jul 29, 2014 at 2:59 PM, Neil Bothwick <neil@digimed.co.uk
> <mailto:neil@digimed.co.uk>> wrote:
> 
>     On Tue, 29 Jul 2014 14:38:04 +0430, behrouz khosravi wrote:
> 
>     > I was trying to emerge chromium and I noticed that it should download
>     > about 200 Mb, and no wonder cause it is source files, not binary
>     > executable. However I wanted to know that if a new version of chromium
>     > comes out, an update will download another 200 Mb or just a diff files
>     > to patch the altered files ? (I am a new user and I have not
>     > experienced that situation!)
> 
>     It will download the source for the new version, which is generally a
>     separate tarball, so another 200MB. That's how Gentoo works, with very
>     few exceptions that source is downloaded and compiled.
> 
>     If you want to avoid the large download and lengthy compile time of
>     chromium, use www-client/google-chrome instead, this is the pre-compiled
>     binary from Google.
> 
> 
>     --
>     Neil Bothwick
> 
>     EMail - garbage at the speed of light.
> 
> 


-- 
Alan McKinnon
alan.mckinnon@gmail.com



  parent reply	other threads:[~2014-07-29 11:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-29 10:08 [gentoo-user] a question about updating process behrouz khosravi
2014-07-29 10:29 ` Neil Bothwick
2014-07-29 10:52   ` behrouz khosravi
2014-07-29 11:00     ` Rich Freeman
2014-07-29 11:25       ` thegeezer
2014-07-29 11:43         ` Neil Bothwick
2014-07-29 11:25     ` Alan McKinnon [this message]
2014-07-29 11:45       ` behrouz khosravi
2014-07-29 11:50         ` Alan McKinnon
2014-07-31 10:36           ` Samuli Suominen
2014-07-30 14:42         ` [gentoo-user] " James
2014-07-30 19:33           ` behrouz khosravi
2014-07-31  8:38             ` Peter Humphrey
2014-07-31  9:59               ` behrouz khosravi
2014-07-30 21:27           ` [gentoo-user] " Stroller
2014-07-29 13:17 ` Ján Zahornadský
2014-07-29 13:38   ` behrouz khosravi

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=53D78499.8000703@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@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