| 1 |
On Fri, Aug 1, 2014 at 7:30 AM, behrouz khosravi <bz.khosravi@×××××.com> |
| 2 |
wrote: |
| 3 |
|
| 4 |
> Is it save to sync my portage not very often, say every month or two, |
| 5 |
> so when I install something I wont be warned that some of my packages |
| 6 |
> are outdated? |
| 7 |
> In this manner I wont need to mask my packages, to prevent them from |
| 8 |
> updating, right ? |
| 9 |
> |
| 10 |
|
| 11 |
You seem to be slightly confusing two different things. There is 'emerge |
| 12 |
--sync' (or emerge-webrsync) which maintains your copy of the portage tree |
| 13 |
and then there's 'emerge --update' which actually downloads the source, |
| 14 |
compiles, and then installs it. Running 'emerge --sync' or 'eix-sync' or |
| 15 |
'emerge-webrsync' downloads *very* little (ebuild files, updates to package |
| 16 |
masks, etc). There's nothing stopping you from running a sync every day but |
| 17 |
only *updating* packages every month. The two are separate operations. |
| 18 |
|
| 19 |
It's probably not a bad idea to sync relatively often so you can see what |
| 20 |
changes are happening and can 'eselect news read' to keep up with |
| 21 |
announcements even if you don't plan on actually upgrading for long periods |
| 22 |
of time |
| 23 |
|
| 24 |
-- |
| 25 |
Douglas J Hunley (doug.hunley@×××××.com) |
| 26 |
Twitter: @hunleyd Web: |
| 27 |
about.me/douglas_hunley |
| 28 |
G+: http://google.com/+DouglasHunley |
Archives