all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Fri, 08 Sep 2017 17:39:08 +0200	[thread overview]
Message-ID: <87shfx9p43.fsf@gnu.org> (raw)
In-Reply-To: <1504870325.2630.39.camel@tourbillion-technology.com> (Paul Garlick's message of "Fri, 08 Sep 2017 12:32:05 +0100")

Hi Paul,

Paul Garlick <pgarlick@tourbillion-technology.com> skribis:

>> 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.  

Good!

> 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")))

Sounds good.

> 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?  

Perhaps adding an extra phase at the end that simply calls ‘symlink’?

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

Yes.

> The links would allow the runpaths to be validated.  So; 
>
> -       #:validate-runpath? #f ; '#:elf-directories' is not recognised
> here

That’d be great.  If that phase errors out, it probably means that the
binaries won’t work out of the box, so it’s good to fix it.

(BTW, please note that executables should go to bin/, libraries and
other architecture-dependent files to lib/, and share/ is for
architecture-independent stuff.  I suppose we’ll only have bin/ and lib/
for a start, that’s OK.)

> The FOAM_INST_DIR variable would need to be updated:
>
> -            (files '(".")))))
>  +          (files '("./lib")))))

I really dislike this FOAM_INST_DIR variable (usually packages “know”
where they are installed and don’t need an extra variable for that), but
if it has to be there, then so be it.  :-)

I think we should be all set?  I’ll wait for your hopefully last patch
revision!

Besides, for the future, if you have an opportunity to discuss these
matters with upstream, I’d recommend suggesting the addition of a proper
installation phase (“make install”), and also support at least for an
installation prefix, and ideally for more directory categories (see
<https://www.gnu.org/prep/standards/html_node/Directory-Variables.html>).

Thanks for your patience!

Ludo’.

      parent reply	other threads:[~2017-09-08 15: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
2017-09-14 15:46             ` Paul Garlick
2017-09-15 16:35               ` bug#28045: " Ludovic Courtès
2017-09-08 15:39     ` Ludovic Courtès [this message]

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=87shfx9p43.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.