On Fri, Mar 15, 2013 at 12:28:22PM +0100, Martijn van Duren wrote: > On Fri, 2013-03-15 at 10:27 +0000, Stuart Henderson wrote: > > On 2013-03-15, Martijn van Duren <[email protected]> wrote: > > > Hello misc, > > > > > > I'm currently trying to update my system, after a cvs -q up -P. In some > > > folders, when I type make update, the process exits immediately with an > > > error code 0. > > > Even adding a FORCE_UPDATE=Yes to it doesn't do anything. > > > > "make update" only works in the most simple cases; where subpackages or > > flavours have changed it can easily become confused. As with all things > > in the ports tree (as opposed to packages) it is more of a developer > > convenience rather than something which is expected to work at all times. > > > > Best bet is to clean the package directory of any old junk before > > you start building new packages, then "make package" and > > "PKG_PATH=/usr/ports/packages/`arch -s`/all sudo pkg_add -u". > > I also get the same problem when doing doing a make package. Even with a > make clean and make distclean beforehand. > # make distclean > ===> Cleaning for help2man-1.41.1 > ===> Dist cleaning for help2man-1.41.1 > # make package > # echo $? > 0
Dude, obviously you already have the older package around. Neither make clean nor make distclean will clean it. Also, RTFM, bsd.port.mk(5) has an extensive documentation about clean. And dpb -R is more likely to work, for a reasonable value of work.
