Changeset 799 for branches/Release04x02/twikiplugins/BuildContrib/data/TWiki/BuildContrib.txt

Timestamp:

11/19/08 08:55:36 (4 years ago)

Author:

KennethLavrsen

Message:

Item205: More TWiki. to %SYSTEMWEB% updated and some Foswiki links I could not
help creating

File:

• branches/Release04x02/twikiplugins/BuildContrib/data/TWiki/BuildContrib.txt (modified) (7 diffs)

branches/Release04x02/twikiplugins/BuildContrib/data/TWiki/BuildContrib.txt

@@ -118 +118 @@
 Now install the !BuildContrib. In a subversion checkout, =cd= to the TWiki root
 and =perl pseudo-install.pl BuildContrib=. In a non-subversion environment,
-install the =BuildContrib= package from TWiki.org.
+install the =BuildContrib= package from foswiki.org.
 
 ---+++ Environment Variables
@@ -125 +125 @@
 pick up the components of the build system. Set =TWIKI_LIBS= (which is a
 path, same as =PERL5LIB=) to point to your =lib= directory in your development
-TWiki. =$TWIKI_LIBS= is used to extend @INC _for the duration of the build
+Foswiki. =$TWIKI_LIBS= is used to extend @INC _for the duration of the build
 only_, so it won't mask problems during testing.
 
@@ -256 +256 @@
 The installer script written by the build process uses the dependency type
 to decide how to install dependant modules. 'cpan' means 'get the module
-from CPAN' and 'perl' means 'get the module from the Plugins web on TWiki.org'
+from CPAN' and 'perl' means 'get the module from the Extensions web on foswiki.org'
 (or whatever other repositories the admin has specified using =$TWIKI_PACKAGES=
 or =$PLUGINS_URL=).
@@ -263 +263 @@
 When your module (the _depender_) depends on another module (a _dependee_), it is important to think carefully about what version of the dependee your module requires.
 
-When you are working with TWiki modules (such as contribs and plugins) you should list the version number of the module that you tested with. Normally you will want to use a <code>&gt;</code> condition, so that more recent versions will also work. If a dependency on a TWiki module fails (because the module isn't installed, for example) then the installer script will pull *the latest version* of the module from TWiki.org, whether that is the required version or not. This is a limitation of the way plugins are stored on TWiki.org.
+When you are working with TWiki modules (such as contribs and plugins) you should list the version number of the module that you tested with. Normally you will want to use a <code>&gt;</code> condition, so that more recent versions will also work. If a dependency on a TWiki module fails (because the module isn't installed, for example) then the installer script will pull *the latest version* of the module from foswiki.org, whether that is the required version or not. This is a limitation of the way plugins are stored on foswiki.org.
 
 When you are working with CPAN modules, you need to take account of the fact that there are *two types* of CPAN modules; _built-ins_ and _add-ons_.
@@ -280 +280 @@
 contans <code>ONLYIF ( _condition_ )</code>, where _condition_ is a Perl
 conditional. This is most useful for enabling dependencies only for certain
-versions of TWiki. For example,
+versions of Foswiki. For example,
 <verbatim>
 TWiki::Rhinos,>=1.000,perl,Required. Download from TWiki:Plugins/RhinosContrib and install.
@@ -301 +301 @@
      all the files you want to include in the release package
 During development we recommend you use the =pseudo-install.pl= script to
-soft-link your plugin code into your development TWiki. This script uses the
+soft-link your plugin code into your development Foswiki. This script uses the
 MANIFEST you write and creates softlinks in your development TWiki that allow
 you to run your test code without having to do a full re-install each time you
@@ -375 +375 @@
    * =cd twikiplugins/BathPlugin/lib/TWiki/Plugins/BathPlugin=
    * =perl build.pl upload=
-By default the =upload= target will upload to TWiki.org. You will be prompted
+By default the =upload= target will upload to foswiki.org. You will be prompted
 to enter an alternate upload target, should you require it (e.g. to upload to
 private corporate repository). The upload updates the topic and any associated