apkkit issueshttps://git.adelielinux.org/adelie/apkkit/-/issues2019-07-11T14:01:42Zhttps://git.adelielinux.org/adelie/apkkit/-/issues/1Dependency SLOTs are not tracked, leading to impossible resolutions2019-07-11T14:01:42ZA. WilcoxDependency SLOTs are not tracked, leading to impossible resolutionsPackage names always include SLOT if non-zero. However, when reading out RDEPEND, SLOT is not included in the name of the dependency. This means that any package that depends on a slot will have an unsatisfiable dependency. This needs...Package names always include SLOT if non-zero. However, when reading out RDEPEND, SLOT is not included in the name of the dependency. This means that any package that depends on a slot will have an unsatisfiable dependency. This needs to be resolved.https://git.adelielinux.org/adelie/apkkit/-/issues/2EAPI=2+ weak blocks are not yet supported2019-07-11T14:01:42ZA. WilcoxEAPI=2+ weak blocks are not yet supportedThe docstring in the Portage module is not accurate. ! blocks are not warned on, they are treated as fatal as !! are.
See the [PMS](https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-830008.2.6) for information on the intended behaviour.The docstring in the Portage module is not accurate. ! blocks are not warned on, they are treated as fatal as !! are.
See the [PMS](https://dev.gentoo.org/~ulm/pms/head/pms.html#x1-830008.2.6) for information on the intended behaviour.https://git.adelielinux.org/adelie/apkkit/-/issues/3NEEDED is not parsed for extra dependencies2019-07-11T14:01:42ZA. WilcoxNEEDED is not parsed for extra dependenciesIt would be a very good idea to parse ``NEEDED`` or ``NEEDED.ELF.2`` for additional runtime dependencies, for a few reasons:
* ``RDEPEND`` can be outdated or just plain *wrong* sometimes.
* ``RDEPEND`` by design never contains anythi...It would be a very good idea to parse ``NEEDED`` or ``NEEDED.ELF.2`` for additional runtime dependencies, for a few reasons:
* ``RDEPEND`` can be outdated or just plain *wrong* sometimes.
* ``RDEPEND`` by design never contains anything in the ``@system`` profile or compiler runtimes, including libstdc++ and friends, which could cause issues if someone managed to build an entire system out of simple C apps then tried to install a C++ app without the runtime.
The apk-tools package upstream already seems to support ``so:foo`` where ``foo`` is a SONAME, therefore the apk side should be fairly easy. What we really should do, however, is strip SONAMEs that are provided by packages in ``RDEPEND``.