On Thursday 23 March 2006 19:16, Duncan wrote: > Chris Bainbridge posted <[EMAIL PROTECTED]>, > > excerpted below, on Thu, 23 Mar 2006 12:47:13 +0000: > > Adding the ebuilds to overlays is one option, but > > then other users will be expected to find an overlay with their > > package in, and then add it to make.conf. > > ... This hints at something I wasn't aware of. Does it mean that portage > already supports remote overlays, using them as it would a local overlay > only over HTTP/FTP/RSYNC, the the appropriate URL placed in make.conf, or > must the user manually sync the overlay to a local dir using whatever > protocol and let portage access the overlay from there? I had assumed a > separate manual sync was necessary. Was I assuming incorrectly? Can it > be as simple as putting the URL in make.conf? Wouldn't that be rather > resource intensive in terms of portage access to the remote server? Or > was the step of acquiring a local copy of that overlay simply omitted and > a reference to that local copy, not the global instance, assumed, when > mentioning putting it in make.conf? > > -- > Duncan - List replies preferred. No HTML msgs. > "Every nonfree program has a lord, a master -- > and if you use the program, he is your master." Richard Stallman in > http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html Hi, Using a remote overlays is rather simple, just do "emerge layman". Read the einfo and then "man layman". It works flawlessly, just tested this with one remote overlay. Beside that "man layman" explains pretty much of it's innerwork. PS:There's an article in "gentoo-wiki.com" with a list of overlays. HTH.Rumen
pgpJq5nfb3zgW.pgp
Description: PGP signature
