Date: Mon, 24 Aug 2015 19:27:10 +0200 From: Matthieu Volat <mazhe@alkumuna.eu> To: Baptiste Daroussin <bapt@FreeBSD.org> Cc: ports@FreeBSD.org Subject: Re: [HEADSUP] portmaster/portupgrade support for new features Message-ID: <20150824192710.08c77060@freedom> In-Reply-To: <20150824135802.GF93486@ivaldir.etoilebsd.net> References: <20150629092226.GL68142@ivaldir.etoilebsd.net> <20150824135802.GF93486@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/sf+qaQLzc4sBIxJSAwiJRqx
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable
On Mon, 24 Aug 2015 15:58:02 +0200
Baptiste Daroussin <bapt@FreeBSD.org> wrote:
> On Mon, Jun 29, 2015 at 11:22:27AM +0200, Baptiste Daroussin wrote:
> > hi all,
> >=20
> > A couple of new features are coming to the ports tree. The first of whi=
ch has
> > landed in the ports tree and should not be used before a while, still b=
efore 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 an=
d it will
> > be in te next version.)
> >=20
> > 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!)
> >=20
> > Aka BLA_DEPENDS=3D pattern:${PORTSDIR}/category/port can now become
> > pattern:category/ports
> >=20
> > 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.
> >=20
> > I would really appreciate to see people testing that and provide patche=
s if
> > necessary so that the day we adopt this syntax those tools are already =
ready to
> > use it ootb.
> >=20
> > FYI: https://github.com/freebsd/portmaster and
> > https://github.com/freebsd/portupgrade
> >=20
> > Later more changes will be necessary to support upcoming VARIANTS (form=
erly
> > known as FLAVOURS) and sub packages.
> >=20
> > This first step would allow you to step into the code of those tools be=
fore the
> > having to deal with more intrusive changes :)
> >=20
> > Best regards,
> > Bapt
>=20
> 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.
>=20
> If one cares about those tools, please make them work without ${PORTSDIR}
> information.
>=20
> 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.
Regards,
--
Matthieu Volat <mazhe@alkumuna.eu>
--Sig_/sf+qaQLzc4sBIxJSAwiJRqx
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iEYEARECAAYFAlXbU+4ACgkQ+ENDeYKZi35ZbQCguz5qUwiGB0eDDECI+zQRMeUF
rzgAnAva/cubDFV6fzYwM8XPcx6sHUjz
=HM9R
-----END PGP SIGNATURE-----
--Sig_/sf+qaQLzc4sBIxJSAwiJRqx--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150824192710.08c77060>