minimals: How to prevent that core and modules become incompatible?

From: Paul Menzel <paulepanter@users.sourceforge.net>
To: ntg-context@ntg.nl
Subject: minimals: How to prevent that core and modules become incompatible?
Date: Mon, 25 Jul 2011 00:26:41 +0200	[thread overview]
Message-ID: <1311546402.3866.90.camel@mattotaupa> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 1007 bytes --]

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

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

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