FreeBSD ports: 1 unfetchable distfile: net/py-pypcap
gnn at FreeBSD.org
gnn at FreeBSD.org
Thu Mar 8 08:02:11 UTC 2007
At Wed, 7 Mar 2007 17:21:43 -0000 (UTC),
tmclaugh at 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
More information about the freebsd-ports
mailing list