From owner-freebsd-ports-bugs@FreeBSD.ORG Wed Feb 18 17:15:38 2015 Return-Path: Delivered-To: freebsd-ports-bugs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CE1E5D6D for ; Wed, 18 Feb 2015 17:15:38 +0000 (UTC) Received: from mail-ob0-x22f.google.com (mail-ob0-x22f.google.com [IPv6:2607:f8b0:4003:c01::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9228A8CF for ; Wed, 18 Feb 2015 17:15:38 +0000 (UTC) Received: by mail-ob0-f175.google.com with SMTP id va2so4483637obc.6 for ; Wed, 18 Feb 2015 09:15:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=khera.org; s=google11; h=mime-version:date:message-id:subject:from:to:content-type; bh=EN5md8YO7TQKsVftYvbMIbEFF1WaCLPpdhvMSB6bZCQ=; b=GgimVVsurbN21pYSg1MrDQ822jXddfTl+q+pWFPb1FxSR0P+hA3B3Y6XNcPN3mWjAe G/sbeppJLm1AkHmAC6diWWaZR8Eqsn1y3K4RTcz9zVjys9VSRGqzTB1Db4UbQUo4jQVX lmJKDQOjXUFBHrEtrohVf8HwshQsvNyfIntBc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=EN5md8YO7TQKsVftYvbMIbEFF1WaCLPpdhvMSB6bZCQ=; b=ShPnUfqVxlUAjRRvZxHUB9s4P2lGg/viJBfPZV6SPJqFv/LYh+aK0hVkFnGcu4jlJk WSovJc9DmcvZghIk29aphxJY0bgzqGRsJk2h3/ug7MJNkxj+gKuyXBl1oB7tpnm6MPhS i4Cil7NhYbAVp++NifZwQgfHrjLTa10+Il1jnKZdplQx8b6CsayrR5HfGSyeei3I6PVI i6ZKQ4vdVTdVf3azDnrjrZYHGfF5ftA+Aw5v0DXfCrRNO5bwK6m1E3Ymd8c0t+CtL7Zd s8QXW6lEdhHnYa+ZLrvyEF9yRe1CqMHt9DBbUGUJ1MhJyrI5GnBPS6KpCopgwhl3sdyZ 439g== X-Gm-Message-State: ALoCoQngNU9mmMePpM4O4IFtpHYS7+BjLbDr/k24MH72F85NSZkZjyl+zkglcQV0JbJCqVuGQXAH MIME-Version: 1.0 X-Received: by 10.60.144.73 with SMTP id sk9mr171393oeb.71.1424279737563; Wed, 18 Feb 2015 09:15:37 -0800 (PST) Received: by 10.76.28.103 with HTTP; Wed, 18 Feb 2015 09:15:37 -0800 (PST) Date: Wed, 18 Feb 2015 12:15:37 -0500 Message-ID: Subject: change in how dependencies are recorded From: Vick Khera To: freebsd-ports-bugs@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Feb 2015 17:15:38 -0000 I have some local ports I use to quickly configure new servers. They are basically lists of dependencies that pull in what the specific server function requires, such as mail server or web server. Recently, my local package builder (using poudriere) started rebuilding a couple of ports every run claiming "new dependency" was found. I traced it down to the following RUN_DEPENDS: emacs>=23.3:${PORTSDIR}/editors/emacs-nox11 \ This was confusing the dependency registration of the port; that is, "make depends" would notice it needed emacs, then install it. However, when "make install" would run, the resulting package did not register the dependency for emacs. The fix was to remove the ">=23.3" version check. My suspicion is that it has something to do with emacs-nox11 being a slave port. Similarly, this RUN_DEPENDS caused markdown-mode.el to be unregistered the same way (it installed the dependency, but did not register it): textproc/markdown-mode.el:${PORTSDIR}/textproc/markdown-mode.el \ The fix for this situation is to add ">0" as a version dependency. I do not know why this started to fail recently. Also, the following LIB_DEPENDS results in the same situation: the dependency gets installed but not registered: LIB_DEPENDS= tcnative-1:${PORTSDIR}/www/tomcat-native Looking at other ports, it seems that I now need to change the library to LIB_DEPENDS= libtcnative-1.so:${PORTSDIR}/www/tomcat-native which resolves the registration of the dependency. Again, I do not know when this format was changed, but it is relatively recently. It did work when I first used this in October 2013 and I'm fairly certain it was working at least in November 2014.