Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Sven Vermeulen <swift@g.o>
Subject: emerge rsync obsolete?
Date: Sun, 11 May 2003 13:27:00 +0200
Hi,

I'm planning on substituting every "emerge rsync" I can find in the docs to
"emerge sync". Is there *any* reason why I should not do it?

AFAIK is Portage 2.0.47-r10 stable on all supported architectures and
2.0.47-r10 has /usr/bin/emerge with "sync" being the same as "rsync":

[...]
                if x[2:]=="rsync":
                    #print
                    #print red("*** --rsync has been deprecated.")
                    #print red("***   Please use '--sync' instead.")
                    x="--sync"
[...]
            if x=="rsync":
                #print red("***   Please use '--sync' instead.")
                x="sync"
[...]
if myaction in ["sync","rsync"] and (not "--help" in myopts):
[...]


Wkr,
	Sven Vermeulen

PS CC'd to gentoo-docs-review as requested by the Gentoo Documentation Policy

-- 
Thanks to DRM, you know that something has been built in environment of 
unspecified degree of security, from source you cannot check, written by 
programmers you don't know, released after passing QA of unknown quality and 
which is released under a license that disclaims any responsibility...

--
gentoo-dev@g.o mailing list

Replies:
Re: emerge rsync obsolete?
-- Grant Goodyear
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
problems with emerge Mono
Next by thread:
Re: emerge rsync obsolete?
Previous by date:
problems with emerge Mono
Next by date:
[ANNOUNCE] Ebuild Janitor project


Updated Jun 17, 2009

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.