Bug#796550: RFP: sonic-pi -- live coding synth designed for ease of use
[Serge Schneider]
> We get a compiled release from Sam, then build the .deb using the
> previous verion's packaging files as a template:
> http://archive.raspberrypi.org/debian/pool/main/s/sonic-pi/sonic-pi_2.6.0-3.debian.tar.gz
Ouch. So if there is a problem with the binary package and Sam is
unavailable, you have no way to fix it?
> If reworking the package means it could go straight to Debian and
> automatically pulled in by Raspbian, it would save time in the long run.
> However, Sonic Pi releases are fairly frequent and, for us, the latest
> version needs to be in 'stable', which is not going to happen under
> standard Debian.
Well, you can always backport the package from sid or unstable to stable
and stick it in your own repository, if you want to.
> Some input from a Debian maintaner would be useful here. I have doubts
> that we would be able to find a sponsor to get this into untested or
> sid, even if a proper source package existed.
Well, I am a Debian developer, and do not believe it will be hard to get
the package uploaded, once there is a source package available that
build the deb with pbuilder based on unstable/sid.
I would prefer to use a git-repository buildable using git-buildpackage,
but am open to other approaches if you want a different work flow.
--
Happy hacking
Petter Reinholdtsen
Reply to: