From owner-freebsd-ports@FreeBSD.ORG Thu Mar 8 08:02:10 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 EADB316A403 for ; Thu, 8 Mar 2007 08:02:10 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from mrout1.yahoo.com (mrout1.yahoo.com [216.145.54.171]) by mx1.freebsd.org (Postfix) with ESMTP id D5C7113C46B for ; Thu, 8 Mar 2007 08:02:10 +0000 (UTC) (envelope-from gnn@neville-neil.com) Received: from minion.local.neville-neil.com (proxy8.corp.yahoo.com [216.145.48.13]) by mrout1.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id l2881EP1025548; Thu, 8 Mar 2007 00:01:14 -0800 (PST) Date: Thu, 08 Mar 2007 17:01:11 +0900 Message-ID: From: gnn@FreeBSD.org To: tmclaugh@sdf.lonestar.org In-Reply-To: <42419.192.216.27.32.1173288103.squirrel@webmail.freeshell.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> User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.7 Emacs/22.0.93 (i386-apple-darwin8.8.2) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Cc: ports@FreeBSD.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: Thu, 08 Mar 2007 08:02:11 -0000 At Wed, 7 Mar 2007 17:21:43 -0000 (UTC), tmclaugh@sdf.lonestar.org wrote: > > Ah, but here is the problem. I have updated the package for use with > > PCS, and Doug Song has not as yet added those bits. This is kinda a > > fork, but I am feeding him the changes etc. Can we either: > > > > 1) update the PCS port to grab my version > > 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. > OK, can you propose a name and set it all up? The number of these libraries that exist is problematic. > > 2) change the py-pypcap port to point to my version? > > Additionally, if these changes have been accepted by Doug and you're > just waiting for him to do a new release you could just add your > patches to the port's patch files. It sounds like you'll be > continuing work on your pypcap fork so I don't think this option is > as preferable as the first. > They got too big and I didn't get an answer from him in a couple of months so I'd prefer not to wait. Best, George