From owner-freebsd-ports@freebsd.org Thu Jun 23 21:54:21 2016 Return-Path: Delivered-To: freebsd-ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2A7EEB74709 for ; Thu, 23 Jun 2016 21:54:21 +0000 (UTC) (envelope-from elferdo@gmail.com) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id 0982028D6 for ; Thu, 23 Jun 2016 21:54:21 +0000 (UTC) (envelope-from elferdo@gmail.com) Received: by mailman.ysv.freebsd.org (Postfix) id 08CDFB74708; Thu, 23 Jun 2016 21:54:21 +0000 (UTC) Delivered-To: ports@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 061D1B74707 for ; Thu, 23 Jun 2016 21:54:21 +0000 (UTC) (envelope-from elferdo@gmail.com) Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (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 BF99F28D2 for ; Thu, 23 Jun 2016 21:54:20 +0000 (UTC) (envelope-from elferdo@gmail.com) Received: by mail-it0-x233.google.com with SMTP id g127so1002270ith.0 for ; Thu, 23 Jun 2016 14:54:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=mroZttTDVndg97iLIF6u7f0mthNaqXl/AiAbfVGQKDc=; b=aS+lfY3hK5My9jnH5+IQ6AnnIOxADHQx6taJxtHcLro0t4aQhRSQwCRKmsNq13xznK x2RjNVdjhR07J6NwhZjKl8iEXijXvYbmBnC5UrpbXx5UHFEfMlGbSQNtP5RzsUJCytDy szwlyFnqNjXzsi7CZgqKIstAfJKtWbj8aIMcZycG5TkDboT2u3ObqI8JOHl3ymrGd4ws m2SrQk0Hv+fFYSbIPZ2dBUQLcDYj3V7b0okbS49TEbW1qwez3NA4fFnLTevRwfelPKWA sbvt3mZKn77iwvQU0iYO8wkN+dnZjtU4pS91j0alqXybzYhi784X9mynDMezjmzSvRF4 R3hA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=mroZttTDVndg97iLIF6u7f0mthNaqXl/AiAbfVGQKDc=; b=mztSYAXCcz28H6NSRHYkBelKtQvzHujua62RCHjdILRh4p0OLRVts4YnRbjGq65I/7 bHG2E9wmkWjMu3+A38LIQP6bWUcuSe4qzIH88JzyUq7L5icveurFhJ3cEiIw3hNebiOl aFAxTUbjpEAVADquNX6W4irztcMW5QjxQHYVF/XOVkisTAXYQ+k1rGgtgf4C2xwwJwAN Fz9YNBsgHD+c2Lp5UzPU0/LHaoYSo5eg9Xl4Az+IaB0UsxBwmjtLtivKL14354n+udha 4DfNypsBmMWxbLbtJv6XVtwYEzYnUMO0GgNOqK69qeoR8MTbxBi83ljcWJX8dUnpDFhf 5CBA== X-Gm-Message-State: ALyK8tLwx8ilWBz0dA5naE1rRaWR5EtU8ZZ2QwV/46LHvio789n8Sxg6DGg9rsnoQQjzU28EF3RKV0QOQ5vPCw== MIME-Version: 1.0 X-Received: by 10.36.137.131 with SMTP id s125mr22617849itd.93.1466718860243; Thu, 23 Jun 2016 14:54:20 -0700 (PDT) Received: by 10.36.95.17 with HTTP; Thu, 23 Jun 2016 14:54:19 -0700 (PDT) Received: by 10.36.95.17 with HTTP; Thu, 23 Jun 2016 14:54:19 -0700 (PDT) In-Reply-To: <4e06c0b2-e70e-68e8-732b-97774cff8b2d@rawbw.com> References: <4e06c0b2-e70e-68e8-732b-97774cff8b2d@rawbw.com> Date: Thu, 23 Jun 2016 23:54:19 +0200 Message-ID: Subject: Re: Any way to add USES clause depending on two options without including bsd.port.options.mk? From: =?UTF-8?Q?Fernando_Herrero_Carr=C3=B3n?= To: Yuri Cc: ports@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.22 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Jun 2016 21:54:21 -0000 El 23 jun. 2016 11:26 p. m., "Yuri" escribi=C3=B3: > > I have two port options: GUI NLS. > > I would like to have USES=3Dgettext only when both GUI and NLS are "on". > > If it was only one option, say NLS, NLS_USES=3Dgettext would work. > > But what about the two options case? Is there any magic to do this without .include ? > > > Yuri > Hi Yuri, Could you please elaborate on the reasons why you want to do that? I don't see how that particular combination of options would introduce a dependence that neither of them alone would. And then, why not include port.options.mk? Then you could explicitly check for both options being set. Cheers, Fernando