[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[mxe-octave:dev] default-octave on hydra site
From: |
Tatsuro MATSUOKA |
Subject: |
[mxe-octave:dev] default-octave on hydra site |
Date: |
Sat, 23 Jul 2016 15:55:59 +0900 (JST) |
If mxe-octave is configured with --enable-octave=default, mxe-octave is set to
build default branched source.
If one did not make tar ball by oneself, the mxe-octave will download default
branch source from the hydra site
http://hydra.nixos.org/job/gnu/octave-default/tarball/latest/download
However, this tar ball has two demerits:
1. It is not the latest. (Some delays always happen.)
2. Contents of the file HD-ID is "unknown" and ChangeLog is empty so that
one cannot know to which commit is applied to the source tree.
Of course, as is written in the wiki about mxe build,
http://wiki.octave.org/Windows_Installer#Step_2:_To_build_your_first_Octave-for_Windows_development_version:
It is better to build octave on Unix family (linux etcs.) and make tar ball by
make dist.
The tar ball using this procedure has not unknown HD-ID and not empty ChangeLog.
Perhaps the procedure that the mxe-octave downloads tar ball
from hydra site when octave-x.x.x+.tar.gz does not exist in the pkg directory
is considered to be users' convenient.
However, demerit is not so small, I think.
In my opinion, it is better that use of tarball from hydra site will be
optional.
Tatsuro
- [mxe-octave:dev] default-octave on hydra site,
Tatsuro MATSUOKA <=