[gentoo-user] how to use layman --sync ALL across a firewall
Hello, At work, I typically use emerge-webrsync to sync the portage tree. But I don't know how to sync the layman tree. This layman --sync ALL does not work. I guess because git pull does not work across the firewall. Is there a solution to this besides requesting a firewall exception? Thanks, -- Valmor
Re: [gentoo-user] how to use layman --sync ALL across a firewall
Am 17.08.2011 18:27, schrieb Valmor de Almeida: Hello, At work, I typically use emerge-webrsync to sync the portage tree. But I don't know how to sync the layman tree. This layman --sync ALL does not work. I guess because git pull does not work across the firewall. Is there a solution to this besides requesting a firewall exception? Thanks, -- Valmor Well, at least some overlays support fetching via http. `layman -L` shows all available URLs for fetching. In /etc/layman/layman.cfg, you can also specify a proxy. In theory, that should allow you to fetch all these overlays. The remaining problem is: How do you tell layman to prefer the http connection over the native protocol? I haven't found such an option. Maybe you have to try it out yourself or open a bug for a feature request. Worst case: create your own overlay list which only contains the http connections. The documentation shows how to do this. Hope this helps, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] how to use layman --sync ALL across a firewall
On 08/17/2011 02:45 PM, Florian Philipp wrote: Am 17.08.2011 18:27, schrieb Valmor de Almeida: Hello, At work, I typically use emerge-webrsync to sync the portage tree. But I don't know how to sync the layman tree. This layman --sync ALL does not work. I guess because git pull does not work across the firewall. Is there a solution to this besides requesting a firewall exception? Thanks, -- Valmor Well, at least some overlays support fetching via http. `layman -L` shows all available URLs for fetching. In /etc/layman/layman.cfg, you can also specify a proxy. In theory, that should allow you to fetch all these overlays. The remaining problem is: How do you tell layman to prefer the http connection over the native protocol? I haven't found such an option. Maybe you have to try it out yourself or open a bug for a feature request. Worst case: create your own overlay list which only contains the http connections. The documentation shows how to do this. Hope this helps, Florian Philipp Thanks for the inputs. -- Valmor
