Thanks guys. The confusion I'm concerned about in (2) is not the library files themselves, but the package names. If we install roccat-tools' liblua.so.2 to, say, /usr/lib/<arch>/roccat/liblua.so.2, should it's package name just be liblua2, or something else? I can imagine a Lua programming language developer mistakenly installing roccat-tools' liblua2 package when they really want liblua5.2-0. This is why I'm thinking that we might want to name the package something like roccat-modules-lua2.
-- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/CAOHv88PiLyw6VXn6zK=jf3sxc95zsxov8xaqwkmd4elsdrx...@mail.gmail.com
