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 08D5913877A for ; Fri, 1 Aug 2014 17:07:30 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 22D28E09AD; Fri, 1 Aug 2014 17:07:24 +0000 (UTC) Received: from mail-qa0-f45.google.com (mail-qa0-f45.google.com [209.85.216.45]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 09FE7E0969 for ; Fri, 1 Aug 2014 17:07:22 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id cm18so4136437qab.4 for ; Fri, 01 Aug 2014 10:07:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=6QiDS4n5ikz7sSIKJCzE64VqivkTTG4CcGPaCXqHv/Q=; b=npYJKzNMj8x39wnjUvwyzQD41V4aYT0s81Dp0tkqDT4OvEum6W5q1cuHFmuun9jbEE vEEfDzKN9sC+8/Hgg7BSqzUSQV4KYhHrqoCdU0ZeOZY8dRgzA6DlXATP5HpW9G4+jEi1 JKk0DijYPZUwJa8Np1+PlqqvutkJaIqXDGUQGC5dx/TtQCEod8LHqUfQ1zsOB/NbWuae 7jLCvolIK0+YrnmZsSAfevyZ2PzUIIcc3z7nFxZea/Y79OjJX0GPAaPK/6OQoXuBVBNt 0yxrRvYZGJifqNQ4sbMbaKWe16Oqx1PipmAedvv/vMwC87wpHGNAl9eJF9LI+qSgUULv pzrA== 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.140.89.197 with SMTP id v63mr10731976qgd.71.1406912841647; Fri, 01 Aug 2014 10:07:21 -0700 (PDT) Received: by 10.140.108.246 with HTTP; Fri, 1 Aug 2014 10:07:21 -0700 (PDT) In-Reply-To: References: Date: Fri, 1 Aug 2014 10:07:21 -0700 Message-ID: Subject: Re: [gentoo-user] a question about emerge --sync From: Douglas J Hunley To: gentoo-user@lists.gentoo.org Content-Type: multipart/alternative; boundary=001a11c13e30286af304ff946ce0 X-Archives-Salt: 9786700c-fa18-4b9f-9cba-61a54957e694 X-Archives-Hash: a5b979cbea52abe7b3cbe8e4fd7b430f --001a11c13e30286af304ff946ce0 Content-Type: text/plain; charset=UTF-8 On Fri, Aug 1, 2014 at 7:30 AM, behrouz khosravi wrote: > Is it save to sync my portage not very often, say every month or two, > so when I install something I wont be warned that some of my packages > are outdated? > In this manner I wont need to mask my packages, to prevent them from > updating, right ? > You seem to be slightly confusing two different things. There is 'emerge --sync' (or emerge-webrsync) which maintains your copy of the portage tree and then there's 'emerge --update' which actually downloads the source, compiles, and then installs it. Running 'emerge --sync' or 'eix-sync' or 'emerge-webrsync' downloads *very* little (ebuild files, updates to package masks, etc). There's nothing stopping you from running a sync every day but only *updating* packages every month. The two are separate operations. It's probably not a bad idea to sync relatively often so you can see what changes are happening and can 'eselect news read' to keep up with announcements even if you don't plan on actually upgrading for long periods of time -- Douglas J Hunley (doug.hunley@gmail.com) Twitter: @hunleyd Web: about.me/douglas_hunley G+: http://google.com/+DouglasHunley --001a11c13e30286af304ff946ce0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Fri, Aug 1, 2014 at 7:30 AM, behrouz khosravi <bz.khosravi@gmail.co= m> wrote:
Is it save to sync my portage not very often, say every month = or two,
so when I install something I wont be warned that some of my packages
are outdated?
In this manner I wont need to mask my packages, to prevent them from
updating, right ?

You seem to be slightly confu= sing two different things. There is 'emerge --sync' (or emerge-webr= sync) which maintains your copy of the portage tree and then there's &#= 39;emerge --update' which actually downloads the source, compiles, and = then installs it. Running 'emerge --sync' or 'eix-sync' or = 'emerge-webrsync' downloads *very* little (ebuild files, updates to= package masks, etc). There's nothing stopping you from running a sync = every day but only *updating* packages every month. The two are separate op= erations.=C2=A0

It's pr= obably not a bad idea to sync relatively often so you can see what changes = are happening and can 'eselect news read' to keep up with announcem= ents even if you don't plan on actually upgrading for long periods of t= ime

--
Douglas J= Hunley (doug.hu= nley@gmail.com)
Twitter: @hunleyd =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Web: about.me/douglas_hunley
G+: http://g= oogle.com/+DouglasHunley
--001a11c13e30286af304ff946ce0--