On Wed, Sep 13, 2006, Adam D. Morley wrote:
The problem is two-fold: first, cURL has to be proxy-aware to fetch the
RDF indices and second, RPM has to be proxy-aware for fetching the RPM
packages. The problem is that making cURL proxy-aware is simply a matter
of setting the "ftp_proxy" environment variable. Unfortunately, our RPM
4.2 supports only HTTP(!) proxies or REAL FTP(!) proxies, i.e., it does
NOT support a WWW proxy to which you speak HTTP but request a FTP URL.
It really just supports real old-style FTP proxies (most people have
even never seen those beasts ;-). RPM 4.4 seems to be smarter there (as
it uses NEON) and should allow regular proxies to be used if I looked
correctly into its source.
It certainly _is_ doable. Either by doing the RPM 4.4 upgrade (which we
need sometime in the future anyway and which I would recommend to do) or
by hacking in support for FTP-via-HTTP proxying into RPM 4.2 (which I do
not really recommend, but which could be an acceptable hack).
But you already got it, Adam: both are larger and rather thankless tasks
which certainly will never be done by anybody of the community in their
private freetime -- or else it would have already been done, as the
issue is a well known one since a longer time. But that doesn't mean the
issue never can be resolved for OpenPKG: one can order the Development
Services of the OpenPKG GmbH (see http://www.openpkg.com/services/) and
let this issue be resolved for a fee. The RPM 4.4 upgrade I expect to
require about 5-10 man-days, the RPM 4.2 proxy hack I expect to require
about 4-6 man-days.
The total amount of efforts is more for the RPM 4.4 upgrade but one also
gets a lot of really good new things (optional rock-solid SQLite instead
of the sensible Berkeley-DB for the RPM DB, NEON for network I/O, XML
exports, transactions, FTP EPSV support, etc) beside just the proxy
feature. Well, as nobody is neither willing to contribute the upgrade
itself nor pay for letting it done by someone else, perhaps we should do
some official "community fundraising" for finally gettings those longer
standing tasks to be resolved...
If you dont use a proxy and it is just a matter of going through a
firewall, this has worked for me till now:
Edit /prefix/*/*/build.pl and have a look for the two or three places
where curl is called. Remove the "-q" option.
In current, Ralph has already commited this change as far as I remember.
Then create a .curlrc in the user's home dir, you call the openpkg build
from. This is usually root.
Put the following klines in there:
--disable-epsv
--disable-eprt
Regards,
Torsten
--
Torsten Homeyer [EMAIL PROTECTED]
http://www.homeyert.net
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List openpkg-users@openpkg.org
