ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: pmlists@free.fr (Peter Münster)
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: [t-rst] inclusion into Minimals, i. e. installation using `./first-setup.sh --extras='t-rst'`
Date: Sun, 01 May 2011 14:33:24 +0200	[thread overview]
Message-ID: <87mxj6zjl7.fsf@micropit.couberia.bzh> (raw)
In-Reply-To: <BANLkTimQ=sES-Smx+wrjLv3N1tiWK_0S3w@mail.gmail.com> (Mojca Miklavec's message of "Sun, 1 May 2011 13:18:05 +0200")

Mojca Miklavec <mojca.miklavec.lists@gmail.com> writes:

> 2. Until we do something about it, it would be very very desirable to
> put it to modules.contextgarden.net (I know that it is painful).

Indeed, very painful ... ;)

I'm sure, that the module authors would like to run just one simple
command (e.g. "make contrib-upload") to update their modules in the
distribution, instead of filling a form in a web-browser.

Suggestion: to make it easy and fast, why not just add a new
svn directory to foudry.supelec.fr, and every author gets a
sub-directory, where they can upload their modules in TDS format. And
the first-setup.sh would just pull the modules from there.
Thus the authors can keep using bitbucket, github, etc. for their daily
work, and upload a new version by means of a new makefile-target.

-- 
           Peter
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2011-05-01 12:33 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-01 10:18 Paul Menzel
2011-05-01 11:18 ` Mojca Miklavec
2011-05-01 12:33   ` Peter Münster [this message]
2011-05-01 12:37     ` Mojca Miklavec
2011-05-01 14:14   ` Aditya Mahajan
2011-05-02  5:58     ` Mojca Miklavec
2011-05-04 17:00   ` Philipp Gesang
2011-05-04 22:02     ` Aditya Mahajan
2011-05-05  9:47       ` Philipp Gesang
2011-05-06 18:55     ` Mojca Miklavec
2011-05-06 19:04       ` Aditya Mahajan
2011-05-06 19:08       ` Marco
2011-05-07 15:36         ` Mojca Miklavec
2011-05-08 11:18           ` Taco Hoekwater
2011-05-08 14:17             ` Marco
2011-05-08 19:43               ` Pontus Lurcock
2011-05-08 20:07                 ` GUI for minimals WAS: " Marco
2011-05-09  8:03                   ` Taco Hoekwater
2011-05-08 14:56             ` Arthur Reutenauer
2011-05-08 17:36               ` Hans Hagen
2011-05-08 18:17                 ` Mojca Miklavec
2011-05-08 21:00                   ` Marco
2011-05-08 21:28                     ` Thomas A. Schmitz
2011-05-08 22:17                       ` Marco
2011-05-08 14:01           ` Marco
2011-05-07 10:19       ` Philipp Gesang
2011-05-07 11:23         ` Wolfgang Schuster
2011-05-07 12:08           ` Philipp Gesang
2011-05-07 15:45         ` Mojca Miklavec
2011-05-08 18:32           ` Philipp Gesang

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=87mxj6zjl7.fsf@micropit.couberia.bzh \
    --to=pmlists@free.fr \
    --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).