On Wed, Feb 26, 2020 at 5:17 pm, Pirate Praveen
<prav...@onenetbeyond.org> wrote:
On Wed, Feb 26, 2020 at 5:08 pm, Pirate Praveen
<prav...@onenetbeyond.org> wrote:
Package: gem2deb
Severity: wishlist
Version: 1.0.5
In case of gemspecs in their own sub directories just adding
X-DhRuby-Root and binary packages in control is enough. But when the
gemspecs are in the root of the repo, things are not very straight
forward.
I tried for about 4 hours to get concurrent-ruby and
concurrent-ruby-ext gems built from same source repo (I end up
getting empty binary packages with various options tried already).
If we can have a similar option of just adding X-DhRuby-Gemspec in
control to a binary package stanza in control, that will make things
very simple.
Int the short term, can so meone help with ruby-concurrent? I have
single-source and single-source-2 branches with 2 different
approcahes to fix this problem of combining the two source packages.
First approach is to ship ruby-concurrent-ext binary and manually
handle the other gems, second approach is to still get the 2 binaries
working (ruby-concurrent-ext ends up as an empty binary, except for
the /usr/share/doc part).
With some hacks (manually install the second binary package), I managed
to build both packages from same source. But it'd be nice if this can
be handled properly by gem2deb.
But now I get a lintian error
E: ruby-concurrent-ext: library-not-linked-against-libc
usr/lib/x86_64-linux-gnu/rubygems-integration/2.5.0/extensions/x86_64-linux/2.5.0/concurrent-ruby-ext-1.1.6/concurrent/concurrent_ruby_ext.so
Please check master branch of ruby-concurrent. Any ideas?
