- binary-builders - NTG Mailing Lists

[Context] some changes in binary compilation
by Mojca Miklavec 05 May '09

05 May '09

Hello, I'm going to change some aspects of binary compilation in order to enable storing multiple versions of luatex. I have to watch out to make the changes more or less simultaneous. There has been a recent change/patch in pdftex, but assuming that Taco is not going to release the next version of LuaTeX or metapost in the next few days ... I just wanted to warn you that compiling the binaries until my next notice might fail if you start compiling in the wrong moment during transition. After that I will ask you to update build-binaries script to account for the changes. Mojca

1 2

[Context] TL repositories on contextgarden
by Mojca Miklavec 05 May '09

05 May '09

Hello Norbert, I finally arrived home (despite oversleeping the station in Wien it all turned out ok :) I'm reading your conversation from TL list (online, not subscribed as it was distracting me too much to read all the TeX-related lists). I noticed the problem of updates (apparently the version). I tried to set the version to 100000, but I made a typo, so it didn't help. Apparently the version in TL got update for whatever reason and I didn't put the repository into cron (probably I should, I was just waiting for the patch). I'm thinking about the following: - if ConTeXt version gets updated, call the script that only updates ConTeXt - if repository with binaries updates, run the script and update all the luatex-s I know that I should try this before asking, but just curious: if I run the script and version gets updated by one - will the clients compare md5sum or will the clients update just because the version has been updated by one? In any case it probably makes sense if there have been any updates before unconditionally increasing the version by one. I will most probably decide to make sure that the version gets updated to at least 1000 above TL since users that updated from garden once probably don't intend their updates to be reverted next time when they update the rest of the packages without specifying garden repository explicitely. Assuming that I can parse the version of context and luatex before creating TL package - what's the most appropriate field/position to put the version information there? Thanks a lot, Mojca

2 2

[Context] solaris to be removed
by Mojca Miklavec 02 May '09

02 May '09

Hello, Most binaries for Solaris (intel and sparc) are outdated. I'm going to remove files for solaris from server unless someone is willing to catch up and send recent binaries. Mojca

1 0

[Context] Updating TL 2008
by Mojca Miklavec 29 Apr '09

29 Apr '09

Hello, Norbert generously contributed some code. We need to fix some bugs, but you may try http://wiki.contextgarden.net/ConTeXt_Minimals/TeX_Live at the moment it doesn't update automatically yet, I need to find a way to check if version has changed or not. Mojca

2 2

Re: [Context] --extras and --keep
by Mojca Miklavec 25 Apr '09

25 Apr '09

On Sat, Apr 25, 2009 at 16:15, Aditya Mahajan wrote: > On Sat, 25 Apr 2009, Mojca Miklavec wrote: > >> b) putting anything that's not in distribution to texmf-local > > Yes, that is always a good idea. Maybe the initial installtion should create > a texmf-local for the user. I just wanted to ask that. Hans, can you please also add if force then dir.mkdirs(format("%s/%s", texroot, "texmf-cache")) dir.mkdirs(format("%s/%s", texroot, "texmf-local")) end Thanks, Mojca

2 1

[Context] update before building & fixing some issues
by Mojca Miklavec 25 Apr '09

25 Apr '09

Hello, Just in case - please update the building script before executing it since location of metapost binary has changed. Taco - we had to re-add dvitomp binary a while ago for some reason I forgot. Is that file still needed and why (not)? One more thing: I'll try to fix a few issues in the minimals next week (the most important one would be sorting out which luatex binary to use and to enable choosing "experimental" version of luatex, but there are definitely more issues). I need to prepare a list, but I'll start concentrating on the issue next week. You may put your ideas on the wiki or to the tracker or just reply here. Mojca

4 9

Re: [Context] --extras and --keep
by Mojca Miklavec 25 Apr '09

25 Apr '09

On Sat, Apr 25, 2009 at 14:58, Aditya Mahajan wrote: > On Sat, 25 Apr 2009, Mojca Miklavec wrote: > >> Once I use --extras=t-something the module stays there even if I don't >> add the --keep flag. Does it behave differently on your machine? > > I get the same behaviour as you. I think that I had installed some modules > by hand, and those got wiped out, and it took me ages to figure out what > happened. I will correct the wiki. One needs to check what happens in case that one runs ./first-setup.sh --extras=t-something ./first-setup.sh --extras=t-somethingelse I would not be surprised if the first module was deleted (this needs to be checked and fixed). But in general I would suggest: a) putting --extras=whatever to the last line of first-setup.sh b) putting anything that's not in distribution to texmf-local > BTW, do you know why the new t-bib cannot be installed by first-setup? Most probably because there has never been a need for that until recently. I can add it to the repository, but I'm sceptic if it will work properly. rsync is somehow unpredictable if one provides two files with the same name. I would not be surprised if it took one file from context and the other file from the extra module. Feel free to test - bib is in repository now. Mojca

1 0

[Context] --extras and --keep
by Mojca Miklavec 25 Apr '09

25 Apr '09

Hello Aditya, I'm reading the instructions on http://wiki.contextgarden.net/ConTeXt_Minimals: "By default, first-setup.sh does a clean upgrade. This means that anything in the tex tree that is not requested is deleted. In particular, this means that if you are upgrading a installation with third party modules installed, but do not specify --extras=<module-name>, then the installed module will be deleted. One way to avoid this is to always specify the modules that you want while upgrading. An easier alternative is to upgrade using sh ./first-setup.sh --keep" Once I use --extras=t-something the module stays there even if I don't add the --keep flag. Does it behave differently on your machine? Here I get the report MTXrun | run: rsync -rpztlv --stats --delete contextgarden.net::'minimals/current/context/beta/ minimals/current/context/img/ minimals/current/modules/t-gnuplot/ minimals/current/modules/t-tikz/' '<path-to>/texmf-context' even without --extras switch. Mojca

1 0

Re: [Context] [NTG-context] texexec slow
by Taco Hoekwater 24 Apr '09

24 Apr '09

(Redirected to launchpad list) Mojca Miklavec wrote: > > How does pdftex building process decide which one to use in case that > both are installed? The process doesn't do anything explicit, the system's gcc install controls this automatically when you install 'libstdc++-static'. If your system is new enough to have libstdc++.so.6, that is what it will use. If the system is so old that it doesn't have libstdc++.so.6, only .5, then the static version of libstdc++ will automatically also have that version). Any packages with an explicit version number, like 'libstdc++5', are meant for backward compatibilty with older precompiled programs. Those will not be used by the compiler, and by the runtime link resolver. Best wishes, Taco

1 0

Re: [Context] no more pdftex for linux-64
by Mojca Miklavec 24 Apr '09

24 Apr '09

On Wed, Apr 8, 2009 at 11:31, The Thanh Han wrote: > Hi, > > the build script should be updated > after syncing with TL. Will do that soon. Thanks a lot. Mojca

3 4