| Summary: | Installing an octave package needs the octave-devel Mageia pkg, missing dependency | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Jybz <j.biernacki+mga> |
| Component: | RPM Packages | Assignee: | All Packagers <pkg-bugs> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | eatdirt |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | octave-5.1.0-7.1.mga7.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Jybz
2020-02-13 14:26:21 CET
Thank you for the report, and your diagnosis. Start at the end: > At the end, I'm able to use the command butter Where did this come from? Just curious. > Is it possible to give this "under" packages (octave-control, > octave-signal) as RPM instead having to compile it The site makes it clear that if you want to use these modules, you do what you did: "pkg install -forge <package name>" ; that is an Octave Forge pkg, not an rpm. So my guess answer to your question is 'No'. https://www.gnu.org/software/octave/ [an excellent site] Octave Forge Octave Forge is a central location for development of packages for GNU Octave, ...To install a package, use the pkg command from the Octave prompt by typing: pkg install -forge package_name pkg load package_name https://octave.sourceforge.io/ Individual package installation You can find the list of packages by clicking on the Packages link at the top. To install a package, use the pkg command from the Octave prompt by typing: pkg install -forge package_name, where package_name is the name of the package you want to install. https://octave.sourceforge.io/packages.php nicely lists available Forge Packages. -------------------------------------- > >> pkg install -forge signal > error: the following dependencies were unsatisfied: > signal needs control >= 2.4 [Both Octave pkgs]. Clear enough; all inside Octave, not Mageia's affair. > >> pkg install -forge control > pkg: unable to find the mkoctfile command, Octave installation is > incomplete This *does* look our affair. Repeating & confirming your: $ urpmf mkoctfile | sort -u octave-devel:/usr/bin/mkoctfile octave-devel:/usr/bin/mkoctfile-5.1.0 octave-devel:/usr/share/man/man1/mkoctfile.1.xz octave-doc:/usr/share/doc/octave-doc/interpreter/octave.html/XREFmkoctfile.html octave:/usr/share/octave/5.1.0/m/miscellaneous/mkoctfile.m shows that basic 'octave' provides just the last item (whatever it is), the other 3 from the -devel pkg: $ urpmq -l octave-devel | grep mkoctfile | sort -u /usr/bin/mkoctfile /usr/bin/mkoctfile-5.1.0 /usr/share/man/man1/mkoctfile.1.xz If mkoctfile really is a basic requirement to use Octave, it does indeed look as if the whole lot (octave & -devel) could be in one pkg; and while it is not, octave-devel should be a requirement of octave. Agree with your proposition! --- Assigning this globally, CC'ing Chris as having committed 'octave' several times. Assignee:
bugsquad =>
pkg-bugs I am not sure to understand the problem, mkoctfile.m is the source code of mkoctfile binary, it is provided for information only as far as I see. Maybe its place should be with the devel file indeed, but that won't change anything. The octave package itself contains the octave binary and environment allowing you to use octave as it is. When you develop, download, install additional packages for octave, that means you compile them. As any other packages, for this to work, you need the development files which are in octave-devel. So there is no issue here, it seems to me that everything works as it should. Cheers. Resolution:
(none) =>
WONTFIX |