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>
Cc: Karl Berry <karl@freefriends.org>
Subject: Re: ConTeXt modules on CTAN (authors, please check)
Date: Tue, 15 Jul 2008 17:31:54 +0200	[thread overview]
Message-ID: <6faad9f00807150831t4f36e8fay1f3271fb18df7944@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0807151114040.15467@nqv-yncgbc>

On Tue, Jul 15, 2008 at 5:14 PM, Aditya Mahajan wrote:
> On Mon, 14 Jul 2008, Mojca Miklavec wrote:
>
>> Hello,
>>
>> The ConTeXt modules are now mirrored on CTAN, but they might be
>> lacking better descriptions in the catalogue. Authors of modules -
>> please check.
>
> They are still not included in the current texlive beta.

They are under
    http://www.ctan.org/tex-archive/macros/context/contrib/
but not imported into TeX Live yet.

Karl asked us to rename tex/context/third/vim into
tex/context/third/context-vim (or some similar approach), so that
folder names would match package name. Renaming the package into vim
is out of question since there is already "vim" package in TL (this is
what Karl says, but even if there are no collisions - it's nice if
it's clear that something is a ConTeXt package).

TeX Live has some automated scripts that check the whole TeX Live tree
and match package name with contents. If all packages obey that rule,
then one doesn't need to care about list of files that belong to a
certain package.

But I don't like that solution just for the sake of TeX Live. All
other distributions can live without that double naming happily. It
would be much better if some ConTeXt-specific package management would
be implemented (scripts should be told that they need to deal with
ConTeXt package, not LaTeX package, and search fof files accordingly)
- ConTeXt packages have enough strict rules of where files may reside.
Or whatever.

Another solution would be to write rules about which files to fetch
for each package. But then Karl doesn't like that solution since he
doesn't like having to create new rules every time a new package
appears. I'm willing to write those if that would solve the problem.

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


  reply	other threads:[~2008-07-15 15:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 20:21 Mojca Miklavec
2008-07-15 15:14 ` Aditya Mahajan
2008-07-15 15:31   ` Mojca Miklavec [this message]
2008-07-15 20:50     ` Hans Hagen
2008-07-15 20:35   ` 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=6faad9f00807150831t4f36e8fay1f3271fb18df7944@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --cc=karl@freefriends.org \
    --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).