Re: Interesting paths when building octave 7.1.0.

On 4/10/22 16:02, Dmitri A. Sergatskov wrote:
WARNING: This message has originated from an External Source. This may be a phishing expedition that can result in unauthorized access to our IT System. Please use proper judgment and caution when opening attachments, clicking links, or responding to this email.

On Sun, Apr 10, 2022 at 4:43 PM Montgomery-Smith, Stephen <[email protected]<mailto:[email protected]>> wrote:
I maintain the octave package for FreeBSD.  I recently upgraded to
octave 7.1.0.  I found something rather interesting - it creates a bunch
of files whose names are:

/usr/local/bin/share/octave/7.1.0/test/fixed/xxxxxxxxxx/tbcover.m

where the xxxxxxxx is derived from the directory in which the build
takes place.  In my case, xxxxxxxx would be
usr/ports/math/octave/work/octave-7.1.0.

This makes it very difficult to create a package manifest listing all
the files, because the manifest will be different depending upon where
the build directory takes place.  My current solution is to simply
delete all these files after installation.

My questions:

1.  Can I delete the whole directory share/octave/7.1.0/test?  Or is it
used after the package is built?  If not, what is the purpose of these
tbcover.m files?

2.  Could the makefiles be changed in future versions of octave so that
these files are installed in a predictable place, just like they were in
previous versions of octave?

Thanks, Stephen




I can confirm this on linux and it looks like a bug to me. Could you make a bug report on savannah?

Dmitri.


I don't have an account on savannah.  Could you do the bug report for me?


----------
We are transitioning to a web based forum
for community help discussions at
https://octave.discourse.group/c/help