Hi all, I have just pushed the beta-0.85.0 on the svn server. Please compile, test and report any problem. As usual, the new beta is "cold" but not "frozen", so we can still fixed something. It would be nice to have the binaries (at least) for osx, linux, windows and freebsd in the garden, so we will wait for them before the formal announcement. Hans, Taco, Luigi (in this order :-) )
On Thu, Nov 19, 2015 at 3:46 PM, luigi scarso
Hi all, I have just pushed the beta-0.85.0 on the svn server. Please compile, test and report any problem. As usual, the new beta is "cold" but not "frozen", so we can still fixed something. It would be nice to have the binaries (at least) for osx, linux, windows and freebsd in the garden, so we will wait for them before the formal announcement.
Hans, Taco, Luigi (in this order :-) )
Of course Hans has found a bug with tikz...fixed in rev. 5554 (which means that another build is necessary, sorry ) -- luigi
Hi,
I built and committed binaries for linux and freebsd, 64bit and 32bit.
Alan
On Thu, 19 Nov 2015 15:46:12 +0100
luigi scarso
Hi all, I have just pushed the beta-0.85.0 on the svn server. Please compile, test and report any problem. As usual, the new beta is "cold" but not "frozen", so we can still fixed something. It would be nice to have the binaries (at least) for osx, linux, windows and freebsd in the garden, so we will wait for them before the formal announcement.
Hans, Taco, Luigi (in this order :-) )
-- Alan Braslau CEA DSM-IRAMIS-SPEC CNRS UMR 3680 Orme des Merisiers 91191 Gif-sur-Yvette cedex FRANCE tel: +33 1 69 08 73 15 fax: +33 1 69 08 87 86 mailto:alan.braslau@cea.fr
On 19 November 2015 at 19:12, Alan BRASLAU wrote:
Hi,
I built and committed binaries for linux and freebsd, 64bit and 32bit.
It looks like the sources contained r5551 when you synced, so according to Luigi you will most likely need to repeat the process :( The mac binaries are being compiled right now thanks to Hans. Mojca
On 11/19/2015 8:09 PM, Mojca Miklavec wrote:
On 19 November 2015 at 19:12, Alan BRASLAU wrote:
Hi,
I built and committed binaries for linux and freebsd, 64bit and 32bit.
It looks like the sources contained r5551 when you synced, so according to Luigi you will most likely need to repeat the process :(
The mac binaries are being compiled right now thanks to Hans.
i uploaded the beta that is needed for these binaries ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Thu, Nov 19, 2015 at 8:12 PM, Hans Hagen
On 11/19/2015 8:09 PM, Mojca Miklavec wrote:
On 19 November 2015 at 19:12, Alan BRASLAU wrote:
Hi,
I built and committed binaries for linux and freebsd, 64bit and 32bit.
It looks like the sources contained r5551 when you synced, so according to Luigi you will most likely need to repeat the process :(
The mac binaries are being compiled right now thanks to Hans.
i uploaded the beta that is needed for these binaries
----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
$ luatex --version This is LuaTeX, Version beta-0.85.0 (TeX Live 2016/dev) (rev 5550) rev 5550 is hardcoded, ie it doesn't strictly depends on the current rev. of beta. Given that the only source for beta is tags/beta-0.85.0 in the end this "(rev 5550)" is "just a number". When we will announce the beta, the code will be frozen in the svn, and of course it is associated with a revision number too, which usually is greater. So, to keep the things simple, we fix the rev. to that one of the trunk and we tolerate a bit of delta. The most important things in the banner are "/dev", which means not from a stable TeXLive and "(rev. 5550)" which means that it's a beta, ie frozen. For example, for trunk we have $ luatex --version This is LuaTeX, Version beta-0.85.0 (TeX Live 2016/dev) and for TEXLive 2015 # luatex --version This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238) i.e. "stable TL, code from beta frozen" which is the what we tend to do. If there is a patch to commit after the announcement, then we will make 0.85.0.1 (or 0.85.1, it depends if we also add something new o rewrite something) because as I hev said, after an announcement the code of a beta is frozen. -- luigi
OK Luigi,
but wouldn't it be simple to "hardcode" the real revision number string
into the source automatically?
Alan
On Thu, 19 Nov 2015 20:44:18 +0100
luigi scarso
On Thu, Nov 19, 2015 at 8:12 PM, Hans Hagen
wrote: On 11/19/2015 8:09 PM, Mojca Miklavec wrote:
On 19 November 2015 at 19:12, Alan BRASLAU wrote:
Hi,
I built and committed binaries for linux and freebsd, 64bit and 32bit.
It looks like the sources contained r5551 when you synced, so according to Luigi you will most likely need to repeat the process :(
The mac binaries are being compiled right now thanks to Hans.
i uploaded the beta that is needed for these binaries
----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
$ luatex --version This is LuaTeX, Version beta-0.85.0 (TeX Live 2016/dev) (rev 5550)
rev 5550 is hardcoded, ie it doesn't strictly depends on the current rev. of beta. Given that the only source for beta is tags/beta-0.85.0 in the end this "(rev 5550)" is "just a number". When we will announce the beta, the code will be frozen in the svn, and of course it is associated with a revision number too, which usually is greater. So, to keep the things simple, we fix the rev. to that one of the trunk and we tolerate a bit of delta.
The most important things in the banner are "/dev", which means not from a stable TeXLive and "(rev. 5550)" which means that it's a beta, ie frozen.
For example, for trunk we have
$ luatex --version This is LuaTeX, Version beta-0.85.0 (TeX Live 2016/dev)
and for TEXLive 2015 # luatex --version This is LuaTeX, Version beta-0.80.0 (TeX Live 2015) (rev 5238) i.e. "stable TL, code from beta frozen" which is the what we tend to do.
If there is a patch to commit after the announcement, then we will make 0.85.0.1 (or 0.85.1, it depends if we also add something new o rewrite something) because as I hev said, after an announcement the code of a beta is frozen.
-- Alan Braslau CEA DSM-IRAMIS-SPEC CNRS UMR 3680 Orme des Merisiers 91191 Gif-sur-Yvette cedex FRANCE tel: +33 1 69 08 73 15 fax: +33 1 69 08 87 86 mailto:alan.braslau@cea.fr
OK Luigi, but wouldn't it be simple to "hardcode" the real revision number string into the source automatically?
Alan
If a user does a check out, ie svn checkout --username anonsvn https://foundry.supelec.fr/svn/luatex/trunk
On Thu, Nov 19, 2015 at 8:47 PM, Alan BRASLAU
On 19 November 2015 at 20:47, Alan BRASLAU wrote:
OK Luigi, but wouldn't it be simple to "hardcode" the real revision number string into the source automatically?
On the server I run texk/web2c/luatexdir/getluatexsvnversion.sh which correctly sets the version in texk/web2c/luatexdir/luatex_svnversion.h but there seems to be texk/web2c/luatexdir/luatex.c:int luatex_svn = 5550; that most probably overrides the other value. I don't particularly like the current solution. Mojca
Of course... I was waiting for the garden to sync the updated sources.
Now done, but please note that something is funny with the revision numbers
(is this a problem with the luatex source that does not encode its own revision number correctly?)
$ cat src/VERSIONS
metapost: 1.999
xetex: 0.9999.3
luatex: beta-0.85.0 r5554
luatex_trunk: r5553
$ bin/amd64-freebsd/luatex/luatex --version
This is LuaTeX, Version beta-0.85.0 (TeX Live 2016/dev) (rev 5550)
Alan
On Thu, 19 Nov 2015 20:09:42 +0100
Mojca Miklavec
On 19 November 2015 at 19:12, Alan BRASLAU wrote:
Hi,
I built and committed binaries for linux and freebsd, 64bit and 32bit.
It looks like the sources contained r5551 when you synced, so according to Luigi you will most likely need to repeat the process :(
The mac binaries are being compiled right now thanks to Hans.
Mojca
-- Alan Braslau CEA DSM-IRAMIS-SPEC CNRS UMR 3680 Orme des Merisiers 91191 Gif-sur-Yvette cedex FRANCE tel: +33 1 69 08 73 15 fax: +33 1 69 08 87 86 mailto:alan.braslau@cea.fr
On 19.11.2015 20:43, Alan BRASLAU wrote:
Of course... I was waiting for the garden to sync the updated sources.
Now done, but please note that something is funny with the revision numbers (is this a problem with the luatex source that does not encode its own revision number correctly?)
$ cat src/VERSIONS metapost: 1.999 xetex: 0.9999.3 luatex: beta-0.85.0 r5554 luatex_trunk: r5553 $ bin/amd64-freebsd/luatex/luatex --version This is LuaTeX, Version beta-0.85.0 (TeX Live 2016/dev) (rev 5550)
Comitted for powerpc-linux, with the same number as Alan got, so all is good, it appears... Thomas
ls> Date: Thu, 19 Nov 2015 15:46:12 +0100
ls> From: luigi scarso
On 19 November 2015 at 23:59, Boris Veytsman wrote:
ls> Date: Thu, 19 Nov 2015 15:46:12 +0100 ls> From: luigi scarso
ls> Hi all, ls> I have just pushed the beta-0.85.0 on the svn server. ls> Please compile, test and report any problem.
done for armel-linux (hopefully it was the latest version)
Thank you. This completes the cycle. The only binaries we are missing now are armhf-linux (which I can make with my raspberry). I keep forgetting the difference all the time and we don't properly support distinction between them. We should probably have some short explanation about the difference on the TeX Live page and we should improve the detection code in the future. Mojca
MM> Date: Fri, 20 Nov 2015 19:34:46 +0100
MM> From: Mojca Miklavec
participants (6)
-
Alan BRASLAU
-
Boris Veytsman
-
Hans Hagen
-
luigi scarso
-
Mojca Miklavec
-
Thomas A. Schmitz