Lines Matching refs:package

26 package project_metadata;
35   // Name of this API/package.
38   // A short description (a few lines) of the package. It will be
48   // The name and description for the package should be specified using the top
55   // URL(s) associated with the package.
59   // a package should contain only a single URL from these types.  Occasionally,
60   // a package may be broken across multiple archive files for whatever reason,
66   // The package version.  In order of preference, this should contain:
67   //  - If the package comes from Git or another source control system,
70   //  - a released package version such as "1.0", "2.3-beta", etc.
71   //  - the date the package was retrieved, formatted as "As of YYYY-MM-DD".
74   // The date of the change in which the package was last upgraded from
76   // This should only identify package upgrades from upstream, not local
80   // Note: this is NOT the date that this version of the package was released
84   // License type that identifies how the package may be used. See
88   // Description of local changes that have been made to the package.  This does
101   // The homepage for the package. This will eventually replace
106 // URL associated with a third-party package.
109     // The homepage for the package. For example, "https://bazel.io/". This URL
111     // or to get more information about the package. This is especially helpful
116     // The URL of the archive containing the source code for the package, for
120     // The URL of the upstream git repository this package is retrieved from.
125     // Use of a git URL requires that the package "version" value must specify a
129     // The URL of the upstream SVN repository this package is retrieved from.
133     // Use of an SVN URL requires that the package "version" value must specify
137     // The URL of the upstream mercurial repository this package is retrieved
141     // Use of a mercurial URL requires that the package "version" value must
145     // The URL of the upstream darcs repository this package is retrieved
149     // Use of a DARCS URL requires that the package "version" value must
154     // package is being migrated into third_party from elsewhere in piper, or
155     // when a package is being newly developed in third_party.  For newly
156     // developed packages, the PIPER URL should reference the package itself
157     // (e.g. "http://google3/third_party/my/package")
167     // The URL identifying where the local copy of the package source code can
170     // Typically, the metadata files describing a package reside in the same
171     // directory as the source code for the package. In a few rare cases where
175     // package was retrieved from.