On Fri, May 06, 2011 at 05:08:57PM +0000, Stuart Henderson wrote: > Looking at the webpage the most prominent example of using it is for python; > it feels like you've only done half the job if you skip this part..
That's true. Python module is missing here as I don't need it. I can try and fix python part in my port, but I know that will take me some time. Also I won't be using python code at all. I will have a look into porting python module as well and I'll send updated port. Eventually. > On 2011-05-06, Mikolaj Kucharski <miko...@kucharski.name> wrote: > > Kind reminder. > > > > http://marc.info/?l=openbsd-ports&m=130355640115032&w=1 > > > > On Sat, Apr 23, 2011 at 11:57:24AM +0100, Mikolaj Kucharski wrote: > >> Hi, > >> > >> I've skipped python part, as I don't need it. Builds fine, regress passes. > >> > >> Last time rpointel@ asked me to "don't recreate do-build, do-install if > >> there is a correct Makefile". But to use the Makefile I would need patch > >> it heavly that it wouldn't be upstream Makefile any more. I don't think > >> in this particular port it gives any benefit to write the port in the > >> usual way. > >> > >> Anyway, here is the port.. > >> > >> > >> Comment: > >> library to parse proxy auto-config (PAC) files > >> > >> Description: > >> pacparser makes it easy to add proxy auto-config file parsing capability > >> to any program. It comes as a shared C library which can be used to make > >> any C program PAC scripts intelligent. This package comes also with > >> small binary called pactester(1) which may help one test a PAC file > >> against given url. > >> > >> WWW: https://code.google.com/p/pacparser/ > > -- best regards q#
