new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
#!/usr/bin/env python3
|
|
|
|
|
|
|
|
"""
|
2020-01-06 01:40:27 +00:00
|
|
|
Copyright 2020 Oliver Smith
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
|
|
|
|
This file is part of pmbootstrap.
|
|
|
|
|
|
|
|
pmbootstrap is free software: you can redistribute it and/or modify
|
|
|
|
it under the terms of the GNU General Public License as published by
|
|
|
|
the Free Software Foundation, either version 3 of the License, or
|
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
pmbootstrap is distributed in the hope that it will be useful,
|
|
|
|
but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
GNU General Public License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU General Public License
|
|
|
|
along with pmbootstrap. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
"""
|
|
|
|
|
|
|
|
"""
|
|
|
|
Functions that work on both pmaports and (binary package) repos. See also:
|
|
|
|
- pmb/helpers/pmaports.py (work on pmaports)
|
|
|
|
- pmb/helpers/repo.py (work on binary package repos)
|
|
|
|
"""
|
|
|
|
|
|
|
|
import copy
|
|
|
|
|
|
|
|
import pmb.helpers.pmaports
|
2018-12-03 20:02:18 +00:00
|
|
|
import pmb.helpers.repo
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
|
|
|
|
|
2019-02-15 14:32:39 +00:00
|
|
|
def get(args, pkgname, arch, replace_subpkgnames=False):
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
""" Find a package in pmaports, and as fallback in the APKINDEXes of the
|
|
|
|
binary packages.
|
|
|
|
:param pkgname: package name (e.g. "hello-world")
|
|
|
|
:param arch: preferred architecture of the binary package. When it
|
|
|
|
can't be found for this arch, we'll still look for another
|
|
|
|
arch to see whether the package exists at all. So make
|
|
|
|
sure to check the returned arch against what you wanted
|
|
|
|
with check_arch(). Example: "armhf"
|
2019-02-15 14:32:39 +00:00
|
|
|
:param replace_subpkgnames: replace all subpkgnames with their main
|
|
|
|
pkgnames in the depends (see #1733)
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
:returns: data from the parsed APKBUILD or APKINDEX in the following
|
|
|
|
format: {"arch": ["noarch"],
|
|
|
|
"depends": ["busybox-extras", "lddtree", ...],
|
|
|
|
"pkgname": "postmarketos-mkinitfs",
|
|
|
|
"provides": ["mkinitfs=0..1"],
|
|
|
|
"version": "0.0.4-r10"} """
|
|
|
|
# Cached result
|
|
|
|
cache_key = "pmb.helpers.package.get"
|
|
|
|
if (arch in args.cache[cache_key] and
|
2019-02-15 14:32:39 +00:00
|
|
|
pkgname in args.cache[cache_key][arch] and
|
|
|
|
replace_subpkgnames in args.cache[cache_key][arch][pkgname]):
|
|
|
|
return args.cache[cache_key][arch][pkgname][replace_subpkgnames]
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
|
|
|
|
# Find in pmaports
|
|
|
|
ret = None
|
|
|
|
pmaport = pmb.helpers.pmaports.get(args, pkgname, False)
|
|
|
|
if pmaport:
|
|
|
|
ret = {"arch": pmaport["arch"],
|
|
|
|
"depends": pmb.build._package.get_depends(args, pmaport),
|
2019-02-15 14:32:39 +00:00
|
|
|
"pkgname": pmaport["pkgname"],
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
"provides": pmaport["provides"],
|
|
|
|
"version": pmaport["pkgver"] + "-r" + pmaport["pkgrel"]}
|
|
|
|
|
|
|
|
# Find in APKINDEX (given arch)
|
2019-04-19 23:23:18 +00:00
|
|
|
if not ret or not pmb.helpers.pmaports.check_arches(ret["arch"], arch):
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
pmb.helpers.repo.update(args, arch)
|
2019-04-19 23:23:18 +00:00
|
|
|
ret_repo = pmb.parse.apkindex.package(args, pkgname, arch, False)
|
|
|
|
|
|
|
|
# Save as result if there was no pmaport, or if the pmaport can not be
|
|
|
|
# built for the given arch, but there is a binary package for that arch
|
|
|
|
# (e.g. temp/mesa can't be built for x86_64, but Alpine has it)
|
2019-04-21 21:17:31 +00:00
|
|
|
if not ret or (ret_repo and ret_repo["arch"] == arch):
|
2019-04-19 23:23:18 +00:00
|
|
|
ret = ret_repo
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
|
|
|
|
# Find in APKINDEX (other arches)
|
|
|
|
if not ret:
|
2018-12-03 20:02:18 +00:00
|
|
|
pmb.helpers.repo.update(args)
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
for arch_i in pmb.config.build_device_architectures:
|
|
|
|
if arch_i != arch:
|
|
|
|
ret = pmb.parse.apkindex.package(args, pkgname, arch_i, False)
|
|
|
|
if ret:
|
|
|
|
break
|
|
|
|
|
|
|
|
# Copy ret (it might have references to caches of the APKINDEX or APKBUILDs
|
|
|
|
# and we don't want to modify those!)
|
|
|
|
if ret:
|
|
|
|
ret = copy.deepcopy(ret)
|
|
|
|
|
|
|
|
# Make sure ret["arch"] is a list (APKINDEX code puts a string there)
|
|
|
|
if ret and isinstance(ret["arch"], str):
|
|
|
|
ret["arch"] = [ret["arch"]]
|
|
|
|
|
2019-02-15 14:32:39 +00:00
|
|
|
# Replace subpkgnames if desired
|
|
|
|
if replace_subpkgnames:
|
|
|
|
depends_new = []
|
|
|
|
for depend in ret["depends"]:
|
|
|
|
depend = get(args, depend, arch)["pkgname"]
|
|
|
|
if depend not in depends_new:
|
|
|
|
depends_new += [depend]
|
|
|
|
ret["depends"] = depends_new
|
|
|
|
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
# Save to cache and return
|
|
|
|
if ret:
|
|
|
|
if arch not in args.cache[cache_key]:
|
|
|
|
args.cache[cache_key][arch] = {}
|
2019-02-15 14:32:39 +00:00
|
|
|
if pkgname not in args.cache[cache_key][arch]:
|
|
|
|
args.cache[cache_key][arch][pkgname] = {}
|
|
|
|
args.cache[cache_key][arch][pkgname][replace_subpkgnames] = ret
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
return ret
|
|
|
|
|
|
|
|
# Could not find the package
|
|
|
|
raise RuntimeError("Package '" + pkgname + "': Could not find aport, and"
|
|
|
|
" could not find this package in any APKINDEX!")
|
|
|
|
|
|
|
|
|
|
|
|
def depends_recurse(args, pkgname, arch):
|
|
|
|
""" Recursively resolve all of the package's dependencies.
|
|
|
|
:param pkgname: name of the package (e.g. "device-samsung-i9100")
|
|
|
|
:param arch: preferred architecture for binary packages
|
|
|
|
:returns: a list of pkgname_start and all its dependencies, e.g:
|
|
|
|
["busybox-static-armhf", "device-samsung-i9100",
|
|
|
|
"linux-samsung-i9100", ...] """
|
|
|
|
# Cached result
|
|
|
|
cache_key = "pmb.helpers.package.depends_recurse"
|
|
|
|
if (arch in args.cache[cache_key] and
|
|
|
|
pkgname in args.cache[cache_key][arch]):
|
|
|
|
return args.cache[cache_key][arch][pkgname]
|
|
|
|
|
|
|
|
# Build ret (by iterating over the queue)
|
|
|
|
queue = [pkgname]
|
|
|
|
ret = []
|
|
|
|
while len(queue):
|
|
|
|
pkgname_queue = queue.pop()
|
|
|
|
package = get(args, pkgname_queue, arch)
|
|
|
|
|
|
|
|
# Add its depends to the queue
|
|
|
|
for depend in package["depends"]:
|
|
|
|
if depend not in ret:
|
|
|
|
queue += [depend]
|
2019-02-15 14:32:39 +00:00
|
|
|
|
|
|
|
# Add the pkgname (not possible subpkgname) to ret
|
|
|
|
if package["pkgname"] not in ret:
|
|
|
|
ret += [package["pkgname"]]
|
new action: 'pmbootstrap repo_missing'
Add a new action that lists all aports, for which no binary packages
exist. Only list packages that can be built for the relevant arch
(specified with --arch). This works recursively: when a package can be
built for a certain arch, but one of its dependencies
(or their depends) can not be built for that arch, then don't list it.
This action will be used for the new sr.ht based build infrastructure,
to figure out which packages need to be built ahead of time (so we can
trigger each of them as single build job). Determining the order of the
packages to be built is not determined with pmbootstrap, the serverside
code of build.postmarketos.org takes care of that.
For testing purposes, a single package can also be specified and the
action will list if it can be built for that arch with its
dependencies, and what needs to be built exactly.
Add pmb/helpers/package.py to hold functions that work on both pmaports
and (binary package) repos - in contrary to the existing
pmb/helpers/pmaports.py (see previous commit) and pmb/helpers/repo.py,
which only work with one of those.
Refactoring:
* pmb/helpers/pmaports.py: add a get_list() function, which lists all
aports and use it instead of writing the same glob loop over and over
* add pmb.helpers.pmaports.get(), which finds an APKBUILD and parses it
in one step.
* rename pmb.build._package.check_arch to ...check_arch_abort to
distinguish it from the other check_arch function
2018-11-15 07:36:39 +00:00
|
|
|
ret.sort()
|
|
|
|
|
|
|
|
# Save to cache and return
|
|
|
|
if arch not in args.cache[cache_key]:
|
|
|
|
args.cache[cache_key][arch] = {}
|
|
|
|
args.cache[cache_key][arch][pkgname] = ret
|
|
|
|
return ret
|
|
|
|
|
|
|
|
|
|
|
|
def check_arch(args, pkgname, arch, binary=True):
|
|
|
|
""" Can a package be built for a certain architecture, or is there a binary
|
|
|
|
package for it?
|
|
|
|
|
|
|
|
:param pkgname: name of the package
|
|
|
|
:param arch: architecture to check against
|
|
|
|
:param binary: set to False to only look at the pmaports, not at binary
|
|
|
|
packages
|
|
|
|
:returns: True when the package can be built, or there is a binary
|
|
|
|
package, False otherwise
|
|
|
|
"""
|
|
|
|
if binary:
|
|
|
|
arches = get(args, pkgname, arch)["arch"]
|
|
|
|
else:
|
|
|
|
arches = pmb.helpers.pmaports.get(args, pkgname)["arch"]
|
2019-04-19 23:20:16 +00:00
|
|
|
return pmb.helpers.pmaports.check_arches(arches, arch)
|