Comment 1 for bug 1522004
Revision history for this message
| Didier Roche-Tolomelli (didrocks) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
a60fb26
(Get the code!)
"[Standards compliance]
Yes... well not sure about binary postinst."
-> Yeah, I'm not fan either about that solution. Can't we achieve this more elegantly via a dpkg trigger? That way, we wouldn't fail the whole transition in case we can't compile the module.
Also, I think the package should dep on gcc or any involved compiler?
Finally, there is no obvious copyright of the file not in debian/ directory. We need to either:
- have one GPL2 header into that file (and then, we have an obvious "upstream" copyright
- ship a COPYING or LICENSE file.