Yes. You can use these packages on different systems. IFF they are the same release, and same architecture. amd64 packages won't work on i386, etc. The packages also refuse to install, if you have the wrong versions of libraries installed. 4.4 packages won't work on 4.5, of course.
On 2009 Apr 30 (Thu) at 10:35:41 +0200 (+0200), Pau wrote: :I start to enjoy the ports system... : :What about those packages? Could I use them for another machine :runnning the same obsd release? If i have another laptop in hwich I :want to install openoffice3, could i simply copy over openoffice*.tgz :and install it with pkg_add? :I guess so, but I prefer to ask, just in case of. :And can I remove everything in distfiles? Since the packages built and :were installed, it seems to be the most natural thing. : :But I should do a bit reading before asking so much... : :in any case, thanks a lot : :Pau : :2009/4/30 Stuart Henderson <[email protected]>: :> 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. :> :> : : : :-- :Let there be peace on earth. And let it begin with misc :_______________________________________________ :Openbsd-newbies mailing list :[email protected] :http://mailman.theapt.org/listinfo/openbsd-newbies : -- If you have a procedure with 10 parameters, you probably missed some. _______________________________________________ Openbsd-newbies mailing list [email protected] http://mailman.theapt.org/listinfo/openbsd-newbies
