Date: Wed, 23 Nov 2005 10:20:58 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> Cc: "Pratt, Benjamin E." <bepratt@stcloudstate.edu>, freebsd-questions@freebsd.org Subject: Re: libnet* questions Message-ID: <20051123162057.GF6893@dan.emsphone.com> In-Reply-To: <444q6377yu.fsf@be-well.ilk.org> References: <0451409FD6EF4F49AE13E3D1DD45280027E2B0@EXCHANGE.campus.stcloudstate.edu> <444q6377yu.fsf@be-well.ilk.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Nov 23), Lowell Gilbert said: > "Pratt, Benjamin E." <bepratt@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. On my system, both libnet and libnet10 both install a /usr/local/libnet/libnet.a and /usr/local/include/libnet/*.h files, which is just about as conflicting as you can get :) -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051123162057.GF6893>