On Sat, Nov 07, 2009 at 05:19:04PM -0500, stan wrote: > On Sat, Nov 07, 2009 at 10:16:24PM +0100, Maxime DERCHE wrote: > > Hello, > > > > On Sat, 7 Nov 2009 11:06:07 -0500 > > stan <st...@panix.com> wrote: > > > > > I am building my first OpenBDS machine in a good while. I used the > > > auto partioner (a nice enhancement), but, I ran out of space in /usr. > > > Tracking it down, I find a new directory (new to me > > > anyway) /usr/ports/obj. > > > > > > What is the purpose of this directory? Why does a ?make clean" in a > > > port directory (/usr/ports/print/cups for instance) not delete the > > > appropriate files in this directory? When is it safe to clean up this > > > directory? > > > > man 7 hier > > > > /usr/obj is the "architecture specific target tree produced by > > build-ing the /usr/src tree." > > > >
Actually the correct manpage is bsd.port.mk(5), WRKOBJDIR. The location changed again with -current. > > OK, got that. > > Now, the rest of the question. When/how is it suosed to be cleaned up? I > would have thought that a "make clean" in a given port directory would have > done that, but that does not appear to be the case. > > Followup question, if it is not autmatically cleaned up, when is it safe to > do so manualyy? Clean will remove all files only of the version matches exactly. You can delete it whenever you're not building ports. Isn't that obvious? > > > -- > A: Because it messes up the order in which people normally read text. > Q: Why is top-posting such a bad thing? > A: Top-posting. > Q: What is the most annoying thing in e-mail?
