Comment 8 for bug 811927

Hi, thanks for this effort.

BTW, if you want to expose a bunch of discrete changes like this, the UDD (bzr) workflow can work nicely.

While you are here, can we update this to the latest CG toolkit version?

The description probably should say "In this package" rather than "the components include"

Why are we splitting libcg from libcggl? They are provided togother, and don't have a stable ABI (does they?). It's also starting to look like nvidia-cg-toolkit should be broken into libcg-dev and libcg-bin.

I don't think we need the preinst or postrm (debhelper should take care of that), but we do need that preinst in all the binary packages, or we could break the upgrade path from lucid.

There should be a build-depends on dpkg-dev (>= 1.16)

The conflicts should be on (<< 3.0.0007-0ubuntu2) obviously, increase that if you do a newer upstream version.

There should be a "set -e;" before the for loop.

Please include a descriptive changelog entry.

I suggest enganging with the Debian maintainer about this, as well. There were no responses to my "multi-orig rather than download during postinst" changes, but you never know, sometimes another poke is all that's needed...

BTW, I can't see any reverse dependencies. Although there is one reverse-build-dependency: crystalspace-glshader-cg