# cuda-meta-13-1 review

a) debian/cuda-visual-tools-13-1.postinst

Why are the nsight and nvvp desktop files created in postinst, and not
shipped in their respective binary debian packages? I presume nsight is
shipped by cuda-nsight-13-1, but nvvp I don't know.


b) debian/cuda-toolkit.postinst debian/cuda-toolkit.postrm
b1) no #DEBHELPER# marker
b2) this script lies, as it says "Setting alternatives" (and removing in the 
postrm case) but doesn't. It's just the `echo`.

What's the point?


c) This source package produces only meta packages, right? These binary 
packages should usually be architecture all. Therefore they will only be built 
once, stored once (*_all.deb). But in this particular case, that would also 
mean these _all.deb packages would be uninstallable on !amd64/arm64, hm, 
interesting. I guess for now leaving them as is is best, but I was wondering if 
the thought occurred to you.

So I think my more important question is on (a), the desktop file
creation on postinst.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2141744

Title:
  [needs-packaging] cuda-13-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cuda-cccl-13-1/+bug/2141744/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to