bump version to 2022.02.9

add miyoo_defconfig
This commit is contained in:
tiopex
2023-01-31 13:11:45 +01:00
parent 1fa746c353
commit dcdaa3599c
8423 changed files with 184305 additions and 91107 deletions

View File

@@ -48,11 +48,11 @@ system is based on hand-written Makefiles or shell scripts.
33: endef
34:
35: define LIBFOO_DEVICES
36: /dev/foo c 666 0 0 42 0 - - -
36: /dev/foo c 666 0 0 42 0 - - -
37: endef
38:
39: define LIBFOO_PERMISSIONS
40: /bin/foo f 4755 foo libfoo - - - - -
40: /bin/foo f 4755 foo libfoo - - - - -
41: endef
42:
43: $(eval $(generic-package))
@@ -256,7 +256,7 @@ not and can not work as people would expect it should:
+scp://[user@]host:filepath+, and that filepath is relative to the
user's home directory, so you may want to prepend the path with a
slash for absolute paths:
+scp://[user@]host:/absolutepath+. +
+scp://[user@]host:/absolutepath+. The same goes for SFTP URLs. +
If +HOST_LIBFOO_SITE+ is not specified, it defaults to
+LIBFOO_SITE+.
Examples: +
@@ -291,6 +291,8 @@ not and can not work as people would expect it should:
+ftp://+.
** +scp+ for downloads of tarballs over SSH with scp. Used by
default when +LIBFOO_SITE+ begins with +scp://+.
** +sftp+ for downloads of tarballs over SSH with sftp. Used by
default when +LIBFOO_SITE+ begins with +sftp://+.
** +svn+ for retrieving source code from a Subversion repository.
Used by default when +LIBFOO_SITE+ begins with +svn://+. When a
+http://+ Subversion repository URL is specified in
@@ -314,8 +316,7 @@ not and can not work as people would expect it should:
13:45+01" see "man cvs" for further details).
** +git+ for retrieving source code from a Git repository. Used by
default when +LIBFOO_SITE+ begins with +git://+. The downloaded
source code is cached as with the +svn+
method.
source code is cached as with the +svn+ method.
** +hg+ for retrieving source code from a Mercurial repository. One
'must' specify +LIBFOO_SITE_METHOD=hg+ when +LIBFOO_SITE+
contains a Mercurial repository URL. The downloaded source code
@@ -342,6 +343,10 @@ not and can not work as people would expect it should:
submodules when they contain bundled libraries, in which case we
prefer to use those libraries from their own package.
* +LIBFOO_GIT_LFS+ should be set to +YES+ if the Git repository uses
Git LFS to store large files out of band. This is only available for
packages downloaded with git (i.e. when +LIBFOO_SITE_METHOD=git+).
* +LIBFOO_STRIP_COMPONENTS+ is the number of leading components
(directories) that tar must strip from file names on extraction.
The tarball for most packages has one leading component named
@@ -502,6 +507,39 @@ LIBFOO_IGNORE_CVES += CVE-2020-12345
LIBFOO_IGNORE_CVES += CVE-2020-54321
----------------------
* +LIBFOO_CPE_ID_*+ variables is a set of variables that allows the
package to define its https://nvd.nist.gov/products/cpe[CPE
identifier]. The available variables are:
+
--
** +LIBFOO_CPE_ID_PREFIX+, specifies the prefix of the CPE identifier,
i.e the first three fields. When not defined, the default value is
+cpe:2.3:a+.
** +LIBFOO_CPE_ID_VENDOR+, specifies the vendor part of the CPE
identifier. When not defined, the default value is
+<pkgname>_project+.
** +LIBFOO_CPE_ID_PRODUCT+, specifies the product part of the CPE
identifier. When not defined, the default value is +<pkgname>+.
** +LIBFOO_CPE_ID_VERSION+, specifies the version part of the CPE
identifier. When not defined the default value is
+$(LIBFOO_VERSION)+.
** +LIBFOO_CPE_ID_UPDATE+ specifies the _update_ part of the CPE
identifier. When not defined the default value is +*+.
--
+
If any of those variables is defined, then the generic package
infrastructure assumes the package provides valid CPE information. In
this case, the generic package infrastructure will define
+LIBFOO_CPE_ID+.
+
For a host package, if its +LIBFOO_CPE_ID_*+ variables are not
defined, it inherits the value of those variables from the
corresponding target package.
The recommended way to define these variables is to use the following
syntax: