December 2008 - binary-builders

[Context] [Bug 265107] [NEW] Add pgfplots
by Mojca Miklavec 28 Jan '09

28 Jan '09

Public bug reported: http://sourceforge.net/project/showfiles.php?group_id=224188 ** Affects: context Importance: Undecided Status: New ** Tags: modules -- Add pgfplots https://bugs.launchpad.net/bugs/265107 You received this bug notification because you are a member of ConTeXt distribution team, which is the registrant for ConTeXt distribution. Status in ConTeXt distribution: New Bug description: http://sourceforge.net/project/showfiles.php?group_id=224188

1 3

[Context] test files
by Mojca Miklavec 30 Dec '08

30 Dec '08

Hello, I have created a few files to present some idea about test repository for ConTeXt. Test files should answer several questions, among others: - Do test documents compile? - Do they generate correct result (in comparison to some older distribution)? The second problem is slightly more complex since it requires parallel installations of ConTeXt and bitmap comparisons, but the first part should be relatively easy to implement. The idea is to check if formats can be generated at all, do some basic tests, do some extensive tests by trying to load all the possible fonts that are supposed to be part of dstribution (font names change over time, ...), See http://svn.contextgarden.net/minimals/test/compile (or README one folder up). The idea is to run mtxrun --script test inside that folder. It doesn't work yet and I think that I got it wrong the first time (a simple lua table is not enough to offer enough flexibility to do the testing - I would rather put a simple lua script into each folder, not only table, using some common functions defined in "master" file mtx-test.lua), but just to start some brainstorming. One thing that would be nice to add would be some tagging, so that one could run only some tests like font tests (or skip the font tests) for example ... Mojca

3 2

Re: [Context] ConTeXt minimals for FreeBSD AMD64
by Mojca Miklavec 27 Dec '08

27 Dec '08

>> One more question for the other two FreeBSD-ers: we now have >> i*86) platform="freebsd" ;; >> x86_64) platform="freebsd" ;; >> amd64) platform="freebsd-amd64" ;; >> Where does x86_64 belong? To the first or to the second group? > > The term x86_64 is a synonym for amd64. It is common in the linux > world, but not used for FreeBSD. Here are all potential platforms > supported by FreeBSD: > > http://www.freebsd.org/releases/7.0R/hardware.html#PROC Thanks for the list. Just one question: I have found the thread mentioned below. What does x86_64 do there? I have some faint memories that Yue has been complaining that "if architecture == x86_64" was returning true on FreeBSD, but I may be wrong. I can delete x86_64 or just make it a synonym for amd64. Mojca On Sun, Mar 16, 2008 at 7:44 PM, Michael Krauss wrote: > On 15/03/08, Randy Au wrote: >> PATH="/home/agilis/texlive-branch/branch2007/Master/bin/x86_64-freebsd8:...." > > Thank you, that does the trick.

1 0

Re: [Context] ConTeXt minimals for FreeBSD AMD64
by Mojca Miklavec 27 Dec '08

27 Dec '08

On Sat, Dec 27, 2008 at 2:12 PM, Michael Krauss wrote: > On 27/12/08 "Mojca Miklavec" wrote: >> >> Can you please check if the minimals work OK now? > > No, first-boot.sh downloads some files but get stuck in > bin/mtx-update.lua: > > to /usr/local/texlive/2008/bin/amd64-freebsd MtxRun | variable -> uses TeX Live instead of minimals. Sorry, I always forget to set executable flag when people send me binaries per email. Can you please try one more time? Mojca

1 0

Re: [Context] ConTeXt minimals for FreeBSD AMD64
by Mojca Miklavec 27 Dec '08

27 Dec '08

On Fri, Dec 26, 2008 at 11:12 PM, Michael Krauss wrote: > Hello Mojca, > > on Christmas I migrated my second machine from FreeBSD i386 to > FreeBSD AMD64. Till now there are no context minimals for AMD64. Can you please check if the minimals work OK now? > But > unlike a month ago on OpenSolaris, I was able to build the binaries > without problems: Taco has fixed quite some compilation bugs recently thanks to all the people who reported all the possible and impossible compilation issues on almost every single platform that existed :) :) (So I guess that we lost you for Open Solaris now? :) One more question for the other two FreeBSD-ers: we now have i*86) platform="freebsd" ;; x86_64) platform="freebsd" ;; amd64) platform="freebsd-amd64" ;; Where does x86_64 belong? To the first or to the second group? Should freebsd alone be renamed or is it ok to leave only freebsd there? > So at least for FreeBSD AMD64 I can provide binaries through subversion > on a regular basis. Just send me the desired username/password. Mojca PS: Hans, can you please update mtx-update.lua (["freebsd-amd64"] = "freebsd-amd64") and mtxrun.lua? elseif name == "freebsd" then local architecture = os.arch() if architecture:find("amd64") then return "freebsd-amd64" else --if architecture == 'i386' or 'x86_64': not sure about x86_64 return "freebsd" end end

