tags 288324 + pending thanks (I'm directly emailing everyone who emailed the bug report to make sure they all notice this, as well as Bccing everyone who emailed me privately, so that their email addresses are not exposed for spam purposes.)
Hi all, I am extremely sorry that I have neglected this package for several years. The original reason I had packaged this went away, and I don't use it myself. Once enough time had gone by without any action being needed (about 3 years), I had become so disinterested already when the wishlist new-version bug was filed that I let the bug sit until I was too ashamed at my neglect to deal with it any time within the following 3 years. Even though I don't use this package anymore, it is a very low-maintenance package, and I now have both the time and motivation to return to my Debian packaging duties and give this package the minimal attention it needs. Spurred into action by Christoph Berg's recent orphaning of this package, I now have created a package that's fully up-to-date on both upstream and Debian Policy changes, have closed his orphaning wnpp bug, and am about to resume my maintainership by uploading the package to Debian. Rest assured I am now quite determined not to let this problem happen again for tolua or for any package I may maintain in the future. Again, please accept my apologies. The package I am about to upload is the official tolua, which is up to version 5.1 now (using Lua 5.1), not tolua++. Tolua++ could be packaged by someone else if they want, in a separate package. Also, the shared library is going away. Debian advises against having a shared library without upstream coordination, and even though upstream long ago acknowledged the patch I sent him to add a shared library, the versions he has released subsequently do not include a shared library, leaving me to conclude that at least for the time being he does not want a shared library. Thus the only binary package is libtolua-dev, containing a static library, a header file, and the binary tolua program for use at build time. - Jimmy Kaplowitz [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
