Github messages for voidlinux
 help / color / mirror / Atom feed
From: st3r4g <st3r4g@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Cyclic dependency (notably, mesa, gobject-introspection)
Date: Fri, 15 May 2020 11:16:28 +0200	[thread overview]
Message-ID: <20200515091628.7VgRsb4WtzugL1DQPW0fS1c8Ll7ndswCaIFfSmxFH0Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21899@inbox.vuxu.org>

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

New comment by st3r4g on void-packages repository

https://github.com/void-linux/void-packages/issues/21899#issuecomment-629127980

Comment:
This is not really about mesa specifically.
A user has no reason to install `mesa-opencl` (or any other implementation of an API) alone by itself, unless he wants to do OpenCL development (in this case he should know he needs the loader too). Let's say instead someone wants to use an OpenCL-powered application: he will install that application, which links to the loader, therefore automatically getting the loader as a dependency. The simplest possible example of such an app is `clinfo`. Then you run `clinfo`, which says there are no actual OpenCL implementations in your system. They can't be automatically provided, because we don't know the hardware configuration (or needs of a certain impl) of the user. It is at this point that the user must make a choice: let's say he has an AMD card, so he goes for `mesa-opencl`. Or maybe the soon-to-be-packaged ROCm. Or both. `ocl-icd` is already there, pulled in by the actual application the user is trying to run.

  parent reply	other threads:[~2020-05-15  9:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13  0:57 [ISSUE] " fosslinux
2020-05-13 12:53 ` st3r4g
2020-05-13 12:57 ` st3r4g
2020-05-14  0:03 ` fosslinux
2020-05-14  8:29 ` st3r4g
2020-05-14 10:06 ` fosslinux
2020-05-14 10:33 ` st3r4g
2020-05-14 10:38 ` st3r4g
2020-05-14 22:30 ` fosslinux
2020-05-15  9:16 ` st3r4g [this message]
2020-05-16  4:44 ` fosslinux
2020-05-23  8:43 ` [ISSUE] [CLOSED] " Hoshpak

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=20200515091628.7VgRsb4WtzugL1DQPW0fS1c8Ll7ndswCaIFfSmxFH0Q@z \
    --to=st3r4g@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).