Bug#811484: Need mentor for packaging ruby-did-you-mean (RFP #811484)
Hi Antonio,
first of all, thanks for looking into this.
Yes, you're right, the Sonic Pi source made did_you_mean optional
recently. However, it *is* a component that Sam, the Sonic Pi main
developer, really wants to see included with the software, as it makes
the error messages more helpful for the users.
As you can see in https://github.com/samaaron/sonic-pi/issues/928 we
have already identified all gems that are needed to get the vendor/
directory out of Sonic Pi and thus remove all convenience copies of 3rd
party gem sources from upstream.
We are only missing did_you_mean, hamster (#811390) and wavefile
(#811086) in Debian to proceed packaging Sonic Pi for sid.
> Hi, after out chat on IRC today I have just uploaded
> ruby-did-you-mean
Thank you so much, that's great.
You asked on IRC about the deployment strategy for Sonic Pi. My goal is
to make Sonic Pi debian-compliant and maintain that package on Debian.
Based on that package, I want to make packages ready for Raspbian and
Ubuntu.
The Ubuntu PPA is already the test bed for my current incomplete
packaging attempt. The current state is
https://github.com/deb-pkg-sonic-pi/pkg-sonic-pi - it's not ready for
review and I haven't begun to remove the vendor/ directory there, yet.
ruby2.3 won't come to Raspbian in a long while, so I will have to make
sure that the package works with earlier ruby versions, too. While I can
live with offering ports of dependencies for Sonic Pi, I wouldn't want
to backport the ruby2.3 package to Raspbian just for this. So I'll see
if I can package a did_you_mean 0.10.0 version based on your example
that I can use for those distributions that don't have ruby2.3.
Yes, in the long run, the problem will just go away once the other
distributions ship with ruby2.3.
Thanks again, your help is very appreciated.
Kind regards,
Hanno
Reply to: