timblechmann
.deb packaging effort
Hello,
there is an effort to package the Supercollider sc3-plugins for Debian.
While doing so, it turned out that both main Supercollider and sc3-plugins need the nova-simd library for building.
Discussing this on the #debian-multimedia IRC channel, it occured that it would thus make sense to package nova-simd as a development package which then both supercollider and sc3-plugins can build-depend on. Would you agree with this or would rather want to see it as part of Debian's supercollider-dev package? (as discussed here with @danstowell)
If a separate package is ok, what versioning should the package use? There are no obvious download releases or version numbers for this github repo.
Instead, I could use the most-recent commit date and id as a versioning scheme. e.g. the "current" version could be nova-simd_git20141024-0.4514831.orig.tar.gz. Would that be ok?
nova-simd doesn't have a stable API, so sc3-plugins and supercollider should use the version that is bundled (or referenced as git submodule).
i know that i'm disagreeing with the debian package guidelines, but nova-simd is really an implementation detail and should be bundled with the source packages and not treated as dependency. especially: there is no guarantee that sc3-plugins or supercollider depend on the same version.
packaging nova-simd as separate library will call for trouble without any benefit, especially as its a header-only library.
OK, thanks.
especially: there is no guarantee that sc3-plugins or supercollider depend on the same version.
Really? I didn't really see that, they both seem to use the same version.
they might use the same version and API changes might be rare ... but the point is: i don't want to give any guarantees on it, that's why i'd suggest to bundle it ... safer, less effort for bundling and maintaining the packages ...