From owner-freebsd-ports@FreeBSD.ORG Sat Mar 17 09:21:15 2007 Return-Path: X-Original-To: ports@FreeBSD.org Delivered-To: freebsd-ports@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0D24416A402 for ; Sat, 17 Mar 2007 09:21:15 +0000 (UTC) (envelope-from lwhsu@lwhsu.ckefgisc.org) Received: from knight.lwhsu.ckefgisc.org (lwhsu.Dorm7.NCTU.edu.tw [140.113.90.48]) by mx1.freebsd.org (Postfix) with ESMTP id CB2C613C43E for ; Sat, 17 Mar 2007 09:21:13 +0000 (UTC) (envelope-from lwhsu@lwhsu.ckefgisc.org) Received: by knight.lwhsu.ckefgisc.org (Postfix, from userid 1001) id DAF6711441; Sat, 17 Mar 2007 17:04:28 +0800 (CST) Date: Sat, 17 Mar 2007 17:04:28 +0800 From: Li-Wen Hsu To: gnn@FreeBSD.org Message-ID: <20070317090428.GA46256@knight.lwhsu.ckefgisc.org> References: <200702211000.l1LA0qVZ039693@freefall.freebsd.org> <12749.192.216.27.32.1173205452.squirrel@webmail.freeshell.org> <42419.192.216.27.32.1173288103.squirrel@webmail.freeshell.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="fdj2RfSjLxBAspz7" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.13 (2006-08-11) Cc: ports@FreeBSD.org, tmclaugh@sdf.lonestar.org, Li-Wen Hsu Subject: Re: FreeBSD ports: 1 unfetchable distfile: net/py-pypcap 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: Sat, 17 Mar 2007 09:21:15 -0000 --fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=big5 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On =A5|, 3 08, 2007 at 17:01:11 +0900, gnn@FreeBSD.org wrote: > At Wed, 7 Mar 2007 17:21:43 -0000 (UTC), > tmclaugh@sdf.lonestar.org wrote: > > > > > > 1) update the PCS port to grab my version > >=20 > > I think this is the ideal way to handle the situation. Only caveat > > on your end is your modified pypcap shouldn't interfere with the > > port of Doug's pypcap. It should install with a slightly different > > module name so we don't need to set port conflicts and so ports > > relying on net/pypcap don't see your fork installed and assume > > net/py-pypcap is installed which may lead to potential breakage. >=20 > OK, can you propose a name and set it all up? The number of these > libraries that exist is problematic. There are too many ports with similar names, I propose ``py-pycap'', it's nothing but a new name to make difference with others. Thus we need to add a new port, py-pycap, I made a shar: http://freebsd.csie.nctu.edu.tw/~lwhsu/tmp/py-pycap.shar I have changed some files in py-pypcap-1.1.2.tar.gz, like PKG-INFO, README and setup.py, for installing with different module, %%PYTHON_SITELIBDIR%%/pycap.so. And repack it as py-pycap-1.0.tar.gz. We also need to change the RUN_DEPENDS in net/pcs, in earlier discussion, we think rename it to net/py-pcs is better, so we might need a repocopy. This shar contains the new net/py-pcs, and updates the pcs to 0.4: http://freebsd.csie.nctu.edu.tw/~lwhsu/tmp/py-pcs.shar Due to the renaming of pcs, we also need to change RUN_DEPENDS in net/pdb, This patch updates pdb: http://freebsd.csie.nctu.edu.tw/~lwhsu/tmp/pdb.diff Please check these shars and patches, thanks. --=20 Best Regards, Li-Wen Hsu --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFF+68bQWsOOSiXsigRAlNfAKCTIVd6L7kTa5tJOcsVt701itiK1wCfW3fY 80+ierPGssPVSvE8vxGkBYI= =txJo -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7--