Le mercredi 05 février 2014 à 11:29 +0100, Sébastien Villemot a écrit : > [ replying to the Debian Octave Group list ] > > Le jeudi 23 janvier 2014 à 13:34 +0100, Thomas Weber a écrit : > > On Wed, Jan 22, 2014 at 03:13:50PM +0100, c. wrote: > > > > the other I don't remember. The change in value I do > > > > not remember - it doesn't matter however. I am not an expert in whatever > > > > domain the constants are used, so I assume that every change might be > > > > important to someone working in a specific domain. > > > > > > That's why I whish Debian packagers would let pkg.m work > > > so Octave users could just decide for themselves. > > > > We share that wish. Have you a fix for > > http://savannah.gnu.org/bugs/?32049 ? > > As a reminder, this issue is also tracked in Debian as #536839 and > #672651. > > If I understand correctly the issue, the problem comes from the "pkg > prefix" line that we put in /etc/octave.conf. It prevents users from > installing packages in their home directory with "pkg install -local". > > My impression is that this "pkg prefix" line in /etc/octave.conf > currently serves no useful purpose (it may be a remnant from the time > when there were 2 different octave versions in the archive). The default > global location hardcoded in pkg.m is already the right one. The only > change that may be needed would be to force the "-global" flag when > running "pkg install" from octave-pkg-dev. > > I think packages in the global location would still be detected by > octave, because of the "pkg global_list" line in /etc/octave.conf. > > Am I missing something? (I admit I did not test that my proposition > works) I pushed that change to git. I could verify that building and running of Forge packages still work. Please test if you have the time. -- .''`. Sébastien Villemot : :' : Debian Developer `. `' http://www.dynare.org/sebastien `- GPG Key: 4096R/381A7594
Attachment:
signature.asc
Description: This is a digitally signed message part