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 <[email protected] > <mailto:[email protected]>> 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 [email protected]
