I have just installed 110.43 from ~x86 and ... It compiled and the thing works, but it proudly presents itself as ver.042: wasowski@klimt wasowski $ sml Standard ML of New Jersey v110.42 [FLINT v1.5], October 16, 2002 - If you firstly download the filenames using .42 ebuild (using --fetchonly, or simply by failing to build .42 with gcc 3.3, which is probably what happens to most people), then you have tgz files of .42 in distfiles and the .43 ebuild does not download the new files. The .42 sources are happy with the new patches, so everything goes seemlessly only user gets a wrong version installed. I checked that this is not the bug in smlnj implementation. The files on the official website have the right (.43) version in sources. Then I found that digest-smlnj-110.43 and digest-smlnj-110.42 in portage are identical... No doubt that this will be happy with files from 0.42. Moreover anybody installing .43 a fresh is bound to file on MD5 check [which is a moderately serious problem, as it cannot be solved without hacking in the tree]. The digest has to be recomputed. A side remark: I do not think we should mark this "SML/NJ working versions" stable as they are not considered stable releases by developers of the package. As to my knowledge the last stable release was 110.0.7, not available in portage at all.
*** Bug 43017 has been marked as a duplicate of this bug. ***
I do not understand portage well enough to make a proper comment, but I would like to add that apart from wrong digest there is something wrong with mirrors. It seems that emerge downloads files from gentoo mirror (not from smlnj website). Regardless which ebuild I use I get the same files from http://gentoo.oregonstate.edu/distfiles/. Can anybody look into this? Or give me a hint what to change in the ebuild. Presently there seems impossible to install any other version of smlnj than 110.42 (which is a slightly outdated working version, neither stable nor bleeding edge). While doing this I also discovered that the ftp site of smlnj does not work any more. I will attach an ebuild for .43 with new URIs. Please use it, instead of the CVS copy if you want to change anything. I have not change anything besides the homepage and URIs.
Created attachment 26425 [details] smlnj-110.43-r1.ebuild with URIs updated to new project websites This new ebuild has correct URIs. Note that it does *not* solve the problem of this bug for me, but the fix is related as downloading of proper sources will not work without proper download locations, so it is a good starting point.
The updated URI's are not right either, as the packages are on smlnj.cs.uchicago.edu. To fix the problem, we need to put renamed packages on gentoo mirrors and go from there. I have smlnj-110.{42,43} packages on my dev account now, and updated (and working) ebuilds using mirror:// i can commit. What do you think
I finally removed smlnj-110.{42,43} as they do not build working versions, but i added 110.45 which does, and also 110.0.7. These two ebuilds use the mirror:// mechanisms. Mirrors should get populated with the corresponding files in the next hours.
