Github messages for voidlinux
 help / color / mirror / Atom feed
From: namgo <namgo@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [Package request] Nvidia CUDA Kit
Date: Tue, 05 Dec 2023 14:17:33 +0100	[thread overview]
Message-ID: <20231205131733.98p-n_9Gyho9BIAWIniQPabDqmNfGURenO6727GFNEk@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20077@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1347 bytes --]

New comment by namgo on void-packages repository

https://github.com/void-linux/void-packages/issues/20077#issuecomment-1840696345

Comment:
@mcneb10 I'm asking on irc today, but given how archlinux packages cuda, it MIGHT be possible to distribute the binaries/libraries/headers as their own package.

One nice thing about the CUDA bins/libs/headers is that they're really just that. It appears that the driver that void-linux ships with is cuda-compatible. (note: this is not a well-tested statement and I'm questioning myself - see next comment).

I'll update when I hear back from others on how to proceed.

The EULA is confusing to me, otoh we're legally able to distribute the SDK, but only if it's used by our "application". This makes me think I should contact one of the arch linux packagers to see what they do.

- I sent off an email to the arch linux package maintainer responsible for CUDA, I'll hopefully hear back soon.
- if I hear back with an easy licensing option, I'll describe it here
- If it requires someone signing off on a legalities email, I'll let one of the void-linux maintainers know that they can do that.

Meanwhile, I'll spend some time and figure out the least ugly hack to re-package CUDA under void's templating. Even if it ends up being a licensing nightmare, it'd be good to document how to do it.

  parent reply	other threads:[~2023-12-05 13:17 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 20:40 [ISSUE] Question: Is there a package for the Nvidia CUDA Kid Frick-David
2020-03-13 22:44 ` daniel-eys
2020-12-03  7:31 ` Question: Is there a package for the Nvidia CUDA Kit Frick-David
2021-03-12  4:50 ` WormChickenWizard
2022-04-16  2:02 ` github-actions
2022-04-19 13:20 ` WormChickenWizard
2022-04-19 17:16 ` Duncaen
2022-05-25 14:02 ` [Package request] " soanvig
2022-06-03  7:02 ` jjc224
2022-06-03  7:03 ` jjc224
2023-04-30 20:16 ` DirtyVoid
2023-10-03 20:47 ` namgo
2023-11-05  3:49 ` mcneb10
2023-11-05  3:56 ` mcneb10
2023-11-05  4:07 ` mcneb10
2023-11-05  9:17 ` mcneb10
2023-12-04 18:57 ` namgo
2023-12-04 18:59 ` namgo
2023-12-04 19:46 ` namgo
2023-12-04 23:58 ` mcneb10
2023-12-05 12:26 ` namgo
2023-12-05 13:06 ` namgo
2023-12-05 13:09 ` namgo
2023-12-05 13:17 ` namgo [this message]
2023-12-05 13:25 ` namgo
2023-12-05 13:29 ` namgo
2023-12-05 14:52 ` namgo
2023-12-05 15:07 ` namgo
2024-01-28 16:08 ` atisharma
2024-02-23 19:37 ` namgo
2024-03-31  2:24 ` jlhamilton777

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=20231205131733.98p-n_9Gyho9BIAWIniQPabDqmNfGURenO6727GFNEk@z \
    --to=namgo@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).