unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Paul A. Patience" <paul@apatience.com>
To: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Adding Trilinos to dealii package
Date: Fri, 21 May 2021 12:36:14 +0000	[thread overview]
Message-ID: <8iXokLJz8g9vAHrX2pFDjHgz8tYMLRM4CNZwiOx2nQXIf6gO7B0PQGFigeTmf-vFzIIZi7Io4YSBkQezgQ7BsToDVkT2jeoqFVSMvJuX9kI=@apatience.com> (raw)

Hi,

I would like to eventually package the Lethe CFD library [1], but it
requires a version of dealii compiled with Trilinos, which is not
currently available in Guix.

PETSc and Trilinos (and many other libraries available in Guix) can be
compiled with several different options.
What is the standard way to deal with this in Guix?
From what I can tell, in general the packages get a reasonable default
and people who require different options make a channel and inherit from
the base package, and in some really practical cases we get a variant of
the package with a similar name, e.g., dealii-openmpi.

The potential problem with PETSc and Trilinos when it comes to dealii is
that some of the optional modules they can be compiled with are the
same, which causes trouble when dealii is configured with both of
them [2].
(From what I can tell, the module in question is not configured in the
Guix package for PETSc, so this point may be moot.)

I'm wondering what the best way would be to add Trilinos to the dealii
packages (assuming I manage to package Trilinos as well).
In other words, which would be best among the following:

- Build Trilinos with a reasonable configuration for dealii [3] and
  update the dealii and dealii-openmpi packages to include it (if the
  problem mentioned above turns out not to be an issue).
  This assumes people won't mind having to build Trilinos as a
  dependency for dealii even if they don't need it.

- Build Trilinos as above but add separate packages for the resulting
  dealii, e.g., dealii-trilinos, dealii-trilinos-openmpi.
  This seems like it would get awkward quite quickly, which is why
  assuming my thoughts on the purposes of channels are correct, this is
  the inferior option.

- Abandon all hope and just maintain a channel for dealii configured
  with Trilinos (the inferiorer option :)).

- Some other possibility I have not thought of.

Thank you and best regards,
Paul

[1]: https://github.com/lethe-cfd/lethe
[2]: https://www.dealii.org/current/external-libs/petsc.html
[3]: https://www.dealii.org/current/external-libs/trilinos.html



             reply	other threads:[~2021-05-22 12:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-21 12:36 Paul A. Patience [this message]
2021-05-23  5:19 ` Adding Trilinos to dealii package Arun Isaac
  -- strict thread matches above, loose matches on Subject: below --
2021-05-23 12:40 zimoun
2021-05-24 17:04 ` Leo Famulari
2021-05-24 17:53 Paul Garlick

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='8iXokLJz8g9vAHrX2pFDjHgz8tYMLRM4CNZwiOx2nQXIf6gO7B0PQGFigeTmf-vFzIIZi7Io4YSBkQezgQ7BsToDVkT2jeoqFVSMvJuX9kI=@apatience.com' \
    --to=paul@apatience.com \
    --cc=guix-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).