On Mon, Dec 14, 2009 at 06:11:16PM -0300, Felipe Sateler wrote: > However: > - How are transitions eased by this? AFAIK, lua looks for $modulename.so > when a module is required, so as long as I don't provide 2 versions I > don't get any help.
I was thinking of renaming, like what just happened. if your module was csnd and now is luaCsnd, you could make just one share library with 2 symbols (luaopen_csnd and luaopen_luaCsnd) for the same function and ship 2 symlinks, then remove one in a late upload, when all packages depending on it changed their require statements. Maybe it's a bit overkilling, so far no one depends on liblua5.1-cnsd... > - doing -llua5.1-csnd doesn't work because there is no public .so > symlink. The 2 options I see to fix this are not completely > satisfactory: > 1. Ship it in the binary package. This breaks when X.Y changes to X.Z > and Breaks: need to be added for all previous versions. > 2. Create a new package for just one symlink. What I usually do is ship a -dev package containing: - .so symlink - .a for static linking - .pc for pkg-config - developer documentation - .h with the declaration of luaopen_foo If you don't want to ship 2 packages for lua, you may put all that stuff in the -dev package of the mail library, maybe adding a provide: libalu5.1-csnd-dev. Cheers and thanks for your work -- Enrico Tassi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
