From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Moving module installation from first-setup.sh to ctxtools
Date: Tue, 31 May 2011 18:52:01 +0200 [thread overview]
Message-ID: <BANLkTinAXJRxE5kYCnzMgvcfFrZBkzssZw@mail.gmail.com> (raw)
In-Reply-To: <loom.20110531T184131-400@post.gmane.org>
On Tue, May 31, 2011 at 18:44, Bruce wrote:
> Mojca Miklavec writes:
>
>>
>> On Tue, May 31, 2011 at 18:26, Bruce wrote:
>> > Per subject line, I'd just like to suggest moving the (quite helpful)
>> > module installation functionality from first-update.sh to one of the
>> > core context scripts (like ctxtools), so that it's usable outside
>> > the minimal distribution (in TL). E.g. something like:
>> >
>> > ctxtools --install="t-simpleslides"
>>
>> How would you determine the destination (where to put the module)?
>
> Same way the first-setup.sh script does. Why should I have to think about
> where to put a module?
first-setup.sh always places the files under
$LOC/tex/texmf-context/
where $LOC is location of first-setup.sh. The "tex" part is
configurable, but it is governed by some settings that you have to
provide to first-setup.sh explicitely.
If you are using TeX Live and want to install the module, you need to
decide whether you will install it under $HOME/texmf,
$HOME/Library/texlive/texmf, /usr/locat/texlive/texmf-local, etc.
>> ConTeXt tools could do it, but the main question is: where? Another
>> problem is this doesn't provide any "uninstallation", but user has to
>> be aware of that.
>
> That's not a big deal to me. But it could always include an uninstall option.
For uninstaller the installer should remember the files and store that
somewhere. This is currently not done at all.
>> TeX Live & MikTeX provide the module. Out of curiosity: where else
>> would you find the command handy to use?
>
> Not following you here.
How exactly would you want to use such command? With what TeX distribution?
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
___________________________________________________________________________________
next prev parent reply other threads:[~2011-05-31 16:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-31 16:26 Bruce
2011-05-31 16:37 ` Mojca Miklavec
2011-05-31 16:44 ` Bruce
2011-05-31 16:52 ` Mojca Miklavec [this message]
2011-05-31 21:17 ` Bruce
2011-05-31 21:26 ` Mojca Miklavec
2011-05-31 21:30 ` Mojca Miklavec
2011-05-31 23:15 ` Bruce
2011-06-01 6:53 ` Mojca Miklavec
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=BANLkTinAXJRxE5kYCnzMgvcfFrZBkzssZw@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).