From: ludo@gnu.org (Ludovic Courtès)
To: Paul Garlick <pgarlick@tourbillion-technology.com>
Cc: 28045@debbugs.gnu.org
Subject: [bug#28045] [PATCH] gnu: Add openfoam
Date: Mon, 11 Sep 2017 13:39:16 +0200 [thread overview]
Message-ID: <87mv61a2hn.fsf@gnu.org> (raw)
In-Reply-To: <1505121536.2356.21.camel@tourbillion-technology.com> (Paul Garlick's message of "Mon, 11 Sep 2017 10:18:56 +0100")
Hi Paul,
Paul Garlick <pgarlick@tourbillion-technology.com> skribis:
> I think it is helpful to consider this question in two ways; thinking about the short term and the longer term. I think in the short term it is best to stick with the OpenFOAM-standard layout, modified in the 'middle-road' way suggested
> earlier. On top of the previous points made, there is an additional advantage to this approach in that the OpenFOAM-standard layout has been thoroughly tested in production use over many years.
>
> In the longer term I think it would be possible to develop a Guix-standard layout. I cannot see any reason why this would not work. However, with a large system such as OpenFOAM, this may not necessarily be an easy task. I see this
> as principally an upstream job, since they are the most knowledgeable people on the current layout and are best placed to deal with any subleties involved. With a working Guix package in place it will be a good time to contact
> upstream and discuss the merits of a new layout.
I agree. So for now, I’d say go with the bin/ symlink, and then start a
discussion with upstream to see how to improve things in the future.
> Today I hope to finish the package definition. I have placed the tree under the 'lib' directory and this allows the 'validate-runpath' phase to run. The phase currently fails as ld-wrapper does not add the runpaths of the shared objects in
> the build tree. I plan to use patchelf to fix this.
I would refrain from using PatchELF, if possible, by just passing
-Wl,-rpath=DIR at link time, where DIR is the final library directory.
Ludo’.
next prev parent reply other threads:[~2017-09-11 11:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1504818378.3116.38.camel@tourbillion-technology.com>
2017-08-11 11:06 ` [bug#28045] [PATCH] gnu: Add openfoam Paul Garlick
2017-08-14 23:07 ` Marius Bakke
2017-08-15 2:49 ` Eric Bavier
2017-08-16 17:52 ` Paul Garlick
2017-08-16 20:04 ` Eric Bavier
2017-08-17 9:42 ` Paul Garlick
2017-08-22 13:02 ` Ludovic Courtès
2017-08-22 17:10 ` Paul Garlick
2017-08-22 22:33 ` Ludovic Courtès
2017-08-30 15:08 ` Paul Garlick
2017-09-06 21:28 ` Paul Garlick
2017-09-07 11:57 ` Ludovic Courtès
2017-09-07 22:41 ` [bug#28045] [PATCH] gnu: Add openfoam] Paul Garlick
2017-09-08 8:23 ` [bug#28045] [PATCH] gnu: Add openfoam Ludovic Courtès
2017-09-08 11:32 ` Paul Garlick
2017-09-08 15:34 ` Eric Bavier
2017-09-08 20:30 ` Ludovic Courtès
2017-09-11 9:18 ` Paul Garlick
2017-09-11 11:39 ` Ludovic Courtès [this message]
2017-09-14 15:46 ` Paul Garlick
2017-09-15 16:35 ` bug#28045: " Ludovic Courtès
2017-09-08 15:39 ` [bug#28045] " Ludovic Courtès
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=87mv61a2hn.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=28045@debbugs.gnu.org \
--cc=pgarlick@tourbillion-technology.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 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.