1 |
On Fri, 2006-09-08 at 18:27 -0400, Mike Kelly wrote: |
2 |
> On Fri, 08 Sep 2006 14:57:16 -0700 |
3 |
> "Vladimir G. Ivanovic" <vgivanovic@×××××××.net> wrote: |
4 |
> |
5 |
> > I run this script every hour: |
6 |
> > |
7 |
> > #!/bin/sh |
8 |
> > glsa-check -f new 2>/dev/null |
9 |
> > [[ $? -eq 0 ]] || echo "glsa-check: error" |
10 |
> > |
11 |
> > Does this not do what you're looking for? |
12 |
> |
13 |
> glsa-check draws its information from your local portage tree, so |
14 |
> unless you are syncing hourly, too, it won't do you any good. |
15 |
|
16 |
No, I'm not syncing portage every hour. Thanks for the info. |
17 |
|
18 |
> |
19 |
> |
20 |
> On Thu, 7 Sep 2006 15:30:57 -0400 |
21 |
> "Andy Dustman" <farcepest@×××××.com> wrote: |
22 |
> |
23 |
> > 2) Even with recent metadata cache update improvements, it still takes |
24 |
> > a long time, and a lot of resources, to sync the tree. |
25 |
> |
26 |
> There are some other methods of syncing your tree which may or may not |
27 |
> be faster for you, though. Take a look at emerge-webrsync (included |
28 |
> with sys-apps/portage), and emerge-delta-webrsync (included in |
29 |
> app-portage/emerge-delta-webrsync). |
30 |
> |
31 |
> The former pulls complete daily tarballs of the tree from a remote |
32 |
> location. This may slower. |
33 |
> |
34 |
> The latter pulls patches instead of full tarballs. As I understand it, |
35 |
> it's still fairly experimental, but it should, at least in theory, be |
36 |
> much less network intensive than rsync. |
37 |
|
38 |
I forgot about app-portage/getdelta and friends (mainly because I |
39 |
haven't used it.) It doesn't use websync, but like websync, it's |
40 |
supposed to make upgrading faster because only package differences are |
41 |
downloaded if you add |
42 |
|
43 |
FETCHCOMMAND="/usr/bin/getdelta.sh \${URI}" |
44 |
|
45 |
to your /etc/make.conf. I don't think deltup will help syncing. |
46 |
|
47 |
--- Vladimir |
48 |
|
49 |
-- |
50 |
Vladimir G. Ivanovic <vgivanovic@×××××××.net> |
51 |
|
52 |
-- |
53 |
gentoo-server@g.o mailing list |