Dear mentors,
There is a package I maintain that was abandoned, but now it has been forked. I have decided to upload a new version renaming it, and following instructions in [1]. In this new project, and that is the doubt I have, the package is being built using a version of mruby[2] different from the one in the debian archive. In addition, new upstream authors are using 3rd-party mruby extensions[4]. I believe this represents a problem because in theory a debian package has to be able to compile with already distributed binaries/libs in the archive. As you may have noticed, this would be the first time I intend to upload a package that depends on ruby. Would it be fine to upload the package compiled with these upstream shipped versions of mruby/extensions? or does it has absolutely to be compiled with the versions present in the debian archive?. I ask it because those mruby parts are compiled statically. I would be glad if anyone could help me with this. Regards, [1] https://www.debian.org/doc/manuals/developers-reference/pkgs.html#s5.9.3 [2] https://github.com/Secretchronicles/TSC/blob/v2.0.0-rc1/tsc/mruby_tsc_build_config.rb [3] https://github.com/Secretchronicles/TSC/tree/v2.0.0-rc1/mruby/mgems [4] https://github.com/Secretchronicles/TSC/tree/devel/mruby -- Muammar El Khatib. Linux user: 403107. GPG Key = 71246E4A. http://muammar.me | http://proyectociencia.org ,''`. : :' : `. `' `- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
