ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Robert Krug <destiny6@mac.com>
To: ntg-context@ntg.nl
Subject: OpenBSD install broken
Date: Fri, 20 Sep 2019 23:02:58 -0000	[thread overview]
Message-ID: <327ab547-be27-47c3-b2fb-796ca42a2d13@me.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2286 bytes --]

Greetings,



First, thanks for all the wonderful work on context.



Now, to the reason for this note. I recently tries to install context on an OpenBSD 6.5 AMD64

system, but the install failed. Thanks to some helpful emails in the archives from 2017 and 2018,

I was able to get this working by editing mtxrun and mtx-update.sh.



I include what I did below.



Thanks again,

Robert



1) Do the usual:

  mkdir context && cd context
  rsync -ptv rsync://contextgarden.net/standalone/setup/first-setup.sh .
  ./first-setup.sh

This will silently fail, because
bin/mtx-update.lua
bin/mtxrun
do not recognize openbsd.

2) Edit bin/mtxrun:

We need to define a "good" version of resolvers.platform(t,k)
At line 4049, there is a default definition. Replace it with:

 function resolvers.platform(t,k)
  local platform="openbsd6.5-amd64"
  os.setenv("MTX_PLATFORM",platform)
  os.platform=platform
  return platform
 end

3) Edit bin/mtx-update:

3a) In the table update.platforms add an entry for openbsd:

    ["openbsd6.5-amd64"]  = "openbsd6.5-amd64",

I put this at line 198, after the entries for freebsd.

3b) In the function update.synchronize()

replace line 282:

    local platforms    = states.get('platforms') or { }

with:

    local platforms    = states.get('platforms') or {"openbsd6.5-amd64" }

3c) At the very start of local function add_collection(collection,platform)
line 417, add:

            platform = "openbsd6.5-amd64"

Maybe something is broken on my system or these last two aren't
really needed, but this is what I did,

4) Edit first-setup.sh:

To avoid overwriting the files we just edited, comment out line 146:

# rsync -rlptv rsync://contextgarden.net/minimals/setup/$platform/bin .

This may interfere with future updates.

5) Install for real this time:

  ./first-setup.sh --modules=all

6) Finally, the setuptex script gives me an error message:

  megaera$ . /home/<name>/Context/tex/setuptex
  /bin/ksh: /home/<name>/Context/tex/setuptex[163]: ${.sh.file}": bad substitution

but it is not hard to set the path correctly:

  PATH=$PATH\:/home/<name>/Context/tex/texmf-openbsd6.5-amd64/bin ; export PATH




[-- Attachment #1.2.1: Type: text/html, Size: 3069 bytes --]

[-- Attachment #2: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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:[~2019-09-20 23:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-20 23:02 Robert Krug [this message]
2019-09-21 11:22 ` Mojca Miklavec
2019-09-23 20:38 Robert Krug
2019-10-08 17:24 Damien Thiriet

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=327ab547-be27-47c3-b2fb-796ca42a2d13@me.com \
    --to=destiny6@mac.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).