Project

General

Profile

Actions

Feature #15343

open

package metadata could contain git branch and commit

Added by Joshua M. Clulow 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
packaging
Start date:
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
External Bug:

Description

We currently use Set Actions to attach a variety of metadata to a package:

$ pkg contents -r -t set system/kernel
NAME                          VALUE
info.classification           org.opensolaris.category.2008:System/Core
org.opensolaris.consolidation osnet
org.opensolaris.smf.fmri      ['svc:/system/dumpadm', 'svc:/system/dumpadm:default', 'svc:/system/intrd', 'svc:/system/intrd:default', 'svc:/system/scheduler', 'svc:/system/scheduler:default']
pkg.description               core kernel software for a specific instruction-set architecture
pkg.fmri                      pkg://helios-dev/system/kernel@0.5.11,5.11-1.0.21408:20221212T210940Z
pkg.summary                   Core Solaris Kernel
variant.arch                  i386
variant.debug.illumos         ['false', 'true']
variant.opensolaris.zone      ['global', 'nonglobal']

When Git is the SCM for a build, we could attach other provenance properties as well; e.g., we might want:

$ pkg contents -r -t set system/kernel
NAME                          VALUE
...
build.git.branch              master
build.git.commit              33978c4b5557a6a1dc35ef166f620b6839539ff6
...

It is possible that distributions are already doing this in their build systems, so we should survey and coordinate as part of naming the metadata. Probably we should not use the pkg.* prefix?

No data to display

Actions

Also available in: Atom PDF