| 1 |
> Another note to new developers considering a CVS only approach: |
| 2 |
> rsync mirrors distribute a partial Portage cache, cvs does not, so you |
| 3 |
> should be building this yourself via `emerge regen`. If you dont, things |
| 4 |
> will break in weird ways. |
| 5 |
|
| 6 |
Full ebuild cache. The only generation is an eclass cross reference |
| 7 |
table. Regen is absolutely not required... if there is something |
| 8 |
affected by that, either the ebuild is broken or there is a bug |
| 9 |
that needs to be reported. |
| 10 |
|
| 11 |
> Also, I highly advise against using CVS |
| 12 |
> checkout as a "real" overlay specified in make.conf.. this will force |
| 13 |
> Portage to rebuild the cache for this tree in addition to the rsync tree |
| 14 |
> and eat up cpu time needlessly. |
| 15 |
|
| 16 |
Very true, but Nakano has an enhancement to caching in CVS and |
| 17 |
testing portages that should kill this penalty for the most part. |
| 18 |
|
| 19 |
CVS over rsync is a bad idea in general though. You're likely to |
| 20 |
confuse yourself on which ebuild and eclasses are actually being |
| 21 |
used to acquire data and handle the package. Overlays should only |
| 22 |
be partial sets. |
| 23 |
|
| 24 |
--NJ |
| 25 |
|
| 26 |
|
| 27 |
-- |
| 28 |
gentoo-dev@g.o mailing list |
Archives