Bug 488534

Summary:	=app-portage/g-octave-0.4.1 - Fix *.oct installation path.
Product:	Gentoo Linux	Reporter:	Fabio Rossi <rossi.f>
Component:	Current packages	Assignee:	Rafael Martins (RETIRED) <rafaelmartins>
Status:	RESOLVED FIXED
Severity:	normal	CC:	raphexion, sci-mathematics
Priority:	Normal	Keywords:	PATCH
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	g-octave-0.4.1-fix-Makefile.patch

Description Fabio Rossi 2013-10-18 21:54:00 UTC

Created attachment 361272 [details, diff]
g-octave-0.4.1-fix-Makefile.patch

g-octave uses a Makefile from upstream in its g-octave.eclass for the installation of the packages. What happens is that *.oct file are installed in wrong locations which are not automatically included by pkg("load", "auto") during octave startup. The result is that a package using an external *.oct will not work correctly.

The problem is located in the Makefile which contains an error. I have already reported in http://savannah.gnu.org/bugs/?39045 but upstream is not interested in fixing it because no package uses anymore that file. As g-octave is using that file I strongly suggest to include a fix in portage.

The proposed patch here attached is quite simple and it would solve problems like the one reported in #454632.

Comment 1 Rafael Martins (RETIRED) gentoo-dev

2013-10-19 21:03:24 UTC

+*g-octave-0.4.1-r4 (19 Oct 2013)
+
+  19 Oct 2013; Rafael G. Martins <rafaelmartins@gentoo.org>
+  +files/g-octave-0.4.1-fix-Makefile.patch, +g-octave-0.4.1-r4.ebuild,
+  -g-octave-0.4.1-r3.ebuild:
+  Fix .oct installation path. Thanks to Fabio Rossi (bug #488534).
+

Can you please submit your patch through git to https://github.com/rafaelmartins/g-octave ?

Thanks

Comment 2 Fabio Rossi 2013-10-19 22:05:29 UTC

(In reply to Rafael G. Martins from comment #1)

> Can you please submit your patch through git to
> https://github.com/rafaelmartins/g-octave ?
> 
> Thanks

Done, thanks.

Comment 3 Fabio Rossi 2013-10-20 00:03:40 UTC

*** Bug 454632 has been marked as a duplicate of this bug. ***