Re: Self Introduction
by Steven Munroe
Now that pveclib <https://munroesj52.github.io/> is safely integrated as a
Fedora package and Fedora 31 is released, I though it was time to offer my
expertise to package developers doing vector code.
In a previous life I learned a lot about the PowerISA and as the initial
contributor of GCC's PowerPC implementation of the Intel (tm) vector
intrinsic headers and as the primary implementer of pveclib, I learned a
lot about the differences, similarities, and generally how GCC behaves when
compiling vector codes and intrinsics.
This was documented in the"
Linux on Power Porting Guide: Vector Intrinsics
http://openpowerfoundation.org/wp-content/uploads/resources/Vector-Intrin...
And continues with the implementation of pveclib and associated
documentation.
If this is of interest or you have issues, problems, questions about the
best, good, practical approaches to vector programing for you package, Sent
me a note and I will try to answer.
4 years, 4 months
How to create octave packages to allow "pkg load" to be aware of dependencies?
by Qianqian Fang
Dear list,
I am packaging a few octave toolboxes for Fedora. Some of the toolboxes
have a dependency to other toolboxes.
On the rpm package level, I can use *Requires* to ask rpm to install
these dependent modules, but when running Octave, the *pkg load* command
is not aware of the dependent toolboxes and automatically load them.
I would like to know if anyone know if pkg is capable of loading
dependent toolboxes? if yes, what file I should create to tell pkg such
information? because the spec file uses the
*%octave_pkg_{build,install,preun}* macros to create toolbox packages, I
am wondering if adding dependency info is supported by these macros (and
how).
thanks
Qianqian
4 years, 5 months