From owner-freebsd-ports@freebsd.org Mon Aug 24 19:06:47 2015 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 497579C17C2 for ; Mon, 24 Aug 2015 19:06:47 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 261C69FA for ; Mon, 24 Aug 2015 19:06:47 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by mailman.ysv.freebsd.org (Postfix) id 236F39C17C1; Mon, 24 Aug 2015 19:06:47 +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 220839C17C0 for ; Mon, 24 Aug 2015 19:06:47 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: from mail-ig0-f169.google.com (mail-ig0-f169.google.com [209.85.213.169]) (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 E2A1E9F9 for ; Mon, 24 Aug 2015 19:06:46 +0000 (UTC) (envelope-from sobomax@sippysoft.com) Received: by igfj19 with SMTP id j19so68860789igf.0 for ; Mon, 24 Aug 2015 12:06:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=H7ogW5vhXyvduIrl4RtLKYKrHVtTh/Qb1uSCb6V4owI=; b=XZlUzeCQP2VR5ffQ4FgrwfYuJo6JdBcuPQYjeQlGzUCUy8a9McFvDTYp2FsKg/4YYa DYfmSfSN6iCFBXKaWuFooj9tKtXRAhe1pzOL03tuD/9AcCd78x8tTRiQBhcMrhlHkM1U Ha2NTtfMT79vWpeoHefRSqeO8usq224iabp7gY72bmT7Kh7el5Ol28b4wCJ4xjYgQeG7 30LRfneEHTGYiVCDw7Vf8hPI0CS0nKpsf/KVn5PYWI2EyRP7EL+D5yzSK4dH6kgRUPsu Ye1VrpC+LlHw5Lj9VFNjm2u0RJgT7KgMLLS2cjUfu624b5Uk/yecD7y5oJL8KOR7GKTm AsXg== X-Gm-Message-State: ALoCoQn4nACgC6rnENOaxHWV3dFhBAxGgtjtt7J+lNJwIS9H8o7h6ZsDhxBfJ66HC1tCba6y6M2n MIME-Version: 1.0 X-Received: by 10.50.137.100 with SMTP id qh4mr15168076igb.1.1440442717435; Mon, 24 Aug 2015 11:58:37 -0700 (PDT) Sender: sobomax@sippysoft.com Received: by 10.79.103.134 with HTTP; Mon, 24 Aug 2015 11:58:37 -0700 (PDT) In-Reply-To: <20150824185412.GJ93486@ivaldir.etoilebsd.net> References: <20150629092226.GL68142@ivaldir.etoilebsd.net> <20150824135802.GF93486@ivaldir.etoilebsd.net> <20150824192710.08c77060@freedom> <20150824185412.GJ93486@ivaldir.etoilebsd.net> Date: Mon, 24 Aug 2015 11:58:37 -0700 X-Google-Sender-Auth: NjAowA7qIOMQoBIJsgDG9rzVmaY Message-ID: Subject: Re: [HEADSUP] portmaster/portupgrade support for new features From: Maxim Sobolev To: Baptiste Daroussin Cc: Matthieu Volat , ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Aug 2015 19:06:47 -0000 Are you going to keep support for the "old" way too? This is kinda crucial for us (and possible other people) in order to properly build off-the-tree (private) ports. Thanks! -Maxim On Mon, Aug 24, 2015 at 11:54 AM, Baptiste Daroussin wrote: > On Mon, Aug 24, 2015 at 07:27:10PM +0200, Matthieu Volat wrote: > > On Mon, 24 Aug 2015 15:58:02 +0200 > > Baptiste Daroussin wrote: > > > > > On Mon, Jun 29, 2015 at 11:22:27AM +0200, Baptiste Daroussin wrote: > > > > hi all, > > > > > > > > A couple of new features are coming to the ports tree. The first of > which has > > > > landed in the ports tree and should not be used before a while, > still before we > > > > start using it, it would be a very good idea to bring support for it > to > > > > portmaster/portupgrade. (I have already done the change in poudriere > and it will > > > > be in te next version.) > > > > > > > > So since recently we can remove the ${PORTSDIR} from all the > dependency lines. > > > > (Please do not use that syntax before all the tools are able to > handle it!) > > > > > > > > Aka BLA_DEPENDS= pattern:${PORTSDIR}/category/port can now become > > > > pattern:category/ports > > > > > > > > I haven't checked portmaster/portupgrade code so I have no idea if > they will > > > > support that out of box or if they will need some changes. > > > > > > > > I would really appreciate to see people testing that and provide > patches if > > > > necessary so that the day we adopt this syntax those tools are > already ready to > > > > use it ootb. > > > > > > > > FYI: https://github.com/freebsd/portmaster and > > > > https://github.com/freebsd/portupgrade > > > > > > > > Later more changes will be necessary to support upcoming VARIANTS > (formerly > > > > known as FLAVOURS) and sub packages. > > > > > > > > This first step would allow you to step into the code of those tools > before the > > > > having to deal with more intrusive changes :) > > > > > > > > Best regards, > > > > Bapt > > > > > > Here is a reminder on help needed. We do really need to get this > feature in the > > > ports tree to be able to step further in flexible dependencies (hear > > > provides/requires) and VARIANTS/FLAVORS and subpackages. > > > > > > If one cares about those tools, please make them work without > ${PORTSDIR} > > > information. > > > > > > Best regards, > > > Bapt > > > > Hello, > > > > Are those features already present somehow in ports? > > > > The first thing I see is a failure because calling commands > > such as "make build-depends-list" in port directories in which I > > removed ${PORTSDIR} from LIB_DEPENDS failing. > > > No not yet because we are writing for portmaster/portupgrade to handle > that to > commit them. How ever I can provide a patch so anyone willing to work on > that > will be able to test. > > Best regards, > Bapt >