Paludis Logo Introduction Hooks environment.conf sets/
Bugs, Requests, Support Syncers keywords.conf / platforms.conf repositories/
Overview Fetchers use.conf / options.conf  
FAQ Env Vars licenses.conf / licences.conf  
Clients File Formats mirrors.conf  
Configuration Dep Specs package_mask.conf  
API specpath.conf bashrc  

Fetchers

Overview

Paludis makes use of scripts called 'fetchers' to do most downloading. Fetchers can be added for additional protocols (for example, if you need to use a third party ebuild where upstream distributes its sources via Gopher), and built-in fetchers can be replaced (for example, if you want to use something other than wget to fetch via http).

Standard Fetchers

Paludis ships with the following fetcher protocols:

User Defined Fetchers

To write your own fetcher for protocol proto, create an executable script named doproto (the do prefix is essential) and place it in SHAREDIR/paludis/fetchers/, where SHAREDIR is probably /usr/share. This directory has priority over the usual Paludis fetcher locations, so it can be used to override existing fetchers as well as creating new ones.

A fetcher is called with two parameters, the source URI and the destination filename. It indicates success or failure via its exit status.

For examples, consult the built-in fetchers, which can be found in LIBEXECDIR/paludis/fetchers/.