1 0

[Context] switching to the next luatex "generation"
by Mojca Miklavec 16 Dec '08

16 Dec '08

Hello, Hans sent me a patch to fix behaviour of the latest LuaTeX (that I still need to test). Should we wait? Should we patch the otf files and switch to the latest luatex? (linux-ppc and solaris would lag behind until we get the new binaries, but that doesn't seem too critical) Should I wait for the "big package" of changes? The main problem is now also the "current" branch of ConTeXt. If we switch to the new LuaTeX, then current ConTeXt will stop working properly with mkiv. On the other hand: I'm still looking for a better way to deal with such incompatibilities. - There is a way to switch to an older ConTeXt, but that doesn't really help since LuaTeX changes too fast. - There is experimental branch that is not fully functional (but could be made functional, I'm only not sure what binaries to commit there). Some ideas or discussions would be welcome. - One could misuse a different server or a different subdomain to put "more experimental stuff" there and then only sync if there have been no problems observed for more than three days - One could put the whole texmf-whatever tree with all the modules under version control; one looses the possibility to choose modules, but at least the option to roll back in time would be there Any suggestion welcome. Mojca

3 3

Re: [Context] Test files
by Mojca Miklavec 06 Dec '08

06 Dec '08

On Thu, Dec 4, 2008 at 11:12 PM, Diego Depaoli wrote: > 2008/12/4 Mojca Miklavec: >> Hello, >> >> Here's a suggestion from Hans ... The idea about including some sample >> documents when installing minimals sounds OK to me, but I would add >> some "my first document"-like files to warm up the users, and maybe >> some more files for testing. In that case it would make sense to have >> some repository with files somewhere. > Include test files in minimals sounds useful, but hard to maintain. > You/we may verify than they: > a) work > b) work with pdftex engine > c) work with xetex engine > ..... > unless we include trivial files, but that sounds useless. > A wiki page 'download test files' can be better maintained/improved by users. > > Instead, what you think about a repository with tested working typescripts? > A lot of messages in list are fonts-related. > We could create a page with: > fontname, license, url, url-typescript-download. You just gave me some ideas, but maybe the discussion should move to ntg-context. If I "forget" to write something about that to the main list within two weeks, please remind me. My idea would be to: - add a --test and --demo switch to mtx-update - it would sync some repository that we or users can create (but there should be one moderator) - one would also need to add some rules for building files (lua tables): some test files only make sense for luatex, some only for pdftex, some *should* fail - one could take a look at what Sanjoy did a while ago and check what's on the current test repository - demo would be for newbies to give them some short examples & ideas where to start - test could include a short and an extensive test suite to check if everything still works fine Mojca PS: sorry, sent twice since I forgot to add the mailing list to the list of recipients

1 0

[Context] Test files
by Mojca Miklavec 04 Dec '08

04 Dec '08

Hello, Here's a suggestion from Hans ... The idea about including some sample documents when installing minimals sounds OK to me, but I would add some "my first document"-like files to warm up the users, and maybe some more files for testing. In that case it would make sense to have some repository with files somewhere. Looking for ideas ... (maybe such a mail could go to the main mailing list) Mojca ---------- Forwarded message ---------- From: Hans Hagen <pragma(a)wxs.nl> Date: Thu, Dec 4, 2008 at 11:45 AM Subject: test file To: Mojca Miklavec <mojca.miklavec.lists(a)gmail.com> Hi how about an extra path : bin tex test i will add context-test.tex to the distribution and we can then have a copy in test so that users can check their system Hans

1 0

[Context] Important: ConTeXt Minimals and --delete/--keep switch
by Mojca Miklavec 01 Dec '08

01 Dec '08

Hello, This is a rather important notice for users of ConTeXt minimals. You might want to add --keep to ./first-setup.sh There are some options for which I'm not sure if they should be enabled by default or not. The script (mtx-update.lua and consequently the simplistic ./first-setup.sh script) provides two switches: --keep and --delete. The --delete switch deletes all the files that are not part of distribution. The --keep switch doesn't care about those files (that have been remove from distribution or that you added) and leaves them where they are. Your own files should go to texmf-local that update doesn't touch at all. Now the important info: if you want your files to be kept, you should use the --keep switch in ./first-setup.sh. --delete has been misfunctional for a while, and maybe it should not be kept as the default option. But as it stands now, it is the default. Recently there has been a new option added (--extras=list,of,context,modules), but I would like the option to be renamed to something more self-explanatory than --extras= (--modules= for example). You can test if fetching modules works OK, but I would like to rename the option. Mojca (Maybe we should add --cvs-exclude rule to rsync to prevent deleting kpathsea files and formats.)

2 2

[Context] Minimals
by Taco Hoekwater 01 Dec '08

01 Dec '08

Hi Mojca, I have added a link to the Minimals on the wiki front page, hope you don't mind.

3 4