Hi all,
On Mon, Dec 07, 2015 at 06:08:41PM +0100, Helge Kreutzmann wrote: > Hello Muammar, > hello ZenWalker, > smc is not part of testing since June. The last maintainer upload was > 2013. The standard version is quite out of date. No open bug has a reply > from the maintainer. I locally rebuild smc (on stable) with an > uptodate git checkout and it seems to work fine. Also the update of > the standards version is a noop (no change required). > > So the status of the maintenance of current smc is unclear. SMC cannot compile with latest versions of CEGUI IIRC. And I cannot keep in the archive two versions of the library. > > I locally build tsc (as a Debian package, however, not fit for > release, but I can provide it as a start if someone wants to continue work > on it). It build (on stable) without any problem; however it crashes > immediately when I try to start the first level. (I haven't > investigated further). > I prepared a debian/ directory that you can check in the upstream's github¹. I lost some interest because nobody checked that this could be safely merged... The new TSC needs some mruby packages that are not in debian. So what they did was to ship them with the source, and this is not acceptable in Debian. I asked them to build TSC using external² mruby extensions. And the reply was more or less like they will need to work this a bit before it is possible. Then, I decided to send a message to the debian mailing list, and each of those submodules have to be present in debian before uploading TSC. Honestly, I am not willing to do this... as I am not interested in ruby. > In principle, given that smc and tsc do not share their name and seem > to have a different aim both should coexist; however, currently > neither is available. > > Muammar, it would be great to hear your plans. > So in summary, there exists a debian/ directory that compiles debian packages as seen in Ref. 1. Those changes haven't been accepted by upstream in github. Mruby modules are needed in the archive before uploading, and the source as it is right now cannot be compiled using external mruby extensions. I wouldn't have any problems to maintain TSC provided that those modules are maintained by someone else. I am open to team-maintain the package as well. Regards, -- Muammar El Khatib. http://muammar.me | http://proyectociencia.org
