ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: TeXLive and ConTeXt
Date: Wed, 6 Jun 2018 20:37:35 +0200	[thread overview]
Message-ID: <CA35B8D8-B59D-401E-BB31-610CDF3DF68B@gmail.com> (raw)
In-Reply-To: <nycvar.YAK.7.76.44.1806061109221.21710@ervasbepr.pvz.zptvyy.pn>

Hi Aditya,

Your experiment confirms what I experienced last week with various types of operating systems, and today on my Mac with MacTeX 2018, which is just an installer of TL2018 dedicated to MacOS.

Best regards: OK

> On 6 Jun 2018, at 17:20, Aditya Mahajan <adityam@umich.edu> wrote:
> 
> Hi Otared,
> 
> On Wed, 6 Jun 2018, Otared Kavian wrote:
> 
>> I don't know to whom I should write to have ConTeXt enabled in TeXLive when one installs it: can anyone give me a hint?
> 
> I haven't used context that comes with texlive so I tried doing so on a new computer (which means that there were no left overs from previous texlive installs). I am on archlinux. First, some sanity checks:
> 
> $whereis context
> context: /usr/bin/context
> 
> $pacman -Qo =context
> /usr/bin/context is owned by texlive-core 2017.46770-1
> 
> Now, I tried compiling a file:
> 
> $context test
> resolvers       | trees | analyzing 'home:texmf'
> mtx-context     | warning: no format found, forcing remake (commandline driven)
> resolvers       | resolving | configuration files already identified
> resolvers       | resolving | loading configuration file 'selfautodir:/share/texmf-dist/web2c/texmfcnf.lua'
> resolvers       | resolving |
> resolvers       | resolving | locating list of 'home:.texlive/texmf-config' (runtime) (tree:///home:.texlive/texmf-config)
> resolvers       | methods | resolving, method 'locators', how 'uri', handler 'tree', argument 'tree:///home:.texlive/texmf-config'
> resolvers       | trees | locator 'home:.texlive/texmf-config' not found
> resolvers       | resolving | locating list of 'home:texmf' (runtime) (tree:///home:texmf)
> resolvers       | methods | resolving, method 'locators', how 'uri', handler 'tree', argument 'tree:///home:texmf'
> resolvers       | trees | locator '/home/adityam/texmf' found
> resolvers       | resolving | hash 'home:texmf' appended
> resolvers       | resolving | locating list of '/etc/texmf' (cached)
> resolvers       | methods | resolving, method 'locators', how 'uri', handler 'file', argument '/etc/texmf'
> resolvers       | files | file locator '/etc/texmf' found as '/etc/texmf'
> resolvers       | resolving | locating list of '/var/lib/texmf' (cached)
> resolvers       | methods | resolving, method 'locators', how 'uri', handler 'file', argument '/var/lib/texmf'
> resolvers       | files | file locator '/var/lib/texmf' found as '/var/lib/texmf'
> resolvers       | resolving | locating list of 'selfautoparent:texmf-project' (cached)
> resolvers       | methods | resolving, method 'locators', how 'uri', handler 'file', argument 'selfautoparent:texmf-project'
> resolvers       | files | file locator 'selfautoparent:texmf-project' not found
> resolvers       | resolving | locating list of 'selfautoparent:texmf-fonts' (cached)
> resolvers       | methods | resolving, method 'locators', how 'uri', handler 'file', argument 'selfautoparent:texmf-fonts'
> resolvers       | files | file locator 'selfautoparent:texmf-fonts' not found
> resolvers       | resolving | locating list of '.' (cached)
> resolvers       | methods | resolving, method 'locators', how 'uri', handler 'file', argument '.'
> resolvers       | files | file locator '.' found as '.'
> resolvers       | resolving | locating list of 'selfautodir:share/texmf-dist' (cached)
> resolvers       | methods | resolving, method 'locators', how 'uri', handler 'file', argument 'selfautodir:share/texmf-dist'
> resolvers       | files | file locator 'selfautodir:share/texmf-dist' found as '/usr/share/texmf-dist'
> resolvers       | resolving |
> resolvers       | methods | resolving, method 'generators', how 'uri', handler 'file', argument 'home:texmf'
> resolvers       | expansions | using cached scan of path 'home:texmf', branch 'home:texmf'
> resolvers       | methods | resolving, method 'generators', how 'uri', handler 'file', argument '/etc/texmf'
> resolvers       | expansions | scanning path '/etc/texmf', branch '/etc/texmf'
> resolvers       | expansions | 14 files found on 11 directories with 2 uppercase remappings
> resolvers       | methods | resolving, method 'generators', how 'uri', handler 'file', argument '/var/lib/texmf'
> resolvers       | expansions | scanning path '/var/lib/texmf', branch '/var/lib/texmf'
> resolvers       | expansions | 86 files found on 21 directories with 1 uppercase remappings
> resolvers       | methods | resolving, method 'generators', how 'uri', handler 'file', argument '.'
> resolvers       | expansions | scanning path '.', branch '.'/usr/bin/mtxrun:253: cannot open ./systemd-private-55c5c02a6995423fa7b5ef0af16560b5-colord.service-GCWnsA/: Permission denied
> 
> which says that context could not find a format, so it tried to generate one, but none of the given directories were writable. I don't know why mtxrun is trying to write in a /systemd-private directory.
> 
> $ mtxrun --expand-var TEXMFCACHE
> /var/lib/texmf;home:.texlive/texmf-var
> 
> and the second directory is writable.
> 
> So, I can confirm that context that ships with texlive did not run out of the box on my computer. It would have been nice had texlive generated the context format (as it does for latex), so a user could have run context out of the box. Even if that is not the case, context does try to generate the format on its own and fails. I'll dig deeper into why that is happenign.
> 
> Please do keep in mind that this is texlive that ships with archlinux and not the one distributed by ctan. So, this could be a packaging error in arch.
> 
> Aditya
> 
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
> 
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
> archive  : https://bitbucket.org/phg/context-mirror/commits/
> wiki     : http://contextgarden.net
> ___________________________________________________________________________________

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2018-06-06 18:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06 14:54 Otared Kavian
2018-06-06 15:19 ` Taco Hoekwater
2018-06-06 18:35   ` Otared Kavian
2018-06-06 15:20 ` Aditya Mahajan
2018-06-06 18:37   ` Otared Kavian [this message]
2018-06-06 22:40     ` Taco Hoekwater
2018-06-07 12:35       ` Aditya Mahajan
2018-06-07 22:25       ` Hans Åberg
2018-06-14  8:58         ` Robert Zydenbos
2018-06-07 18:12   ` Aditya Mahajan
2018-06-06 17:15 ` Hans Hagen
2018-06-06 18:40   ` Otared Kavian
2018-06-07 12:53     ` Arthur Reutenauer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA35B8D8-B59D-401E-BB31-610CDF3DF68B@gmail.com \
    --to=otared@gmail.com \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).