On 2009/04/30 09:55, Pau wrote: > I started compiling the day before yesterday at 21h30, left the laptop > on during the night, took it with me to work, as usual, but this time > compiling, spent the whole day at the institute. There the compilation > crashed, because /usr was full! I have a 20G /usr partition. True, I > had also compiled other things, but I had plenty of space before > starting to compile, at least I thought so. So I did a make clean in > /usr/ports and resumed the compilation (make install again).
That sounds about right for this software (-: You can make it easier to clean up after port builds - set WRKOBJDIR in /etc/mk.conf and instead of creating directories under each port it will create them in the directory you specify. e.g. WRKOBJDIR=/usr/obj/ports Then you can easily rm -r when you need the space back. This is also useful if /usr is full but you have more space elsewhere you can build in. You can also set this on a port-by-port basis, bsd.port.mk(5) tells you more under the WRKOBJDIR description. > hux(pd)| du -hs /usr/ports/* | grep G > 1.9G /usr/ports/distfiles > 4.9G /usr/ports/packages > > Now i understand... but what is the difference between distfiles and packages > ? > > I see tgz in the two of them. Why two separate folders? distfiles are downloaded source code used to build the port; packages are the binary packages built by the port. There are multiple directories inside the packages directory; the files for most ports will appear in each of them (all, ftp, cdrom), but they don't take any extra place as they are hard-links (extra directory entries pointing to the same inode on the filesystem) - see ln(1) and ls -li. _______________________________________________ Openbsd-newbies mailing list [email protected] http://mailman.theapt.org/listinfo/openbsd-newbies
