Conversation
|
@adamjstewart ping. |
|
Looks good to me. Is there a particular file found in the tar that is indicative of Octave extensions? If so one of us can add logic to create.py to automatically detect the build system, add |
|
judging from the list of packages http://octave.sourceforge.net/packages.php , they are have the same prefix in the url with |
1332575 to
0faa6dd
Compare
| Octave('--eval', 'pkg install %s' % self.stage.archive_file) | ||
| """ | ||
| # Octave extension builds can have a global Octave executable function | ||
| module.Octave = Executable(join_path(self.spec.prefix.bin, 'octave')) |
There was a problem hiding this comment.
Why Octave and not octave (like the binary it is tied to)?
|
I think |
|
@adamjstewart as far as i can tell, this should work for majority of cases . |
|
Will do. |
UPDATE: does install now, octave seems to pick up the installed package:
relevant documentation
https://www.gnu.org/software/octave/doc/v4.0.1/Installing-and-Removing-Packages.html
https://www.gnu.org/software/octave/doc/v4.0.1/Command-Line-Options.html#Command-Line-Options
TODO if possible:
octave --eval pkg uninstall <name>. Otherwise octave still consider the package to be installed.outdated:
I can install packages from Spack's env bash:
but i can't make it work from within Spack:
whereas from log you see that it did something
and actually installed the package
Any advices/ideas?
p.s. ideally fixes #1111