On Fri, 2006-09-08 at 18:27 -0400, Mike Kelly wrote:
> On Fri, 08 Sep 2006 14:57:16 -0700
> "Vladimir G. Ivanovic" <[EMAIL PROTECTED]> wrote:
>
> > I run this script every hour:
> >
> > #!/bin/sh
> > glsa-check -f new 2>/dev/null
> > [[ $? -eq 0 ]] || echo "glsa-check: error"
> >
> > Does this not do what you're looking for?
>
> glsa-check draws its information from your local portage tree, so
> unless you are syncing hourly, too, it won't do you any good.
No, I'm not syncing portage every hour. Thanks for the info.
>
>
> On Thu, 7 Sep 2006 15:30:57 -0400
> "Andy Dustman" <[EMAIL PROTECTED]> wrote:
>
> > 2) Even with recent metadata cache update improvements, it still takes
> > a long time, and a lot of resources, to sync the tree.
>
> There are some other methods of syncing your tree which may or may not
> be faster for you, though. Take a look at emerge-webrsync (included
> with sys-apps/portage), and emerge-delta-webrsync (included in
> app-portage/emerge-delta-webrsync).
>
> The former pulls complete daily tarballs of the tree from a remote
> location. This may slower.
>
> The latter pulls patches instead of full tarballs. As I understand it,
> it's still fairly experimental, but it should, at least in theory, be
> much less network intensive than rsync.
I forgot about app-portage/getdelta and friends (mainly because I
haven't used it.) It doesn't use websync, but like websync, it's
supposed to make upgrading faster because only package differences are
downloaded if you add
FETCHCOMMAND="/usr/bin/getdelta.sh \${URI}"
to your /etc/make.conf. I don't think deltup will help syncing.
--- Vladimir
--
Vladimir G. Ivanovic <[EMAIL PROTECTED]>
--
[email protected] mailing list
