Tags and releases

[alexxy]

Hi! I want to add this package for gentoo linux (as well as update for prusaslicer 2.7-alpha). But it seems i can only add live build for this repo, since it doesnt have any tags/releases.

So can you add tag corresponding to version that builds with alpha of prusaslicer, since its mandatory dependency for it.

[oxivanisher]

This is somewhat related to the Octoprint plugin which would like to add bgcode support to it. Will there be releases/builds of the library somewhere i.e. in PyPi?

[alexxy]

No, its not related to Octoprint, but it will be good to have

[oxivanisher]

No, its not related to Octoprint, but it will be good to have

I meant it the other way around, sorry. The octoprint problem is also somewhat depending on having releases/tags to build a useful plugin.

[alexxy]

Also its actual problem for packagers, since prusa-slicer 2.7.0 released and it depend on this library

[foosel]

Best would be to have this tagged and released on pypi, ideally not only as source but as wheels for x86, armv6 & armv7. That way it won't have to be compiled on every single thing depending on it.

[jneilliii]

I would also like to stress the importance of wheel releases on pypi. As it stands now, every plugin update in the OctoPrint plugin requires rebuilding the library, which on a pi 4 has reported to take upwards of 12 minutes.

[alexxy]

So. What about adding release tags for this repo?

[CorporalCrawdad]

I'm looking to package PrusaSlicer 2.8.1 for void linux, which depends on this library. If this repo is not ready for a 1.0, can we at least get a 0.* release so it can be packaged for distros that require versioned releases?