34724 – Improve portage syncing ( cvsup ).

Bug 34724 - Improve portage syncing ( cvsup ).

Summary: Improve portage syncing ( cvsup ).

Status:	RESOLVED LATER

Alias:	None

Product:	Portage Development
Classification:	Unclassified
Component:	Enhancement/Feature Requests (show other bugs)
Hardware:	All Linux

Importance:	High enhancement (vote)
Assignee:	Portage team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2003-11-29 14:21 UTC by Nicko Lukianov
Modified:	2011-10-30 22:35 UTC (History)
CC List:	0 users

See Also:
Package list:
Runtime testing required:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Nicko Lukianov 2003-11-29 14:21:51 UTC

to sync portage tree i need to sync all the ebuilds. its stupid, killing gentoo
servers bandwidth and users bandwidth, 
it will be smart to use something like cvsup from BSD to sync single ports(ebuilds).
for example: i want to sync only /usr/portage/sys-kernel.
and for doing that i need to sync the hole portage tree.



Reproducible: Always
Steps to Reproduce:
1. support anonymoust cvs

Actual Results:  
killed my bandwidth

Comment 1 Marius Mauch (RETIRED) gentoo-dev

2003-12-01 21:31:57 UTC

anonymous cvs was offered in the past but disabled due to server load. rsync tries  to minimize the bandwith by using diffs and compression, a typical `emerge --sync` shouldn't cause more than 1 or 2 MB of traffic (assuming you sync at least weekly). cvsup is an option for portage-ng but needs some major work done before it can be deployed.