From: Cons-Cat <Cons-Cat@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] Package Request: Nsight Graphics (and request for pr advice)
Date: Sat, 25 Dec 2021 19:33:09 +0100 [thread overview]
Message-ID: <20211225183309.V1zsYyJxJ1QN6lSuOLc6-h3HCpdDKYodgNJP9vWuIUI@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34022@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1261 bytes --]
Closed issue by Cons-Cat on void-packages repository
https://github.com/void-linux/void-packages/issues/34022
Description:
https://developer.nvidia.com/nsight-graphics
This is a weird one, and I'd be willing to try a pull request to help with it. I've already gotten this app to work on my Void Linux machine, so it is usable today. But Nsight Graphics is unusual because:
A) Ideally, legacy versions would be packaged because Nvidia removes this tool's ability to profile GPU architectures as soon as they release a new architecture for their products. For instance, Pascal GPUs cannot be used for any version of Nsight Graphics beyond 2021.1, even though Pascal GPUs are still sold and are very common. I don't know how far back you need to go for Maxwell architecture support.
B) It provides an installer interface that generates a complicated directory rather than providing a simple tarball and listing out the shared object libraries you need.
I'm not sure what the protocol in Void is for handling apps that need multiple versions packaged in parity, or ones that have complicated set up. I'd appreciate some advice on how I could proceed with a pull request for this, as it is a popular and important application for graphics programming.
prev parent reply other threads:[~2021-12-25 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-11 3:52 [ISSUE] Package Request: Nsight Graphics (and request for packaging advice) Cons-Cat
2021-12-25 18:33 ` Package Request: Nsight Graphics (and request for pr advice) Cons-Cat
2021-12-25 18:33 ` Cons-Cat [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211225183309.V1zsYyJxJ1QN6lSuOLc6-h3HCpdDKYodgNJP9vWuIUI@z \
--to=cons-cat@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).