Date: Tue, 18 Jun 2019 12:25:04 +0200 From: =?UTF-8?B?VMSzbA==?= Coosemans <tijl@FreeBSD.org> To: Mathieu Arnold <mat@FreeBSD.org>, bapt@FreeBSD.org Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org, svn-ports-head@freebsd.org Subject: Re: svn commit: r503385 - head/Mk/Scripts Message-ID: <20190618122504.791b3fcd@kalimero.tijl.coosemans.org> In-Reply-To: <20190615170158.489616a4@kalimero.tijl.coosemans.org> References: <201906031257.x53Cvi9P092541@repo.freebsd.org> <20190615170158.489616a4@kalimero.tijl.coosemans.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 15 Jun 2019 17:01:58 +0200 T=C4=B3l Coosemans <tijl@FreeBSD.org> wrote: > On Mon, 3 Jun 2019 12:57:44 +0000 (UTC) Mathieu Arnold <mat@FreeBSD.org> > wrote: >> Author: mat >> Date: Mon Jun 3 12:57:44 2019 >> New Revision: 503385 >> URL: https://svnweb.freebsd.org/changeset/ports/503385 >>=20 >> Log: >> Use UCL for pkg-message >> =20 >> Remain backward compatible but use ucl for the pkg-messages, which all= ows to: >> - append messages one after the other >> - only print message on delete, install, upgrade from a version to ano= ther >> =20 >> If pkg-message starts with a [ we consider it should be a valid ucl fi= le >> =20 >> The format is the following: >> [ >> { message: "Always print" }, >> { message: "package being removed", type: remove }, >> { message: "package being installed", type: install }, >> { message: "package is being upgraded", type: upgrade }, >> { message: "Upgrading from lower than 1.0", maximum_version: "1.0", ty= pe: upgrade }, >> { message: "Upgrading from higher than 1.0", minimum_version: "1.0", t= ype: upgrade }, >> { message: "Upgrading from >1.0 < 3.0", maximum_version: "3.0", minimu= m_version: "1.0", >> ] >> =20 >> Because it is ucl one can use some sugar like: >> [ >> { message =3D <<EOD >> formatted >> message 'with fancy things' >> EOD >> }, >> } =20 >=20 > Can this be extended to include these fields: > opsys: <operating system this message applies to> > osversion: <list of os version ranges this message applies to> > arch: <list of architectures this message applies to> > options: <list of options that need to be on or off> Or should pkg-message just be created dynamically at package build time in these cases?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190618122504.791b3fcd>