Possible to launch a Dev Branch of Raspotify that Tracks Dev Branch of Librespot

[txoof]

I have a project (PaperPi) that depends on SpoCon/librespot-java which has a built-in ability to pull now-playing information and album art.

Something has gone off the rails with regards to the Java version and the latest version of Bullseye. Local builds fail and SpoCon (which provides a tidy debian package) crashes on play.

After some coaching from @JasonLG1979, I built the dev branch of librespot and used the onevent sample script to get pretty much everything I need.

I've installed raspotify and then just plunked in the newly built dev version of librespot into /usr/bin/ and tested it out. It works perfect for my needs, but it is rather a round-about way of doing this. The one caveat is that the config file needs to have an explicity LIBRESPOT_AUTOPLAY=on directive for the service to start properly.

Is there a possibility to build raspotify-dev against librespot-dev?

[JasonLG1979]

You could just fork Raspotify and point to the librespot dev branch in the build script and make whatever changes you need elsewhere.

I have no plans on doing Raspotify-dev

[JasonLG1979]

5 is not needed. The make file does that.

[JasonLG1979]

You will also need to change the build profile to release when building upstream librespot.

[JasonLG1979]

I usually also prune the container right after I build or at least before I rebuild to make sure that I'm building with the latest base. For me anyway the docker build environment is a single use thing in this case. I'm sure there's a way to tell docker to never save/cache it for later?

[txoof]

You will also need to change the build profile to release when building upstream librespot.

Unsure what you mean by this?

I usually also prune the container right after I build or at least before I rebuild to make sure that I'm building with the latest base.

So just docker container prune and kill the stopped containers?

After substituting in https://github.com/librespot-org/librespot.git into build.sh, I ran another make (without pruning) and everything went as expected, but kicked the error below and failed to produce a .deb file. I suspect this has something to do with lines 65-78 in build.sh. Any ideas what I need to move past this?

   Compiling librespot v0.4.2-raspotify-fork (/mnt/raspotify/librespot)
    Finished raspotify [optimized] target(s) in 12m 44s
Copy Librespot binary to package root...
'/build/armv7-unknown-linux-gnueabihf/raspotify/librespot' -> 'raspotify/usr/bin/librespot'
Generate Debian control...
Build Raspotify deb...
dpkg-deb: error: parsing file 'raspotify/DEBIAN/control' near line 2 package 'raspotify':
 'Version' field value '0.43.46~librespot.unknown-': revision number is empty
make: *** [Makefile:8: armhf] Error 2

[txoof]

when I try to run the commands on lines 65/66 manually from the librespot cloned repo they appear to work:

$ git describe --tags "$(git rev-list --tags --max-count=1)" 2>/dev/null
v0.4.2

$ git rev-parse HEAD | cut -c 1-7 2>/dev/null
fc549b9

Not sure why they yield '0.43.46~librespot.unknown-' when run from in the build script.