From owner-freebsd-ports@FreeBSD.ORG Sat Aug 2 14:36:31 2014 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8D58CAA0 for ; Sat, 2 Aug 2014 14:36:31 +0000 (UTC) Received: from bein.link (vps-6159-8629.cloud.tilaa.com [37.252.124.82]) by mx1.freebsd.org (Postfix) with ESMTP id 5349C2645 for ; Sat, 2 Aug 2014 14:36:31 +0000 (UTC) Received: from quad.localnet (unknown [172.16.32.6]) by bein.link (Postfix) with ESMTPSA id 3BDC4404D9 for ; Sat, 2 Aug 2014 16:36:14 +0200 (CEST) From: Maxim V FIlimonov To: freebsd-ports@freebsd.org Subject: Re: devel/stlink Date: Sat, 02 Aug 2014 18:36:27 +0400 Message-ID: <2382005.ICHve2rjt0@quad> User-Agent: KMail/4.12.5 (FreeBSD/10.0-RELEASE; KDE/4.12.5; amd64; ; ) In-Reply-To: <20140802141819.GH2644@home.opsec.eu> References: <4443341.EiikNYngQK@quad> <1637580.MU5nyUnjPH@quad> <20140802141819.GH2644@home.opsec.eu> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Aug 2014 14:36:31 -0000 On Saturday 02 August 2014 16:18:19 Kurt Jaeger wrote: > > > Can you tell me where I get urllib2 for python on an 10.0-amd64 ? > > > > > > f10$ ./latest.sh > > > > > > Traceback (most recent call last): > > > File "getlatest.py", line 1, in > > > > > > import urllib2 > > > > > > ImportError: No module named 'urllib2' > > > > Ah, I see, in my case it was installed with python27: > > $ pkg which /usr/local/lib/python2.7/urllib2.py > > /usr/local/lib/python2.7/urllib2.py was installed by package > > python27-2.7.8 > > Thanks. Now, frankly, I have no easy idea on how to integrate this > "get the latest from github" into a proper port. > Well, I tried to integrate my scripts into the existing Makefile, but I ended up with a cyclic fetch. I also tried to make this a dependency for pre-config, but it's not a good way to do that because config is not run every time you rebuild a port. Might there be any other targets to apply those actions to? > Probably some /usr/ports/Mk/ magic needs to be created for this > to work in general. > > Would it be sufficient if we just commit the current "state", > explain the process in the pkg-message and provide your scripts > latest.sh and getlatest.py with a stlink-related name ? > That's also a solution. I could update that port manually. > I know this is not purrrrfect 8-} Well, it isn't, but at least it works. -- wbr, Maxim Filimonov che@bein.link