svn commit: r503385 - head/Mk/Scripts

[Baptiste Daroussin]

On Tue, Jun 18, 2019 at 12:48:32PM +0200, Tijl Coosemans wrote:
> On Tue, 18 Jun 2019 12:32:03 +0200 Baptiste Daroussin <bapt at FreeBSD.org>
> wrote:
> > On Tue, Jun 18, 2019 at 12:25:04PM +0200, Tijl Coosemans wrote:
> >> On Sat, 15 Jun 2019 17:01:58 +0200 Tijl Coosemans <tijl at FreeBSD.org>
> >> wrote:  
> >>> On Mon, 3 Jun 2019 12:57:44 +0000 (UTC) Mathieu Arnold <mat at FreeBSD.org>
> >>> wrote:  
> >>>> Author: mat
> >>>> Date: Mon Jun  3 12:57:44 2019
> >>>> New Revision: 503385
> >>>> URL: https://svnweb.freebsd.org/changeset/ports/503385
> >>>> 
> >>>> Log:
> >>>>   Use UCL for pkg-message
> >>>>   
> >>>>   Remain backward compatible but use ucl for the pkg-messages, which allows to:
> >>>>   - append messages one after the other
> >>>>   - only print message on delete, install, upgrade from a version to another
> >>>>   
> >>>>   If pkg-message starts with a [ we consider it should be a valid ucl file
> >>>>   
> >>>>   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", type: upgrade },
> >>>>   { message: "Upgrading from higher than 1.0", minimum_version: "1.0", type: upgrade  },
> >>>>   { message: "Upgrading from >1.0 < 3.0", maximum_version: "3.0", minimum_version: "1.0",
> >>>>   ]
> >>>>   
> >>>>   Because it is ucl one can use some sugar like:
> >>>>   [
> >>>>   { message = <<EOD
> >>>>   formatted
> >>>>   message 'with fancy things'
> >>>>   EOD
> >>>>   },
> >>>>   }    
> >>> 
> >>> 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?  
> > 
> > For now it is pretty simple on how it works.
> > 
> > Yes we could imagine those extension easily, I will see what I can do.
> > but in the mean time one can create pkg-message based on the option.
> 
> No need to rush.  It's just something that popped into my head when I
> saw the firefox pkg-message.
> 
> > The only non easy one for me to add is the one based on options.
> 
> I'm not familiar with the syntax of UCL, but I imagine it would look
> similar to the options section in the output of "pkg info -f firefox"?

Yes I planned to use firefox as a guinea pig ;)

Best regards,
Bapt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/svn-ports-all/attachments/20190618/41487082/attachment.sig>