libnet* questions

[Lowell Gilbert]

"Pratt, Benjamin E." <bepratt at stcloudstate.edu> writes:

> > -----Original Message-----
> > From: lowell at be-well.ilk.org [mailto:lowell at be-well.ilk.org] 
> > On Behalf Of Lowell Gilbert
> > Sent: Wednesday, November 23, 2005 08:30
> > To: Pratt, Benjamin E.
> > Cc: freebsd-questions at freebsd.org
> > Subject: Re: libnet* questions
> > 
> > "Pratt, Benjamin E." <bepratt at stcloudstate.edu> writes:
> > 
> > > Hello, I'm writing to find out what others do, and what I can do, to
> > > work with ports that require the now three different 
> > libnet* ports. What
> > > I've been doing, and it seems like there should be an easier way, is
> > > installing one libnet*, for instance net/libnet then running
> > > portupgrade. I then deinstall net/libnet, install 
> > net/libnet-devel and
> > > run portupgrade. Now there's net/libnet10 that I've got to 
> > deal with as
> > > well.
> > > 
> > > What is the best way people have found to get around 
> > package conflicts
> > > with these ports?
> > 
> > I haven't noticed any conflicts with these ports.  libnet and
> > libnet10 don't conflict at all -- they can be installed on the
> > same machine -- and libnet-devel isn't required by anything else
> > as far as I can see.
> 
> I am still getting conflicts. Example:
> 
> root at chiefwiggum# pwd
> /usr/ports/net/libnet
> root at chiefwiggum# make install clean
> ===>  Installing for libnet-1.1.2.1,1
> 
> ===>  libnet-1.1.2.1,1 conflicts with installed package(s):
>       libnet10-1.0.2a_1,1
> 
>       They install files into the same place.
>       Please remove them first with pkg_delete(1).
> *** Error code 1
> 
> Stop in /usr/ports/net/libnet.
> root at chiefwiggum#

It should work in both directions, and doesn't seem to.  I'll try to
remember to put in a PR later today.

> As far as needing libnet-devel goes, there was something that required
> it just this past week when I CVSuped and ran portupgrade. I can't
> remember what port it was, and couldn't find it immediately but will
> keep looking.

A portstree search didn't turn up anything.  But in any case, it
should only be a build dependency and not a run dependency, so you can
delete any of them at any time if needed.