unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Paul Garlick <pgarlick@tourbillion-technology.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28045@debbugs.gnu.org
Subject: [bug#28045] [PATCH] gnu: Add openfoam
Date: Fri, 08 Sep 2017 12:32:05 +0100	[thread overview]
Message-ID: <1504870325.2630.39.camel@tourbillion-technology.com> (raw)
In-Reply-To: <87y3ppk39y.fsf@gnu.org>

Hi Ludo,


> Does it address the use case you have in mind?

Yes, I think that both the multiple-profile solution and the 'ad-hoc'
environment will work for Guix/OpenFOAM.  

The traditional method of installing multiple OpenFOAM versions is to
install to a common $FOAM_INST_DIR directory.  However, as you point
out, this is not strictly necessary and does not provide any advantage
in the Guix system.

So, continuing the 'middle road' line of thought, the 'install-dir'
variable would be modified to add a '/lib' element:

-                                %output "/OpenFOAM-" ,version)))
+                                %output "/OpenFOAM-" ,version
"/lib")))

You suggest adding a link between bin and lib/OpenFOAM-
4.1/platforms/linux64GccDPInt32Opt/bin.  What would be the best way to
add this to the package definition?  

There could also be a link between lib and lib/OpenFOAM-
4.1/platforms/linux64GccDPInt32Opt/lib.

The links would allow the runpaths to be validated.  So; 

-       #:validate-runpath? #f ; '#:elf-directories' is not recognised
here

The FOAM_INST_DIR variable would need to be updated:

-            (files '(".")))))
 +          (files '("./lib")))))

WDYT?

Paul.

  reply	other threads:[~2017-09-08 11:33 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 [this message]
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
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

  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=1504870325.2630.39.camel@tourbillion-technology.com \
    --to=pgarlick@tourbillion-technology.com \
    --cc=28045@debbugs.gnu.org \
    --cc=ludo@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).