ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Standalone
Date: Sat, 3 May 2014 13:35:28 +0200	[thread overview]
Message-ID: <CALBOmsafGWfefQsK91J06c85-_yErjkrqn+kjwJuWP8RAuYJOg@mail.gmail.com> (raw)
In-Reply-To: <20140301214206.2316@binki>

Hi,

I'm sending the reply with a tiny bit of delay ... but I would be
grateful for some testing of modifications I have done.

---------------------

It took me a while to actually understand the problem.

cygwin support has an interesting history:
- at first, no support
- then tried to setup the support by native cygwin binaries
- the original

On Sat, Mar 1, 2014 at 1:42 PM,   wrote:
> On my system I already have Cygwin.  I want to install the standalone Context.
>
> Which involves basically:
>
>    mkdir -o /opt/context
>    cd /opt/context
>    wget "http://minimals.contextgarden.net/setup/first-setup.sh
>    chmod 744 first-setup.sh
>    ./first-setup.sh
>
>    #this works up to this point only partially.
>
>  - /opt/context/tex  is not installed.   This is a bad error.  It causes
>   - first-setup.sh to fail.
>
> And what is loaded will cause conflicts with cygwin which already exists, I believe.
> I can't see why rsync is use to load anothe versio of rsync in a diff location.
>
>    #1. Why does 1st setup duplicate Cygwin dlls?

Because 99% of Windows users don't have rsync installed. And because
the version of rsync we are using links against cygwin's dlls.

But if you ask why it fetched that under cygwin, the answer is most
probably "because everyone attempting to install minimals under cygwin
gave up or vanished before we were able to fix the issues".

>         I've hurd that having multiple
>         cygwin*.dlls can cause problems.   Besideds They already exist and so does
>         luatex.exe for that matter.  'first-setup.sh' should know that it does a test
>         for CYGWIN, but doesn't seem to do anything with it.
>
>    #2. Also redundant and confusing is first-setup.sh forces the fetching of rsync by
>        an already existing rsync.  Is rsync already exists, why fetch another one and
>        put it in a different location.

In past we had special cygwin-specific binaries, but those building
them gave up. So we switched to fetching the "regular" windows
binaries and forgot about the fact that cygwin users wouldn't want to
install rsync & cygwin's dlls.

> I have texlive for unix on a cygwin platform, on top of an XP system.
>
> I want to make installing the standalone easy for cyginw and linux.

On linux it should be easy already, but if you have some specific
suggestion(s), let me know.

> #
> # Firstly, exactly what packages are needed for context?
> #  I assume it's one or more of the mtx prefixed programs below.  Please advise.
>
>   - mtx-update.lua
>
>   - mtxrun.exe
>   - mtxrun.dll
>   - mtxrun.lua
>
>   - lua52.dll
>   - luatex.dll   Is this needed in addition to luatex.exe?

Yes, luatex.exe is only 1.5K and depends on it.

>   - luatex.exe   <Note: cygwin has  luatex.exe  same functionality?>

Probably yes (unless you have a different version of luatex yourself).

>   - kpathsea620.dll  <Note:  TeXLive has kpath related code>

I didn't understand.

> I understand that there are not a lot of people experimenting with the latest ConTeXt
> and even less for the Cygin platform.

There are a lot of people using the latest ConTeXt (for a certain
meaning of "a lot": it's definitely less than the number of latex or
MS Word users, but still a reasonable number). But the cross section
of those and cygwin users might well be asymptotically approaching
zero (or one, now that you are attempting it).

>  But, I would like to make it easier and clearer for Cygwin users who do want to experiement with the latest versions.

I tried to fix a few problems. Can you please try again.

> I don't know if installing for a native linux version is easier or more straightforward or not.

At least there should not be any problems with fetching rsync and
shared libraries on Linux. Feel free to try.

Mojca
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  parent reply	other threads:[~2014-05-03 11:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-01 12:42 Standalone hwitloc
2014-03-02  0:06 ` Standalone Hans Hagen
2014-05-03 11:35 ` Mojca Miklavec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-08-18 15:40 minimals Hans Hagen
2011-08-18 15:58 ` standalone (was: minimals) Henning Hraban Ramm
2011-08-18 16:38   ` standalone Hans Hagen

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=CALBOmsafGWfefQsK91J06c85-_yErjkrqn+kjwJuWP8RAuYJOg@mail.gmail.com \
    --to=mojca.miklavec.lists@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).