From: Fernando Rodriguez <cyklonite@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: emerge --sync
Date: Mon, 24 Oct 2016 12:36:04 -0400 [thread overview]
Message-ID: <cae17b1b-db0e-1855-49d8-2746c51c95b6@gmail.com> (raw)
In-Reply-To: <CAKpSnpJpx2qu7CJgyZTNFS0P-+hdKvd85bsMZ3ew==UocWGFYA@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 10/24/2016 11:35 AM, Jorge Almeida wrote:
> On Mon, Oct 24, 2016 at 8:29 AM, Martin Vaeth <martin@mvath.de> wrote:
>> Jorge Almeida <jjalmeida@gmail.com> wrote:
>>> I want to do emerge --sync on computer A and then update computer B by
>>> copying /usr/portage. Is this safe?
>>
>> Yes, although ...
>>
>>> does emerge --sync just updates the contents of /usr/portage
>>
>> portage also changes the content of /var/cache/edb, and in some
>> cases even of /var/db or even of binary packages, but it will
>> repeat the necessary steps automatically if only /usr/portage
>> has changed.
>>
>>
> Does this mean that the next time portage is used (e.g., as in "emerge
> -p ...") it will detect that /usr/portage is not consistent with
> /var/db... and will fix the latter?
Yes. And you will see the same output that your see at the end of emerge
- --sync (the profile updates phase, whatever it's called) when you run
emerge. To update the eix database you need to run eix-update.
But a more elegant solution is to emerge app-admin/gentoo-rsync-mirror and
setup your own rsync mirror.
> Jorge
>
- --
Fernando Rodriguez
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJYDjh0AAoJEPbOFX/5UlwckKsP+gJWRUQQvEzI9Zqu/6DXrCvw
tu3BMejUGngXr6ZAyMZZCXAqzNV1a9+4OrGTohwjYdwRMBni26yuapfGdKABw1kS
hVoM4yLwaos0VCET0gXUmQVWu8hnTgpTqOtFLEtCHjhr0NR1ic+xjr/B+edBxZUo
jNKjpARVggrD/IA56KFPUiRFtxnd2C4szmJH4pQuDoxrZg+mrnujGeMb8bIPmJ/f
yFYh/7hqwcFVUnt3YV0HUWv83FozXY+DdLEhZbAZTBtlaK1VhfjVaVPvbOVmVbpa
fFzYB4hz0gurhK/A3ulY5Upe7Gqpa5kimot2Ca70h2x1i7BSZoTUiBsDkvl0xqMT
YayMZ+FBzUZ+A+rv5v7cyXJCsiY7a9kTdzbR/gOl6joPEovna0MTMMK2mJFU8xW9
srsAFD1p1Fac8mkCvwdhTWt7yFJgkTf3kUC5l8/mY7WqzXh3Vki8IB+xI3/Zdohk
yjWRf4rCP3AKgQnbMV7f6R22GKmBvRcSTcO+L4W63UIotNeLb0eEZlWP5yQa+sfE
2nPSQZmR/HFlZ6ubUceFB/74FhgnZll9zHy76oIB53zQgslm9LRgypRX6S76G3CR
i7t26EWxVxK+GoGqan0nEyGKvwHorBfAPW8KC12nnany+7gtNQo3OcU7irJx+EXJ
qljNWt25JuLFwPHUBNxP
=26W6
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2016-10-24 16:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 15:21 [gentoo-user] emerge --sync Jorge Almeida
2016-10-24 15:29 ` [gentoo-user] " Martin Vaeth
2016-10-24 15:35 ` Jorge Almeida
2016-10-24 16:36 ` Fernando Rodriguez [this message]
2016-10-24 16:45 ` Jorge Almeida
2016-10-24 16:56 ` Rich Freeman
2016-10-24 17:44 ` Jorge Almeida
2016-10-24 18:02 ` Alarig Le Lay
2016-10-24 19:49 ` Rich Freeman
2016-10-24 20:27 ` Alarig Le Lay
2016-10-25 4:56 ` Miroslav Rovis
2016-10-24 21:16 ` [gentoo-user] " Håkon Alstadheim
2016-10-24 21:30 ` Dale
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=cae17b1b-db0e-1855-49d8-2746c51c95b6@gmail.com \
--to=cyklonite@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