On Thu, Aug 28, 2008 at 04:21:34PM -0400, Brad wrote: > On Thu, 28 Aug 2008 13:31:32 -0600 > macintoshzoom <[EMAIL PROTECTED]> wrote: > > > On my 4.4 i386 make update on ports kde fetches the distfiles/sources > > and build the packages even when not installed at all nor requested. > > > > As some one of you know, the full sources of kde on a slow connection > > can be desperately loooong. > > > > I asked: > > # env FORCE_UPDATE=yes env FORCE_ALWAYSUPDATE=yes \ > > env FORCE_UPDATEDEPENDS=yes make update > > > > perhaps this is my error? > > It is a combination of three issues.. the way make update works, the way the > ports tree works and your expectation. > > First off, make update really does not work the way most users would probably > think it should work under the most ideal conditions. It is more or less meant > to be run in each directory to update individual ports with the resulting > packages as opposed to trying to run it globally whether it is under > /usr/ports > or even /usr/ports/x11/kde for that matter. It isn't "smart enough" to figure > out what packages are installed and only build the resulting package. It will > just build the packages and then attempt to update the package if it exists on > the system.
Actually, make update is very useful for me... It's mostly a target used to do a complete bulk build on a machine without uninstalling the previous set of packages first. As we've said for years now, users should use binary packages most of the time. The ports tree is heavily slanted towards actual developers and bulk builders. > Last of all, your expectation. You have an expectation that make update works > in a certain manner and as outlined above this is not the way that the tools > actully work at the moment. So get used to it. ;) This is totally unlikely to change... the update he wants is probably pkg_add -ui with SRC path...
