Can you please add some information how that above mentioned problems will be handled? I see them as an important blocker for that bug and will fix it after above mentioned problems are solved.
I see the idea behind it as an important benefit, but don't think that the template mentioned in the bug report is the way to go (also with some changes I saw Tuesday in the git repository). It is ok for me to call `dpkg --print-architecture` and send that information to the dkms-postinst script, but I don't feel comfortable by adding that architecture mapping code . It should be quite easy and more future safe to add it to the dkms-postinst script.
Can you please add some information how that above mentioned problems will be handled? I see them as an important blocker for that bug and will fix it after above mentioned problems are solved.
I see the idea behind it as an important benefit, but don't think that the template mentioned in the bug report is the way to go (also with some changes I saw Tuesday in the git repository). It is ok for me to call `dpkg --print- architecture` and send that information to the dkms-postinst script, but I don't feel comfortable by adding that architecture mapping code . It should be quite easy and more future safe to add it to the dkms-postinst script.