On Wed, 20 Dec 2006 20:39:46 +0300, Bo Ørsted Andresen
<[EMAIL PROTECTED]> wrote:
On Wednesday 20 December 2006 18:16, Mark Knecht wrote:
[SNIP]
I understand that every package is out there in some repository on the
web. I think Neil has pointed me toward it once or twice at least. The
problem is for a user type like me, and yes, I'm *purely* a user type,
it's a bit beyond my skillset today to go get it and build the overlay
myself.
Yes, http://sources.gentoo.org/viewcvs.py/gentoo-x86/ . And it contains
every
ebuild (and patch) that has ever been in the tree. It really isn't that
hard.
Looks like we have got a bug in the Gentoo handbook. This link should be
mentioned together with the recommendation for how often should I sync the
portage tree. I guess the right place is an annotation to the first
request to sync the tree. There are 3 problems for a new user not
discussed in the handbook:
If I get some problem, then why not to start all over again, that is, sync
a tree? Do so every 15 minutes and the rsync server promises to get angry.
I did not do that but found the advice on the maximum syncing rate way too
late.
If I have a problem with sync (as I had some network problem installing
from Knoppix live CD), it is good to know (not to guess) that I do not
need to sync at all if I just downloaded the latest tree.
When SHOULD I sync again? That is, for how long may I not to sync and
expect that ebuilds can find the files they need to download at the
expected locations? It looks like this depends on the good will of 3-d
parties, for example, I will get nVidia legacy drivers only if nVidia
keeps them on their site or the mirror I use keeps them. I still do not
know for how long old ebuilds keep working. I understand that some ebuilds
can stop working any time when a 3-d party changes the file they do not
allow to put on mirrors, but what is normal for an ebuild?
--
Andrei Gerasimenko
--
gentoo-user@gentoo.org mailing list
