On 01/09/2017 06:20 PM, Bruce Ashfield wrote:
The functionality you describe is a good thing, but I have a few
questions to make
sure I understand the change, and confirm that existing functionality
isn't broken ..
and that the internals of the package management do the right thing
(I'm not an
expert on those internals .. so bear with me).
I am not an expert either so I thought I'd suggest this since it works
for me and see how it is received.
With this change, do you know if RDEPENDS="kernel-module-foo" still
works ? or
does it now have to be RDEPENDS="kernel-module-foo-<version>" ?
No, the old writing would not work. You would need to add the version as
in your second example. That will break things, true.
On a similar thought, "smart install kernel-module-foo" would also
work ? or does it
now require a version ?
Also in this example you would need to add the version, even though I
have only used apt-get and not smart.
The meta package "kernel-modules" will work as before, without a version
postfix.
So basically, as I understand it, this may be a blocker for this change.
Alternatives I can come up with are:
1) For all packaged kernel modules, add meta packages that depend on the
correct version of the kernel module itself. Then "kernel-module-foo"
would depend on "kernel-module-foo-<version>". The package
"kernel-modules" would then still be made depending on
"kernel-module-foo-<version>" and the likes.
2) Make the version postfix configurable with a
KERNEL_MODULE_PACKAGE_POSTFIX, exactly like the prefix (which was added
recently). The default would be an empty postfix, but it could be used
to achieve this functionality for those who need it.
No. 2 is a very simple change. No. 1 is more uncertain (to me at least).
/Ola
--
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core
