Pierre Labastie wrote:
Le 30/10/2014 15:45, David Brodie a écrit :
On 29/10/14 22:48, Bruce Dubbs wrote:
Pierre Labastie wrote:
The version checks in jhalfs are fragile, because they depend on an
expected
behavior or the excutable. Actually, the tested version of wget is 1.0.0,
which does not exist, but is lower than any known version: the aim is
just to
test wget presence. Any version will do.
Of course, if Suse strips the version number, this does not work. I
guess you
can answer c<ret> if you are sure that you have wget. But I agree it
is annoying.
I'll try a VM machine with Suse tomorrow (which version actually?)
I believe it was openSUSE-12.3-KDE-Live-x86_64.iso.
Curious, I've just run up openSUSE-13.1 x86-64, which was *installed* from a
live CD, and wget --version gives:
GNU Wget 1.14 build on linux-gnu.
I can confirm that "wget --version" from the 12.3 live CD strips the version
part... Installing now.
End of installation:
It is the same on an installed (from live CD) system. I tried to desinstall
and reinstall wget: still strips the version part. Looks like a bug in this
version of SUSE?
I would think so. Perhaps jhalfs should just test for the presence of
wget and forget about the version. In my use case, I already have the
files downloaded, so I don't need wget for jhalfs at all.
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
