From 775f7cea47815694fde145f72a764f5b43bcb661 Mon Sep 17 00:00:00 2001 From: Stephen J Day Date: Wed, 13 Sep 2017 11:41:45 -0700 Subject: [PATCH] platforms: update format for platform specifier Signed-off-by: Stephen J Day --- platforms/platforms.go | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/platforms/platforms.go b/platforms/platforms.go index 95c40d7f9..56c6ddc51 100644 --- a/platforms/platforms.go +++ b/platforms/platforms.go @@ -49,8 +49,9 @@ // While the OCI platform specifications provide a tool for components to // specify structured information, user input typically doesn't need the full // context and much can be inferred. To solve this problem, we introduced -// "specifiers". A specifier has the format `[/[/]]`. -// The user can provide either the operating system or the architecture or both. +// "specifiers". A specifier has the format +// `||/[/]`. The user can provide either the +// operating system or the architecture or both. // // An example of a common specifier is `linux/amd64`. If the host has a default // of runtime that matches this, the user can simply provide the component that @@ -130,10 +131,10 @@ func (m *matcher) String() string { // Parse parses the platform specifier syntax into a platform declaration. // -// Platform specifiers are in the format [/[/]]. The -// minimum required information for a platform specifier is the operating system -// or architecture. If there is only a single string (no slashes), the value -// will be matched against the known set of operating systems, then fall +// Platform specifiers are in the format `||/[/]`. +// The minimum required information for a platform specifier is the operating +// system or architecture. If there is only a single string (no slashes), the +// value will be matched against the known set of operating systems, then fall // back to the known set of architectures. The missing component will be // inferred based on the local environment. //