[HEADSUP] portmaster/portupgrade support for new features

[Maxim Sobolev]

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 <bapt at freebsd.org>
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 <bapt at FreeBSD.org> 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
>