minimals: How to prevent that core and modules become incompatible?
Dear ConTeXt folks, I just experienced a situation that I wanted to try a module, in this case TikZ [1][2], and I only had run `./first-setup.sh`, so the module and “core” were diverted and I got an error message. ! Undefined control sequence. system > tex > error on line 396 in file tikz.tex: Undefined control sequence ... \pgfutil@addpdfresource@colorspaces ...olorspaces {#1} l.396 ...rspaces{ /pgfprgb [/Pattern /DeviceRGB] } Running `./first-setup.sh --extras=all` fixed the problem for me, but not wanting to install all extras it is quite hard to insert/remember all extras installed on the system. Is there a command to prevent these kind of things or should an option `upgrade` be introduced? Thanks, Paul [1] http://modules.contextgarden.net/ [2] http://wiki.contextgarden.net/TikZ
On 25-7-2011 12:26, Paul Menzel wrote:
Dear ConTeXt folks,
I just experienced a situation that I wanted to try a module, in this case TikZ [1][2], and I only had run `./first-setup.sh`, so the module and “core” were diverted and I got an error message.
! Undefined control sequence.
system> tex> error on line 396 in file tikz.tex: Undefined control sequence ...
\pgfutil@addpdfresource@colorspaces ...olorspaces {#1} l.396 ...rspaces{ /pgfprgb [/Pattern /DeviceRGB] }
Running `./first-setup.sh --extras=all` fixed the problem for me, but not wanting to install all extras it is quite hard to insert/remember all extras installed on the system.
the updater/installer remembers what you've installed so the next time the extras will be synchronized along with the core (all or the selection you've chosen) Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
Am Montag, den 25.07.2011, 09:06 +0200 schrieb Hans Hagen:
On 25-7-2011 12:26, Paul Menzel wrote:
I just experienced a situation that I wanted to try a module, in this case TikZ [1][2], and I only had run `./first-setup.sh`, so the module and “core” were diverted and I got an error message.
! Undefined control sequence.
system> tex> error on line 396 in file tikz.tex: Undefined control sequence ...
\pgfutil@addpdfresource@colorspaces ...olorspaces {#1} l.396 ...rspaces{ /pgfprgb [/Pattern /DeviceRGB] }
Running `./first-setup.sh --extras=all` fixed the problem for me, but not wanting to install all extras it is quite hard to insert/remember all extras installed on the system.
the updater/installer remembers what you've installed so the next time the extras will be synchronized along with the core (all or the selection you've chosen)
Well, then this somehow failed for me. The TikZ module was still from May 2011 and the core July 2011. Thanks, Paul
Am 25.07.2011 um 12:10 schrieb Paul Menzel:
the updater/installer remembers what you've installed so the next time the extras will be synchronized along with the core (all or the selection you've chosen)
Well, then this somehow failed for me. The TikZ module was still from May 2011 and the core July 2011.
The name of the parameter has changed from “extras” to “modules”. To install all modules you have to type “first-setup.sh --modules=all”. Wolfgang
Am Montag, den 25.07.2011, 12:14 +0200 schrieb Wolfgang Schuster:
Am 25.07.2011 um 12:10 schrieb Paul Menzel:
the updater/installer remembers what you've installed so the next time the extras will be synchronized along with the core (all or the selection you've chosen)
Well, then this somehow failed for me. The TikZ module was still from May 2011 and the core July 2011.
The name of the parameter has changed from “extras” to “modules”.
To install all modules you have to type “first-setup.sh --modules=all”.
Thanks, but I think this was not the problem at my end. `~/.first-setup.sh` is still the one from January, so `extras` worked for me. Thanks, Paul
At Monday, 25.07.2011 on 12:31 Paul Menzel wrote:
Thanks, but I think this was not the problem at my end. `~/.first-setup.sh` is still the one from January, so `extras` worked for me.
The parameters (and the actual update process) are handled by bin/mtx-update.lua which is one of the first things, that first-setup.sh/.bat updates.
That is a bug, not a version mismatch. Mojca
participants (5)
-
Andreas Schneider -
Hans Hagen -
Mojca Miklavec -
Paul Menzel -
Wolfgang Schuster