Hi Mojca & all,

On 2011-05-06 <20:55:59>, Mojca Miklavec wrote:
> On Wed, May 4, 2011 at 19:00, Philipp Gesang wrote:
> >
> >> 1b. At least somebody needs to find it useful and request it (which
> >> you just did; should it also be added to TeX Live?).
> >
> > What would the inclusion into TL imply?
> 
> That people using TeX Live could also install it.

True, but I was, rather selfishly, thinking about what it would
imply for the module author. Permanent maintenance of one release
over a year? Is it really worth it? After all, most people who
come to this list asking for help with their TL context are
advised to switch to the minimals.

> >> 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).
> >
> > If it’s possible now I’d try it asap.
> 
> Did you have any problems? In case you did, please contact Patrick.

I did have problems about a year ago. Probably tomorrow---
depending on the weather---I’ll add an xml interface file and
comment the module source. After that I’ll give the upload
another shot.

> >> Once 1 and 2 are met, I just add a single line to sources that trigger
> >> inclusion of the module to minimals (and a separate one for inclusion
> >> into TeX Live).
> >
> > Looks like context needs a package manager.

> Do you have any suggestion how it should look like and how it should
> work? mtx-update is kind-of package manager, but I admit that I miss
> some GUI (but then again I have no idea how to write a portable GUI).

The GUI would be the last thing I’d start worrying about.
Basically it would have to receive a list of locations and the
respective VCS, like for instance: ::

  t-filter,       git, https://github.com/adityam/filter.git 
  transliterator, hg,  https://bitbucket.org/phg/transliterator

Then it would call the VCS to checkout the tip (or latest tag or
whatever). Each should have a “.install.lua” in the base dir
containing instructions about where the files should go. (Best
thing is, probably, that no compilation is necessary because
everything’s plain text.) A local register could contain version
information, filenames, paths etc. of the modules installed.

But that’s just musings as I don’t have a clue what restrictions
other OS might put on file attributes (does luafs get rid of
these?). Someone with experience on all the main three platforms
could really help here.

Philipp


> 
> Mojca
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the 
> Wiki!
> 
> maillist : [email protected] / 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
> ___________________________________________________________________________________

Attachment: pgp8cQO0i2zHc.pgp
Description: PGP signature

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the 
Wiki!

maillist : [email protected] / 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 via email to