billchenchina/ognibuild
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Rename architecture.md.

Browse source
This commit is contained in:
Jelmer Vernooij 2021-02-20 01:50:29 +00:00
parent b689774fa6
commit f0e45ab26b
No known key found for this signature in database
GPG key ID: 579C160D4C9E23E8
2 changed files with 0 additions and 31 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

30
notes/structure.md
View file

@ -1,30 +0,0 @@
Upstream requirements are expressed as objects derived from UpstreamRequirement.
They can either be:
* extracted from the build system
* extracted from errors in build logs
The details of UpstreamRequirements are specific to the kind of requirement,
and otherwise opaque to ognibuild.
When building a package, we first make sure that all declared upstream
requirements are met.
Then we attempt to build.
If any problems are found in the log, buildlog-consultant will report them.
ognibuild can then invoke "fixers" to address Problems.
Problems can be converted to UpstreamRequirements by UpstreamRequirementFixer
Other Fixer can do things like e.g. upgrade configure.ac to a newer version.
UpstreamRequirementFixer uses a UpstreamRequirementResolver object that
can translate UpstreamRequirement objects into apt package names or
e.g. cpan commands.
ognibuild keeps finding problems, resolving them and rebuilding until it finds
a problem it can not resolve or that it thinks it has already resolved
(i.e. seen before).

1
ognibuild/resolver/apt.py
View file

@ -22,7 +22,6 @@ from ..apt import AptManager
from . import Resolver from . import Resolver
from ..requirements import ( from ..requirements import (
BinaryRequirement, BinaryRequirement,
PythonPackageRequirement,
) )