Marco Atzeri writes:
>> That sounds like something you'd want to use alternatives for.
>
> alternative does not work for dll's
I keep forgetting that it uses symlinks… :-(
So could we not do this via postinstall scripts, then?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andro
On 6/23/2015 7:35 AM, Achim Gratz wrote:
Marco Atzeri writes:
1) openblas is optional but it collides with lapack blas.
So it must be before in the PATH
$ cygcheck -l libopenblas
/usr/bin/cygblas-0.dll
That sounds like something you'd want to use alternatives for.
alternative does not wo
Marco Atzeri writes:
> 1) openblas is optional but it collides with lapack blas.
> So it must be before in the PATH
>
> $ cygcheck -l libopenblas
> /usr/bin/cygblas-0.dll
That sounds like something you'd want to use alternatives for.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQk
On 6/22/2015 6:49 PM, Achim Gratz wrote:
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 /us
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 wo
Marco Atzeri writes:
> if I understood correctly a script called
>
> /etc/postinstall/zp_octave_finish.dash
>
> will be always executed at the end of the postinstall script
> sequence and never renamed as ".done".
Yes.
> I am moving the octave update script in
> /var/lib/octave/update_packages
On 5/30/2015 8:01 AM, Achim Gratz wrote:
Marco Atzeri writes:
TeXLive had the same problem, that's one of the reasons perpetual
postinstall scripts were introduced. You can look at that to see how
Ken deals with that.
..
> Regards,
> Achim.
>
Hi Achim,
if I understood correctly a script calle
On 5/30/2015 8:12 AM, Marco Atzeri wrote:
On 5/30/2015 8:01 AM, Achim Gratz wrote:
Marco Atzeri writes:
- /usr/share/octave/packages does not exist if the database is empty
so I can not change its permission in the postinstall phase before
its creation.
Why is that? Just because
On 5/30/2015 8:01 AM, Achim Gratz wrote:
Marco Atzeri writes:
- /usr/share/octave/packages does not exist if the database is empty
so I can not change its permission in the postinstall phase before
its creation.
Why is that? Just because cygport by default removes empty directories?
Marco Atzeri writes:
> /usr/share/octave/site/m/startup/octaverc is updating
> "/usr/share/octave/packages"
> if any subdirectory under "/usr/share/octave/" has been added
> or removed, to update the octave package database.
>
> Why do you see actions under "/usr/lib" ?
I simply remembered wrong
On 5/29/2015 9:22 PM, Achim Gratz wrote:
The site octaverc has code that tries to keep the package directory
up-to-date. That's a no-no, since normal users don't have permission to
change files under /usr/lib.
/usr/share/octave/site/m/startup/octaverc is updating
"/usr/share/octave/packages
The site octaverc has code that tries to keep the package directory
up-to-date. That's a no-no, since normal users don't have permission to
change files under /usr/lib.
Could you please remove that code and put the update into a post-install
script?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+
12 matches
Mail list logo
