unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Garlick <pgarlick@tourbillion-technology.com>
To: paul@apatience.com, guix-devel@gnu.org
Subject: Re: Adding Trilinos to dealii package
Date: Mon, 24 May 2021 18:53:49 +0100	[thread overview]
Message-ID: <fcff37ccb52814c2a5fa1f30050929aa433f5ab7.camel@tourbillion-technology.com> (raw)
In-Reply-To: 8iXokLJz8g9vAHrX2pFDjHgz8tYMLRM4CNZwiOx2nQXIf6gO7B0PQGFigeTmf-vFzIIZi7Io4YSBkQezgQ7BsToDVkT2jeoqFVSMvJuX9kI=@apatience.com

Dear Paul,

> I would like to eventually package the Lethe CFD library

Nice!

Trilinos has many bells and whistles. I imagine that there will be some
significant effort required to package it.  One option would be to
subdivide the library and initially package only the elements you need
for Lethe.  See the Debian approach to packaging Trilinos for example
[1].

If Lethe does not use PETSc there would be no risk of conflict.  The
choice between including the new Trilinos (sub)package as a dependency
of dealii and dealii-openmpi or creating new dealii-trilinos and
dealii-trilinos-openmpi packages would be marginal.  How many models
need to use PETSc and Trilinos at the same time?

> This assumes people won't mind having to build Trilinos as a
> dependency for dealii even if they don't need it.

The model run times are usually very much longer than the library build
times.  I expect this would be true for Trilinos and Lethe too.

Best regards,

Paul.

[1]: https://packages.debian.org/source/buster/trilinos



             reply	other threads:[~2021-05-24 17:54 UTC|newest]

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

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=fcff37ccb52814c2a5fa1f30050929aa433f5ab7.camel@tourbillion-technology.com \
    --to=pgarlick@tourbillion-technology.com \
    --cc=guix-devel@gnu.org \
    --cc=paul@apatience.com \
    /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).