From owner-freebsd-ports@FreeBSD.ORG Thu Jun 8 17:13:24 2006 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 97BE616D699 for ; Thu, 8 Jun 2006 15:31:30 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay03.ispgateway.de (smtprelay03.ispgateway.de [80.67.18.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6DF9043D69 for ; Thu, 8 Jun 2006 15:31:23 +0000 (GMT) (envelope-from freebsd-listen@fabiankeil.de) Received: (qmail 26070 invoked from network); 8 Jun 2006 15:31:21 -0000 Received: from unknown (HELO localhost) ([pbs]775067@[217.50.131.128]) (envelope-sender ) by smtprelay03.ispgateway.de (qmail-ldap-1.03) with SMTP for ; 8 Jun 2006 15:31:21 -0000 Date: Thu, 8 Jun 2006 17:31:10 +0200 From: Fabian Keil To: ports@FreeBSD.org Message-ID: <20060608173110.74dd3c56@localhost> X-Mailer: Sylpheed-Claws 2.1.1 (GTK+ 2.8.17; i386-portbld-freebsd6.1) X-PGP-KEY-URL: http://www.fabiankeil.de/gpg-keys/freebsd-listen-2006-08-19.asc User-Agent: 321 test Mime-Version: 1.0 Content-Type: multipart/signed; boundary="Sig_E9K3BA.q6Q2WR0W4Tp/cqwy"; protocol="application/pgp-signature"; micalg=PGP-SHA1 Cc: Subject: Questions regarding ports for trans-proxy-tor and dns-proxy-tor X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jun 2006 17:13:25 -0000 --Sig_E9K3BA.q6Q2WR0W4Tp/cqwy Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable I'm in the process of "porting" trans-proxy-tor and dns-proxy-tor. dns-proxy-tor already works out of the box and I have a patch to get trans-proxy-tor working as well, however I'd like to get your opinion on some port system specific problems. 1) trans-proxy-tor requires some perl header files. Does the port system have a special way to provide them or do I have to write a script? I couldn't find any information in the Porter's Handbook's Perl chapter, therefore I fear the latter. Those perl header files are created by running some of FreeBSD's header files through h2ph(1) which means FreeBSD's sources are required or /usr/include must be complete. Is there an easy way to specify which header files have to be available? 2) The master site is http://p56soo2ibjkx23xo.onion/ and it's only accessible through Tor. If Privoxy and Tor are running and configured, one could set HTTP_PROXY and fetching should work. However I guess this would create problems on the build servers, as they probably don't run Tor and Privoxy. Additionally FETCH_DEPENDS would only make sure that Privoxy and Tor are installed, not that they are configured to work together. I could mirror the tarball on the web and use it as a second master site. Would this be an acceptable solution, or would it still lead to problems on the build servers when the first master site appears to be constantly unreachable? A third solution would be to make the port interactive and have the user fetch the sources herself or confirm that Tor and Privoxy are configured as needed. Which way should I go here? 3) trans-proxy-tor and dns-proxy-tor come in one package, but dns-proxy-tor can be used without trans-proxy-tor. Do you agree that it makes sense to create two separate port and use dns-proxy-tor a dependency for trans-proxy-tor? Fabian --=20 http://www.fabiankeil.de/ --Sig_E9K3BA.q6Q2WR0W4Tp/cqwy Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (FreeBSD) iD8DBQFEiELGjV8GA4rMKUQRArzyAJ9dnK5XjEfdeGlx/yT168Gbyr6w/gCfceau UppFgtUzqBFYMo7HHXuw4HQ= =ic8M -----END PGP SIGNATURE----- --Sig_E9K3BA.q6Q2WR0W4Tp/cqwy--