Comment 10 for bug 811927

Hi gregory (2011.11.21_17:17:35_+0200)
> I'm only a debian user and a developer of a 32bits application (PCSX2)
> so I don't know anything about the UDD workflow. If you can share me
> some input I will be glad.

UDD is the bzr branches every package has.
http://developer.ubuntu.com/packaging/html/udd-intro.html

> I split them for no particular reason. I saw that control file provide
> libcg and libcggl so I create two packages. They can be merged. Maybe
> we can do a review of the package slit.
> /usr/include/* -> libcg-dev
> /usr/lib/* -> libcg
> remaining (doc, bin) -> nvidia-cg-toolkit or rename the package if you
> want. Maybe we can split all doc into a libcg-doc (or
> nvidia-cg-toolkit-doc) but my packager skill is beginner.

OK, I'd probably go for simply libcg + nvidia-cg-toolkit, for now, to
not deviate too much from Debian.

> I didn't understand anything on the prerm/postint stuff. What do you
> want to do exactly?

I think we can delete debian/*{prerm,postinst}
dh_makeshlibs adds ldconfig calls.

> Nvidia-cg-toolkit seems abandoned on debian. It didn't get any update
> from a long time (latest was on 19 Mar 2009). Current version is
> deprecated by Nvidia which send a "please upgade message" to all bts
> bug report ! For information there is another reverse-dependency :
> ogre-plugins-cgprogrammanager (at least on debian)

Yup, I did the last update here too. I don't want to take over
mainatinership of it in Debian, as I don't use it, though.

I should probably start the proceedings on getting it properly
orphaned...