Date: Fri, 17 Apr 2009 09:31:46 +0200 From: Johannes Dieterich <dieterich.joh@googlemail.com> To: Mel Flynn <mel.flynn+fbsd.current@mailing.thruhere.net> Cc: freebsd-current@freebsd.org Subject: Re: Proper procedure to update hal on -current Message-ID: <542798610904170031w44e51957gd342eadf747a4e97@mail.gmail.com> In-Reply-To: <200904170836.36239.mel.flynn%2Bfbsd.current@mailing.thruhere.net> References: <200904170836.36239.mel.flynn%2Bfbsd.current@mailing.thruhere.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Mel, On Fri, Apr 17, 2009 at 8:36 AM, Mel Flynn < mel.flynn+fbsd.current@mailing.thruhere.net<mel.flynn%2Bfbsd.current@mailing.thruhere.net> > wrote: > Hi, > > Given: > http://lists.freebsd.org/pipermail/freebsd-current/2009-March/004871.html > > and the fact that I've got devel/libusb deps forced on me (x11/kdebase4- > workspace for example), what would be the proper procedure to upgrade HAL. > Right now I'm using a +IGNOREME with portmaster, but I'm sure this will > break > stuff in the not so far future. > > Do I need to temporarily uninstall devel/libusb (it doesn't build now > anyway, > but maybe upgrading to today's current will fix that) then reinstall it? My procedure was to deinstall devel/libusb, then I also encountered the same kind of mising dependencies as you do but for me a pkgdb -F afterwards would fix them. Then hal would also build for me. :-) See the procedure in ports/UPDATING, entry 20090309. Hope this helps, Johannes > > > Any chance some BROKEN vars can be set based on FreeBSD_Version? > -- > Mel >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?542798610904170031w44e51957gd342eadf747a4e97>