On Fri, Nov 04, 2011 at 07:57:51AM -0500, Bryan wrote: > On Fri, Nov 4, 2011 at 02:10, Marc Espie <es...@nerim.net> wrote: > > On Thu, Nov 03, 2011 at 10:11:50PM -0500, Bryan wrote: > >> Ah... you have to have a 'clean' machine everytime? I knew there was > >> a catch... > > > > The updates switches are there as a convenience. Sometimes they don't work, > > as some ports don't build if an older version is already there. > > > > "clean" builds should work every time. Non-clean builds, well, depends... > > > > Understood... I did find that running 'make REFETCH=true fetch' on > the entire /usr/ports reduced the amount of output on the screen. > sometimes, the "L" section of the output would be so large that it > would fill up and entire 1920x1080 screen, dropping the "E" section > off the screen for about 3,000 ports... > > I will give dpb a rest for a while... I don't have the assets around > to do that. I do have a quad core server with HT, but it's running > mission critical apps that can't be wiped every time to run dpb. > maybe santa will bring me a server for xmas.
chroot's your friend, that's how I do this ;) > I did read dpb(1), which is how I knew about the switches... for the > packages that errored, I was looking for something like the output > from when you run them individually... so I could post the issues to > the list here... -- viq
pgp5dDkPjrQEs.pgp
Description: PGP signature
