Bug#649514: nvidia-cg-toolkit: should this package be orphaned?

Miguel A. Colón Vélez debian.micove at gmail.com
Thu May 17 19:05:02 UTC 2012


>- please merge github over to git.d.o, this is confusing since
>d/control explicitely ref git.d.o as the main VCS location

I was told to make the repository in github to make it easier to
review. The idea was to make it small commits since the packaging was
made about 2 years ago and updated since then. When it was deemed
ready and reviewed it was supposed to get merged to the one in
git.d.o, tagged and uploaded. Should not have caused confusion if it
went like that since the github ones most likely would have been
deleted. I will wait for a reply from the others before merging it
since I'm not sure what they want to do and I'm not entirely sure if
the upgrade issues in amd64 are completely fixed.

>- d/rules should use uscan to get-orig-source, see ref [1] for an
>example on how to add a shell script in d/watch

The way upstream is setup:
1) The location of the tarballs change with each release.
2) The file names of the source tarballs don't contain the version
number and can't be mangled (Ex: Cg-3.1_April2012_x86.tgz,

I know how to use scripts in the watch file but uscan is not useful in
this case.

>- some overlinking issues:
Some of those are binary blobs from upstream. The others I was aware
of and I was planning to add LDFLAGS += -Wl,--as-needed before it got
uploaded or in the next revision


More information about the pkg-nvidia-devel mailing list