You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doxygen/src/pdsc_format.txt
+10-9Lines changed: 10 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -64,7 +64,7 @@ The \ref packFormat is structured using grouping elements and contains the follo
64
64
- \subpage element_ECCN "<ECCN>": section listing Export Control Classification Numbers (ECCN) for EU and US.
65
65
- \subpage element_keywords "<keywords>": lists keywords to search for packages. Can be used for search engines.
66
66
- \ref element_component_environments "environments": Grouping element for environments information. Each inner \ref element_component_environment "environment" element may be used to provide tool-specific information pertaining to the package as a whole.
67
-
- \subpage element_repository "<repository>": specifies the URL and repository type of a public repository where the pack originates from.
67
+
- \subpage element_repository "<repository>": specifies the HTTPS URL and repository type of a public repository where the pack originates from.
68
68
- \subpage element_dominate "<dominate>": the pack contains one or more device, API, or component that overrules other packs with identical items.
69
69
- \subpage element_releases "<releases>": lists release versions with descriptions.
70
70
- \subpage pdsc_changelogs_pg "<changeLogs>": lists changelog files associated with components and apis within the pack.
@@ -98,8 +98,8 @@ This example of a *.pdsc File explains the sections, particularly how dependenci
98
98
/**
99
99
\page pdsc_package_pg /package element
100
100
The basic package information captures the package vendor, the package name, a brief description of the package, and the schema version.
101
-
Additional elements support the logistics of handling packages. The url specifies the origin of the description. It may be left empty if
102
-
the pack will not be uploaded onto a web server. A license file might point to license agreements. A list of keywords
101
+
Additional elements support the logistics of handling packages. The url (https required) specifies the origin of the description. It may
102
+
be left empty if the pack will not be uploaded onto a web server. A license file might point to license agreements. A list of keywords
103
103
assists searching for packages. An optional environments element can be used to list environment-specific information.
104
104
105
105
\b Example:
@@ -243,7 +243,8 @@ assists searching for packages. An optional environments element can be used to
\page element_repository /package/repository element
625
-
The element specifies the URL of the public repository the pack originates from. The attribute 'type' specifies the repository technology
626
-
and therefore the tools required to be used with this repository.
626
+
The element specifies the URL (HTTPS required) of the public repository the pack originates from. The attribute 'type'
627
+
specifies the repository technology and therefore the tools required to be used with this repository.
627
628
628
629
629
630
\b Example:
@@ -853,7 +854,7 @@ This list must be strictly ordered by `version`, with the highest release `versi
853
854
</tr>
854
855
<tr>
855
856
<td>url</td>
856
-
<td>URL specifying the location of the pack of the specified version. This can be used to override the default location being \c \<url>/\<vendor>.\<name>.\<version>.pack</td>
857
+
<td>HTTPS URL specifying the location of the pack of the specified version. This can be used to override the default location being \c \<url>/\<vendor>.\<name>.\<version>.pack</td>
0 commit comments