public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: [Attn Maintainer] octave
Date: Mon, 22 Jun 2015 16:49:00 -0000	[thread overview]
Message-ID: <87r3p3g02p.fsf@Rainer.invalid> (raw)
In-Reply-To: <556C2E40.3050409@gmail.com> (Marco Atzeri's message of "Mon, 01	Jun 2015 12:04:48 +0200")

Marco Atzeri writes:
> 2) zp_octave_finish.dash checks if
>    /var/lib/octave/update.flag exists
>   and if so execute
>   /usr/bin/octave-cli /var/lib/octave/update_packages_list

You need to set the path in the update script so that it finds the DLL
in /usr/lib/lapack or the script will never work (I just see you already
fixed it for 64bit).

The shells running postinstall don't source /etc/profile or anything
like that, so you need to set up the environment as you need it.  BTW,
the postinstall scripts for octave-forge should all be dash scripts as
well, just as any other postinstall script that isn't making use of any
bash specific feature.  You don't need to check for the existence of the
update file there either, just touch it.

Again, why is it not possible to keep that DLL in a standard location or
link octave with the correct runtime search path?  If it absolutely must
be on path, then couldn't you just add it on the invocation via a
wrapper script?


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

SD adaptation for Waldorf Blofeld V1.15B11:
http://Synth.Stromeko.net/Downloads.html#WaldorfSDada

  parent reply	other threads:[~2015-06-22 16:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-29 19:23 Achim Gratz
2015-05-30  5:13 ` Marco Atzeri
2015-05-30  6:01   ` Achim Gratz
2015-05-30  6:12     ` Marco Atzeri
2015-05-30  6:18       ` Marco Atzeri
2015-06-01 10:05     ` Marco Atzeri
2015-06-01 16:20       ` Achim Gratz
2015-06-22 16:49       ` Achim Gratz [this message]
2015-06-22 20:43         ` Marco Atzeri
2015-06-23  5:35           ` Achim Gratz
2015-06-23  6:20             ` Marco Atzeri
2015-06-23 15:32               ` Achim Gratz

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=87r3p3g02p.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --cc=cygwin-apps@cygwin.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.
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).