On Tue, 2006-06-27 at 17:38 -0500, Mark Linimon wrote: > On Wed, Jun 28, 2006 at 02:11:01AM +0400, Sergey Matveychuk wrote: > > Can I see a log for this breakage? > > Unfortunately I went ahead and cleared the i386-6-exp logfiles out about > an hour ago to get ready for the next build. On top of that, I had already > rerun kdelibs3* on both i386-6 and i386-5-exp, with the change backed out, > to a) make sure that they built, and b) to make the packages available > (they have since been uploaded to the mirrors). (fwiw: the packages did > indeed build after the change.) > > Perhaps pav or marcus still has a copy, I didn't keep one. They were the > ones that first noticed the breakage and asked for the backout.
The breakage potential is easy to see. All elements in DEPENDS are always installed by a given port. So, because kdelibs3 has a DEPENDS on kdehier, make will descend into misc/kdehier, and call make install EVERY TIME make install is called in kdelibs3. If you already have kdehier installed (which is the case during a package build), then the ports system will bail out complaining that kdehier is already installed when it does: (cd misc/kdehier; make install) The way this USED to work is that FORCE_PKG_REGISTER was added to .MAKEFLAGS and DEPENDS_ARGS, and thus the above was called as: (cd misc/kdehier; make install FORCE_PKG_REGISTER=yes) This, of course, would not cause the error. As I said to Mark in a follow-up email, it may very well be time to retire DEPENDS, but the patch that was committed did not successfully do that and maintain the buildability of the tree. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc
signature.asc
Description: This is a digitally signed message part
