| Age | Commit message (Collapse) | Author |
|---|
|
* python-native is an exception because there is still e.g. chromium depending
on _native_ python and a lot of people use it in some form, once
https://bugs.chromium.org/p/chromium/issues/detail?id=942720
is resolved in stable chromium release the same will be set in python-native
* https://www.python.org/doc/sunset-python-2/
* https://python3statement.org/
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
|
|
Fixes:
"dnssec-configure requires the pyparser package from
http://pyparsing.wikispaces.com
[...]
"
Fixes:
"dnskey-pull requires the python-dns package from
http://www.dnspython.org/
[...]
"
It has dependencies on the split packages from python manifest, but
since it RDEPENDS on "python", all standard lib modules are pulled in.
If someone requires a smaller image, the RDEPENDS could be paired down.
It also requires "curl" as shown in INSTALL and:
https://github.com/xelerance/dnssec-conf/blob/8e799683736b4a7b5e5e78f98fba0a6f48393537/dnskey-pull#L86
It also requires "host" (from bind-utils) as shown in:
https://github.com/xelerance/dnssec-conf/blob/8e799683736b4a7b5e5e78f98fba0a6f48393537/dnskey-pull#L299
It recommends "bind", but another nameserver can be used. That level of
complexity is left up to someone that needs a different configuration.
Signed-off-by: Tim Orling <ticotimo@gmail.com>
|
|
dnssec-conf did not receive any updates since 2010 and relies heavily on
python2 code base.
Move recipe to meta-python2 layer, since python2 support has been dropped in
oe-core.
Signed-off-by: Andrey Zhizhikin <andrey.z@gmail.com>
Signed-off-by: Tim Orling <ticotimo@gmail.com>
|
Martin Jansa
Tim Orling
Andrey Zhizhikin