On 3/26/21 9:41 AM, Jarl Gullberg wrote: > Thank you for the prompt reply! Presuming that I put in some elbow > grease and get the package into an acceptable state, is there still > time to submit it for bullseye, or has that window completely closed? > I'm assuming the option to submit it for bookworm and then to > bullseye-backports would still be there, but having it in the base > selection would definitely be the desired outcome.
No, it's too take to get it into bullseye, the hard freeze has started: https://release.debian.org/bullseye/freeze_policy.html#hard Getting it back into testing after the release and backporting it is the way to go to make it available on bullseye indeed. > As a bit of background, we're looking at using osgearth as the basis > for a new map-focused application at work, and we always try to limit > ourselves to what's in the base selection in order to simplify > workflows. Having to sideload osgearth in Debian 11 in a couple of > years would be undesirable (although, of course, possible). When you rely on a package in Debian it's important to be involved in its maintentance. If nothing else, you'll be in a better position to maintain the package in your own repo. osgEarth in Debian mostly because it was used for the Globe plugin in QGIS, but because it was nearly impossible to update osgEarth and keep the Globe plugin working it was deemed unfit for inclusion in Debian. This concern still stands. Like OSSIM no other package should be using it in their builld, but as liblwgeom has shown, if it's there, it will be used. Kind Regards, Bas -- GPG Key ID: 4096R/6750F10AE88D4AF1 Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1 _______________________________________________ Pkg-grass-devel mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-grass-devel
