all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: 57679@debbugs.gnu.org, Ontje.Luensdorf@dlr.de
Subject: [bug#57679] [RFC PATCH] gnu: Add paraview.
Date: Thu, 03 Nov 2022 16:04:04 +0100	[thread overview]
Message-ID: <87leosqduj.fsf@gnu.org> (raw)
In-Reply-To: <87bkpp8evk.fsf@elephly.net> (Ricardo Wurmus's message of "Wed, 02 Nov 2022 17:50:14 +0100")

Hi,

Ricardo Wurmus <rekado@elephly.net> skribis:

> Attached is an earlier version of Paraview (5.9.1) that has been
> submitted by Ontje (in Cc).

Good.  I think you can push so we have a feeling of progress on this.

> @Ludo: there doesn’t seem to be a way to unbundle VTK, because Paraview
> is closely tied to VTK, reuses its build system to some extent, and is
> better understood as an *extension* to VTK than a client application
> using VTK merely as a library.  Upstream also commented that unbundling
> VTK is not a priority and would have to be supported by the community.

Alright.  The ‘guix-hpc’ channel has an older version that I packaged:

  https://gitlab.inria.fr/guix-hpc/guix-hpc/-/blob/master/inria/staging.scm

There was a ‘PARAVIEW_USE_EXTERNAL_VTK’ CMake flag, though apparently it
wasn’t enough.

Anyway, please make sure the reasons for not unbundling are documented
in comments, with links to relevant resources.

Thanks!

Ludo’.




  reply	other threads:[~2022-11-03 15:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 15:24 [bug#57679] [RFC PATCH] gnu: Add paraview Paul A. Patience
2022-09-24 13:33 ` Ludovic Courtès
2022-09-26  0:54   ` Maxim Cournoyer
2022-09-28 15:02     ` Paul A. Patience
2022-11-02 16:50 ` Ricardo Wurmus
2022-11-03 15:04   ` Ludovic Courtès [this message]
2022-12-28 15:37 ` bug#57679: " Ricardo Wurmus

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=87leosqduj.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=57679@debbugs.gnu.org \
    --cc=Ontje.Luensdorf@dlr.de \
    --cc=rekado@elephly.net \
    /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. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.