.. ****** BEGIN LICENSE BLOCK ***** .. Version: CDDL 1.0 .. .. The contents of this file are subject to the COMMON DEVELOPMENT AND .. DISTRIBUTION LICENSE (CDDL) Version 1.0 (the "License"); you may not use .. this file except in compliance with the License. You may obtain a copy of .. the License at http://www.sun.com/cddl/ .. .. Software distributed under the License is distributed on an "AS IS" basis, .. WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License .. for the specific language governing rights and limitations under the .. License. .. .. The Original Code is .. "netlabs.org Open Source Archive Administrator/Client" .. .. The Original Distribution Package is named .. "netlabs.org Open Source Archive Administrator/Client" .. and maintained and distributed by the Initial Developer .. and/or netlabs.org only. .. .. In addition to the CDDL the following applies: .. If you modify the Original Code, you may distribute it only .. as a part of a distribution package where .. - the name of the package, created directories or .. OS2.INI entries do not contain any of the terms .. - "netlabs.org Open Source Archive" .. - "NOSA" .. - "NOSAC" .. - "NOSAADM" .. - neither netlabs.org nor the Initial Developer is stated as .. the vendor or originator of the resulting Distribution Package, .. which contains the Modified Code. .. .. The Initial Developer of the Original Code is .. netlabs.org: Christian Langanke . .. Portions created by the Initial Developer are Copyright (C) 1999-2008 .. the Initial Developer. All Rights Reserved. .. .. Contributor(s): .. .. ***** END LICENSE BLOCK ***** */ .include nosatitle.inc .ti [=DOCTITLE] .hi 234 .. todo !!! .. update info on folder update etc .. ############################################################################# .1 [=DOCTITLE] .. ############################################################################# .an IDPNL_MAIN .at font='20.Tms Rmn' fc=darkgray italic bold .bitmap nllogo.bmp center .ce in association with .bitmap teamlogo.bmp center .ce present the .at font='24.Tms Rmn' fc=red bold italic .ce [=DOCTITLE] .at [=TOPICS] .su 1 .. ============================================================================= .2 What is it all about ? .. ============================================================================= .an IDPNL_WHAT . [=TOPICS] .su V30 .. ----------------------------------------------------------------------------- .3 Overview .. ----------------------------------------------------------------------------- .an IDPNL_WHAT_OVERVIEW .bitmap src\bmp\nllogo.bmp center .at font='24.Tms Rmn' fc=red bold .ce [=DOCTITLE] .at Are you an OS/2 or eComStation developer or want to be one ? Do you search for sample sourcecode or do you have a really good idea for an OS/2 program ? Would you like to have a look at some of the best OS/2 and ecomStation apps or utilities around ? Then come to the [.IDPNL_WHAT_NETLABS] and see, what OS/2 and eComStation related projects are currently hosted here. More, *netlabs.org* hosts source archives for several [.IDPNL_WHAT_PROMOTEOPENSOURCE Open Source Projects'] in the [=NAME], which can be freely accessed. The [=TITLE] package being presented to you by [=IDPNL_WHAT_NETLABS] in association with [.IDPNL_WHAT_TEAMOS2] intends to help you to access these source archives more easily. With this you can download those sources and update them whenever you like (when being member of a project team), so that the [=NAME] always represents the current stage of development at every time. This package is meant to ease the access to the [=NAME], as you need the [.IDPNL_WHAT_CVS] for to access the source archive, and this system is somewhat complex for beginners. The [=TITLE] will both help you with the installation and usage of *CVS* and does not force you to learn dozen of commands with parameters for usage on the command line before being able to see the source. Nevertheless this package can aid only to a certain extend, so that for some more complex operations it is still required to know *CVS* very well and to use the command line. But for the few things, that a beginner requires, and even for most of the operations, that a developer will need for modifications in the archive (requiring write permissions, of course), the [=TITLE] folder and its objects will be sufficient. .. ----------------------------------------------------------------------------- .3 Open Source .. ----------------------------------------------------------------------------- .an IDPNL_WHAT_PROMOTEOPENSOURCE . If you want to know .ul compact - what *Open Source* exactly is - because of what reasons it would make sense to make your own software *Open Source* - would like to know why *Open Source* makes sense for everybody, no matter if one is a hacker, business-man or a customer visit the following pages: .ul compact - [http://www.opensource.org The Open Source Page] . by the Open Source Initiative - [http://www.tuxedo.org/~esr/writings/cathedral-bazaar/index.html The Cathedral and the Bazaar] . by Eric S. Raymond The following are publications of *OS/2 e-Zine!*: .ul compact - [http://www.os2ezine.com/v4n1/wright.htm A dream of Open Source] . by Christopher B. Wright - [http://www.os2ezine.com/v4n1/bazaar.htm The Bazaar and the Other Bazaar] . by Christopher B. Wright - [http://www.os2ezine.com/v4n1/gnl.htm GNU's Not Linux] . by Christopher B. Wright - [http://www.os2ezine.com/v4n4/open.htm Why OpenSource ?] . by Ulrich M”ller The following is a publication of *The Electronical Developer Magazine for OS/2*: .ul compact - [http://www.edm2.com/0704/cvs2/cvshowto.html A Warped RCS/CVS HowTo] . by Henry Sobotka See also the current issues of .ul compact - [http://www.os2ezine.com OS/2 e-Zine!] - [http://www.edm2.com The Electronical Developer Magazine for OS/2] .. ----------------------------------------------------------------------------- .3 netlabs.org .. ----------------------------------------------------------------------------- .an IDPNL_WHAT_NETLABS .bitmap src\bmp\nllogo.bmp center .at font='24.Tms Rmn' fc=red .ce netlabs.org .at What is the goal behind *netlabs.org* ? The answer is simple: #New programs for OS/2#. . Possibly every OS/2- and eComStation user was at least mad once about having to change to another #Operating System#, only because there was no alternative for a program under OS/2. *netlabs.org* will definitely put an end to these times. The whole programming power can gather on the *netlabs.org* web pages in order to create freeware-programs in the style of the GNU-project under Linux and OS/2 and eComStation. Every user may download these programs and copy freely. Every OS/2 and eComStation user can make his contribution to *netlabs.org*, whether it is as a programmer, a designer, a supplier of ideas or just as a user. *netlabs.org* relies on the user, every user should be able to give his visions of software a place to grow. The *netlabs.org* platform is a logical consequence coming out of the growing possibilities of the internet. OS/2 and eComStation users are in most cases experienced programmers. If now all their potential is brought together and used as a whole, a lot of useful and creative programs can result from it. *netlabs.org* is a contribution to a sound OS/2-future with a lot of good programs which do not cost a fortune, but can keep up with any other software available. Visit the homepages of .ul compact - [http://www.netlabs.org www.netlabs.org] - [http://nosa.netlabs.org The netlabs.org Open Source Archive (NOSA)] .. ----------------------------------------------------------------------------- .3 Team OS/2 Germany .. ----------------------------------------------------------------------------- .an IDPNL_WHAT_TEAMOS2 .bitmap teamlogo.bmp center .at font='24.Tms Rmn' fc=red .ce Team OS/2 Germany .at Similar to the *Team OS/2* in the USA and to other OS/2 user groups, also in Germany OS/2 team members support and promote OS/2 and eComStation wherever possible on a private basis. After having grown to somewhat over 1000 members in 1996, at some regions, local Team OS/2 groups as registered societies have been founded in order to increase the efficiency of administration and the organisation of Team OS/2 events. Another intention was to become more independent from support from IBM for *Team OS/2*, which has been more and more going down over the years anyway. These local societies have then organized themselves in an umbrella organization named *Team OS/2 Deutschland e.V.*, where common needs of local societies can be satisfied better. Visit the homepage of .ul compact - [http://www.teamdv.de *Team OS/2 Deutschland e.V* and its member associations] .. ----------------------------------------------------------------------------- .3 Concurrent Versions System (CVS) .. ----------------------------------------------------------------------------- .an IDPNL_WHAT_CVS . See the following links in order to learn more about the *Concurrent Versions System* (CVS): .ul compact . - [http://www.cvshome.org *CVS* homepage] - [http://www.loria.fr/~molli/cvs-index.html *CVS* Bubbles] with links to documentation You can download *CVS* for OS/2 from: .ul compact - [http://hobbes.nmsu.edu/cgi-bin/h-search?key=cvs The Hobbes OS/2 Archive] or search the nearest FTP server near you via .ul compact - [http://ftpsearch.lycos.com/cgi-bin/search?form=medium&query=cvs*.zip&doit=Search&type=Case+insensitive+glob+search&limpath=os2&sort=hostdist FTP Search] [=NOTE] .ul - If you install CVS after installing the [=TITLE], and you don't intend to add the CVS bin directory to your PATH statement, you can rerun the installation program to let NOSA know where CVS is installed. - *CVS* requires the [.IDPNL_WHAT_EMXRUNTIME]. . . See also - [.IDPNL_HOW_SOLVEOPENFILES] .. ----------------------------------------------------------------------------- .3 Info-Zip .. ----------------------------------------------------------------------------- .an IDPNL_WHAT_INFOZIP .bitmap src\bmp\info-zip.bmp center The [=TITLE] uses the *Zip* and *UnZip* program of *Info-Zip*. [=NOTE] .ul compact - The programs and sources of *Info-Zip* is freely available. On the .sl compact - [http://www.info-zip.org Info-ZIP homepage] .el . follow the links to the download pages and download the latest version for OS/2. . - The filename scheme for the executable packages and source packages differ a littlebit between *Zip* and *UnZip*. . This is a littlebit confusing, so the scheme is listed here for the versions *Zip* V2.20 and *UnZip* V5.40 as an example: .lm 10 .pl compact tsize=20 break=none - zip22x1.zip = Zip 2.2, OS/2 16-bit exes (no encryption) - zip22x2.zip = Zip 2.2, OS/2 32-bit exes (no encryption) - zip22.zip = Zip 2.2, source code - unz540d2.zip = UnZip 5.40, OS/2 DLL (32-bit, C and REXX) - unz540x1.exe = UnZip 5.40, OS/2 self-extr. exes (16-bit) - unz540x2.exe = UnZip 5.40, OS/2 self-extr. exes (32-bit) - unzip540.zip = UnZip 5.40, source code .lm .. ----------------------------------------------------------------------------- .3 EMX Runtime .. ----------------------------------------------------------------------------- .an IDPNL_WHAT_EMXRUNTIME . *EMX* is an environment for creating 32-bit programs for OS/2 (and DOS). Developers can use the GNU C compiler to compile programs for emx. The main design goal of EMX is to support the GNU environment to simplify porting Unix software to OS/2 and DOS. This has been done with the [.IDPNL_WHAT_CVS], which is a widely used Unix software. As *CVS* is being used by the [=TITLE], the runtime of the *EMX* package is required. You can download the *EMX runtime* for OS/2 from: .ul compact - [http://hobbes.nmsu.edu/cgi-bin/h-search?key=emxrt.zip&dir=%2Fpub%2Fos2%2Fdev%2Femx The Hobbes OS/2 Archive] Download the file *emxrt.zip* from the subdirectory with the highest revision number. See also .ul compact - [.IDPNL_HOW_SOLVEOPENFILES] .. ============================================================================= .2 Prerequisites .. ============================================================================= .an IDPNL_PREREQUISITES . The following prerequisites apply to the current version of [=TITLE]: .ul - The [=TITLE] runs under OS/2 WARP Version 3 or later with *REXX* installed - Also required is the OS/2 version of the [.IDPNL_WHAT_CVS Concurrent Versions System (CVS)] for to provide access the [=NAME]. - *CVS* in turn requires the [.IDPNL_WHAT_EMXRUNTIME]. - if *CVS* is not already installed on your system, the *UnZip* program of [.IDPNL_WHAT_INFOZIP] are required. - For downloading sources from the [=NAME], also a working internet connection is required. .. ============================================================================= .2 Copyright & Co. .. ============================================================================= .an IDPNL_LEGAL . [=TOPICS] .su V30 .. ----------------------------------------------------------------------------- .3 Common Development and Distribution License (CDDL) .. ----------------------------------------------------------------------------- .an IDPNL_LEGAL_CDDL . [=TITLE] . was written by [.IDPNL_LEGAL_AUTHOR Christian Langanke], [=YEAR] . All rights reserved. You are welcome to send me your comments/suggestions via internet e-mail. Send your e-mail to: *[=EMAIL]* The source code of this package is available under the *Common Development and Distribution License (CDDL)*. See [http://www.sun.com/cddl/] for the full license text of the CCDL, and the following text for further restrictions on distributing modified versions of the [=TITLE]: .fo off Version: CDDL 1.0 The contents of this file are subject to the COMMON DEVELOPMENT AND DISTRIBUTION LICENSE (CDDL) Version 1.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.sun.com/cddl/ Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License. The Original Code is "netlabs.org Open Source Archive Administrator/Client" The Original Distribution Package is named "netlabs.org Open Source Archive Administrator/Client" and maintained and distributed by the Initial Developer and/or netlabs.org only. In addition to the CDDL the following applies: If you modify the Original Code, you may distribute it only as a part of a distribution package where - the name of the package, created directories or OS2.INI entries do not contain any of the terms - "netlabs.org Open Source Archive" - "NOSA" - "NOSAC" - "NOSAADM" - neither netlabs.org nor the Initial Developer is stated as the vendor or originator of the resulting Distribution Package, which contains the Modified Code. The Initial Developer of the Original Code is netlabs.org: Christian Langanke . Portions created by the Initial Developer are Copyright (C) 1999-2008 the Initial Developer. All Rights Reserved. .fo on .. ----------------------------------------------------------------------------- .3 The author .. ----------------------------------------------------------------------------- .an IDPNL_LEGAL_AUTHOR . This program is written by *Christian Langanke*. You can contact the author via internet e-mail. .. Note to translators: Please translate an additional line here: .. Please write either in german or english. Send your e-mail to: *[=EMAIL]* Visit also the homepage of .ul compact - [http://nosa.netlabs.org the *netlabs.org Open Source Archive*] - [http://clanganke.de the author *Christian Langanke*] - [http://www.netlabs.org *netlabs.org*] - [http://www.teamdv.de *Team OS/2 Germany*] and its member associations .. ============================================================================= .2 Installation .. ============================================================================= .an IDPNL_INSTALL . [=TOPICS] .su V30 .. ----------------------------------------------------------------------------- .3 Manual installation .. ----------------------------------------------------------------------------- .an IDPNL_INSTALL_MANINST . The [=ARCHIVE] packages are installed by a *WarpIN* archive: .ul - *[=NAME] [=ADMIN_PROGTYPE]* - *[=NAME] [=CLIENT_PROGTYPE]* The packages are by default installed into separate directories. [=NOTE] .ul compact - Do not install both packages into the same directory, as several scripts have the same name! During installation of the [=NAME] [=CLIENT_PROGTYPE], in a command window the user is prompted for several [.IDPNL_INSTALL_CONFIG configuration values]. .. ----------------------------------------------------------------------------- .3 Configuration .. ----------------------------------------------------------------------------- .an IDPNL_INSTALL_CONFIG . During installation, in a command window you are prompted for the following values. .. .. If the directory of the required [.IDPNL_WHAT_CVS] is not included in the *PATH* .. statement or is not already installed on your system, you can either .. .ul compact .. - enter the *Directory of CVS installation* later (see below). .. - let the installation program program install *CVS* .. .. If you want to let *CVS* be installed automatically, you need to .. .ul compact .. - copy the zip file with the current *CVS* version for OS/2 into the .. same directory with install.cmd, where the zip file must be named cvs???.zip .. - and have the *UnZip* program of [.IDPNL_WHAT_INFOZIP] at hand .. .. [=NOTE] .. .ul compact .. - If *CVS* is installed here by the installation program, .. the *CONFIG.SYS* is NOT modified in order to extend the *PATH* by the *CVS* .. bin directory, because this is not required by the [=TITLE]. Instead, if you .. perform any *CVS* operation via the [.IDPNL_INSTALL_WPSFOLDER], .. or open an [.IDPNL_USAGE_RO_WINDOW archive Window], .. the path is extended to the *CVS* bin directory for these sessions only. .. When entering values .ul compact - press *Enter* if the default value in brackets applies - press *Ctrl-Break* and *Enter* to abort - specify a drive to only modify the drive of the value - path values must be specified with a drive letter You also can rerun the installation program *install\install.cmd* in a command window at any time in order to modify any of these values. These are the values, that you are prompted for: .pl tsize=5 bold - netlabs.org Open Source Archive Server = The server hosting the [=NAME]. If you have other [=SHORTNAME]-like archive servers beside the one from *netlabs.org*, you can specify multiple hostnames separated by commas. .. - root directory for working directories on your computer = The directory, where all working directories, that you use with the [=TITLE], are being created. .. - CVS home directory = The (empty) directory, where *CVS* settings are stored .. - Init Command for project windows (optional) = any command that you want to be executed before [=TITLE] executes any *CVS* operation. This is especially useful when you frequently use [.IDPNL_USAGE_RO_WINDOW archive Windows], for which you may need to setup a different environment. . . Leave that field empty, if you do not need any init command. .. - CVS User Id = your user id, that you want to use with a *CVS* archive on the [=NAME] server. . [=NOTE] .ul compact - If you need only readonly access to the [=NAME], specify #guest# as your userid and later specify #readonly# as your password when [.IDPNL_USAGE_RO_LOGIN logging into] the server. - If you take part in any of the projects being hosted by the [=NAME], you have to specify the user id, that has been setup at *netlabs.org* for your login. - If the environment variable #%USER%# is set, this value is offered as default. - In an [.IDPNL_USAGE_RO_WINDOW archive Window] the environment variable #%USER%# will be set up with the user id, that you specify here. Keep that in mind, if you have to use different values for #%USER%# within the [=TITLE] and elswewhere. .el .. - pager executable = the executable, that should page long *CVS* outputs. Default is using *more.exe*, which of course has the disadvantage, that you can only go forward within the output, but cannot page back, like with *less* or some versions of *list*. .. - Directory of CVS installation = This prompt only appears, if the *CVS* executables are not reachable by your *PATH* statement in *CONFIG.SYS*. Then you can specify the installation directory of *CVS* and the [=TITLE] will extend the *PATH* before performing any *CVS* operation. After that the installation program creates the [=TITLE] [.IDPNL_INSTALL_WPSFOLDER Workplace Shell folder] with several objects in it. .. ----------------------------------------------------------------------------- .3 The [=DOCTITLE] folder .. ----------------------------------------------------------------------------- .an IDPNL_INSTALL_WPSFOLDER .bitmap folder.bmp center To (re)create the [=TITLE] *folder* with precustomized program objects in it, execute the following steps: .ol compact .*---------------- - open a command window .*---------------- - change into the directory, where the files of the [=TITLE] package reside - run the command .sl compact - *cvswps* The following Workplace Shell objects are created within the [=TITLE] folder: .su H50 [=NOTE] .ul compact .*---------------- - If you want to change the location of the files of the [=TITLE] package, move the directory, where the files reside, to the new location and rerun the *[=IDPNL_INSTALL_INSTALL]* to update the objects. .*---------------- .. ............................................................................. .4 Selected netlabs.org Open Source Archives .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_SELECTEDARCHIVES .bitmap selected.bmp center This folder within the [=TITLE] folder contains one [.IDPNL_INSTALL_WPSOBJ_ARCHIVEFOLDER subfolder] for each *CVS* archive that you selected to access. See also .ul compact - [.IDPNL_INSTALL_WPSOBJ_ARCHIVEFOLDER] - [.IDPNL_USAGE_LIST] - [.IDPNL_USAGE_LIST_VIEW] - [.IDPNL_USAGE_LIST_UPDATE] - [.IDPNL_USAGE_UPDATEFOLDER] .. ............................................................................. .4 netlabs.org Open Source Archive Websites/Connections .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_WEBSITES .bitmap websites.bmp center This folder within the [=TITLE] folder contains *Universal Resource Locator* (URL) objects related to the [=NAME] in a sbufolder *Development*. [=NOTE] .ul compact - Before you open one of the *URL* objects within the *Development* subfolder to display the World Wide Web pages within your internet browser, that these *URLs* point to, make sure, that you have an active internet connection. - under eComStation, shadows of all objects within this folder are also created in a subfolder *Development* within the *Websites* folder of eComStation - under OS/2 WARP 4 or before, the folder name and symbol display like this .bitmap connect.bmp center and the shadows of all objects within this folder are also created in a subfolder *Development* within the *Connections* folder of OS/2 .. ............................................................................. .4 netlabs.org Open Source Archive Information .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_INFORMATION .bitmap info.bmp center This folder within the [=TITLE] folder contains documentation about the [=TITLE] and, if installed on your system, objects for the the online documentation about the [.IDPNL_WHAT_CVS *Concurrent Versions System* (CVS)] [=NOTE] .ul compact - shadows of all objects within this folder are also created in the *Information* folder of OS/2. .. ............................................................................. .4 Update the Open Source Archive list from netlabs.org .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_UPDATELIST .bitmap update_l.bmp center This object within the [=TITLE] folder updates the [=NAME] list file via FTP from *netlabs.org*. You need to have an active internet connection for being able to update this file. See also .ul compact - [.IDPNL_USAGE_LIST] - [.IDPNL_USAGE_LIST_VIEW] - [.IDPNL_USAGE_LIST_UPDATE] - [.IDPNL_USAGE_UPDATEFOLDER] .. ............................................................................. .4 View the netlabs.org Open Source Archive list .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_VIEWLIST .bitmap view_l.bmp center This object within the [=TITLE] folder lets you view the contents of the [=NAME] list file. See also .ul compact - [.IDPNL_USAGE_LIST] - [.IDPNL_USAGE_LIST_VIEW] - [.IDPNL_USAGE_LIST_UPDATE] - [.IDPNL_USAGE_UPDATEFOLDER] .. ............................................................................. .4 Update Current Archive folder .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_UPDATEFOOLDER .bitmap update_f.bmp center This object within the [=TITLE] folder updates the folder named *[.IDPNL_INSTALL_WPSOBJ_SELECTEDARCHIVES]*. See also .ul compact - [.IDPNL_USAGE_LIST] - [.IDPNL_USAGE_LIST_VIEW] - [.IDPNL_USAGE_LIST_UPDATE] - [.IDPNL_USAGE_UPDATEFOLDER] .. ............................................................................. .4 Edit CVS configuration .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_CONFIGCVS .bitmap config.bmp center This object within the [=TITLE] folder edits the file #%home%\.cvsrc#, which contains global *CVS* options used by the [=TITLE]. See the *CVS* reference sections for more information: .ul compact - [inf:cvs Default options and the ~/.cvsrc file] .. ----------------------------------------------------------------------------- .3 Archive folder .. ----------------------------------------------------------------------------- .an IDPNL_INSTALL_WPSOBJ_ARCHIVEFOLDER .bitmap afolder.bmp center In the folder named *[=IDPNL_INSTALL_WPSOBJ_SELECTEDARCHIVES]* for each selected *CVS* archive on the [=NAME] server a separate [=IDPNL_INSTALL_WPSOBJ_ARCHIVEFOLDER} is created with the following Workplace Shell objects inside: .su H50 More, a shadow to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your computer is created. See also .ul compact - [.IDPNL_USAGE_USINGFOLDER] .. ............................................................................. .4 Login .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_LOGIN .bitmap login.bmp center This object within an archive folder logs you into a *CVS* archive on the [=NAME] server. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs login* .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RO_LOGIN] .. ............................................................................. .4 Logout .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_LOGOUT .bitmap logout.bmp center This object within an archive folder logs you out of a *CVS* archive you previously logged into. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs logout* .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RO_LOGOUT] .. ............................................................................. .4 Checkout file .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_CHECKOUT .bitmap checkout.bmp center This object within an archive folder checks out a file of *CVS* archive on the [=NAME] server. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs checkout* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RO_CHECKOUT] .. ............................................................................. .4 Fix Snapshot .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_FIXSNAPSHOT .bitmap fixsnap.bmp center This object within an archive folder fixes a previously unpacked snapshot of the *CVS* archive. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvsenv $FIX* .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_CVS_SNAPSHOTS] .. ............................................................................. .4 View file log .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_VIEWLOG .bitmap log.bmp center This object within an archive folder shows the *CVS* log in an archive. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs log* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RO_VIEWLOG] .. ............................................................................. .4 Query file status .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_VIEWSTATUS .bitmap status.bmp center This object within an archive folder shows the status of a local file of a *CVS* archive. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs status* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RO_VIEWSTATUS] .. ............................................................................. .4 Add new file .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_ADDNEW .bitmap add.bmp center This object adds a new file or directory to a *CVS* archive on the [=NAME] server. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs add* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RW_ADDNEW] .. ............................................................................. .4 Update local files .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_UPDATE .bitmap update.bmp center This object updates local files with changes being made by others in a *CVS* archive on the [=NAME] server since you last. checked out or updated the file. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs update* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RO_UPDATE] .. ............................................................................. .4 Merge to local files .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_MERGE .bitmap merge.bmp center This object merges changes being made by others in a *CVS* archive on the [=NAME] server to local modified files. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs update* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - Althouth there exist two icons for updating a local file and merging to a local file within the [=TITLE] folder, they actually execute the same *CVS* command, namely *update*. See also .ul compact - [.IDPNL_USAGE_RW_MERGE] .. ............................................................................. .4 Commit file changes .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_COMMIT .bitmap commit.bmp center This object commits your changes to the archive *CVS* archive on the [=NAME] server. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs commit* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RW_COMMIT] .. ............................................................................. .4 Tag file .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_TAG .bitmap tag.bmp center This object adds, moves or removes tags for files in a *CVS* archive on the [=NAME] server. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs tag* # # .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RW_TAG] .. ............................................................................. .4 Generate Change Report .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_REPORT .bitmap report.bmp center This object generates a HTML report form, that enables you to report changes, that you have committed to a *CVS* archive on the [=NAME], to the change report database via email. It depends on the project team, wether your project uses such reports or not. If your project team decides not to use change reports, simply ignore this icon. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvsreport* .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RW_REPORT] .. ............................................................................. .4 Remove file .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_REMOVE .bitmap remove.bmp center This object removes files, or better: marks files as removed within a *CVS* archive on the [=NAME] server. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs remove* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. See also .ul compact - [.IDPNL_USAGE_RW_REMOVE] .. ............................................................................. .4 View modules .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_MODULES .bitmap modules.bmp center This object displays modules defined for a *CVS* archive on the [=NAME] server. See also .ul compact - [.IDPNL_USAGE_RO_VIEWMODULES] .. ............................................................................. .4 Window .. ............................................................................. .an IDPNL_INSTALL_WPSOBJ_WINDOW .bitmap window.bmp center This object open a textmode window being set up for access on a *CVS* archive on the [=NAME] server. See also .ul compact - [.IDPNL_USAGE_RO_WINDOW] .. ============================================================================= .2 Usage .. ============================================================================= .an IDPNL_USAGE . [=TOPICS] .su V30 .. ----------------------------------------------------------------------------- .3 The archive list file .. ----------------------------------------------------------------------------- .an IDPNL_USAGE_LIST The [=TITLE] comes with a file named #archive.lst#, which contains a list of the current archives available on the [=NAME] server. This list also contains the complete name of the rootdirectory of each *CVS* archive, which is necessary for *CVS* to function properly. [=NOTE] .ul compact - If this file is not present, the [=TITLE] will not function properly. See also .ul compact .su H50 .. ............................................................................. .4 Update the archive list file .. ............................................................................. .an IDPNL_USAGE_LIST_UPDATE . The [.IDPNL_USAGE_LIST archive list file] can be outdated due to some reasons: .ul compact - a new archive has been established at *netlabs.org*, which you might be interested to have a look at. - the rootdirectory of an *CVS* archive has moved, so that the old name being stored on your computer is not longer valid. In both situations it is quite easy to update the list file from the FTP server of *netlabs.org*. Just perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_UPDATELIST] [=NOTE] .ul compact - If you have other [=SHORTNAME]-like archive servers beside the one from *netlabs.org*, you can specify multiple hostnames within the installation program, separated by commas within the [.IDPNL_INSTALL_INSTALL]. When updating the *archive list file*, it will be assembled from the lists of all servers, that could be queried successfully. Entries in the list coming from servers, that could not be reached, remain untouched. See also .ul compact - [.IDPNL_USAGE_LIST] - [.IDPNL_USAGE_LIST_VIEW] - [.IDPNL_USAGE_UPDATEFOLDER] .. ............................................................................. .4 View the archive list .. ............................................................................. .an IDPNL_USAGE_LIST_VIEW . In order to view the archives list file, that is being stored on your computer, perform the following steps: .ul compact - open the [=TITLE] folder - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_VIEWLIST] See also .ul compact - [.IDPNL_USAGE_LIST] - [.IDPNL_USAGE_LIST_UPDATE] .. ----------------------------------------------------------------------------- .3 Update the Current Archive Folder .. ----------------------------------------------------------------------------- .an IDPNL_USAGE_UPDATEFOLDER . You can rebuild the complete [=TITLE] folder at any time, in case that .ul compact - you got lost some icons - or that an updated [.IDPNL_USAGE_LIST archive list file] contains the name of a new source archive available on the [=NAME] server. In order to update the complete folder, perform the following steps: .ul compact - open the [=TITLE] folder - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_UPDATEFOOLDER] As an alternative, you can do the same via commandline: .ul compact - open a command window - change to the directory, where the files of the [=TITLE] reside - execute the command .sl compact - *cvswps* [=NOTE] .ul compact - You do not need to have an active internet connection in order to update the [=TITLE], as only the [.IDPNL_USAGE_LIST archive list file] already being stored on your computer is used. See also .ul compact - [.IDPNL_USAGE_USINGARCHIVE] - [.IDPNL_USAGE_USINGFOLDER] - [.IDPNL_USAGE_LIST] - [.IDPNL_USAGE_LIST_UPDATE] - [.IDPNL_USAGE_LIST_VIEW] - [.IDPNL_WHAT_CVS] .. ----------------------------------------------------------------------------- .3 Using a netlabs.org CVS archive .. ----------------------------------------------------------------------------- .. TODO .an IDPNL_USAGE_USINGARCHIVE . For accessing a remote *CVS* archive, you will need some basic *CVS* knowledge, even when [=TITLE] eases the access to it by providing a simple WPS interface. Please read the following sections: .su H50 Depending on which type of access you have, refer to: .ul compact - [.IDPNL_USAGE_RO] - [.IDPNL_USAGE_RW] See also .ul compact - [.IDPNL_USAGE_USINGFOLDER] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 CVS working directory .. ............................................................................. .an IDPNL_USAGE_CVS_WORKINGDIR . *CVS* needs a working directory, when it is to perform actions on a *CVS* archive. During installation of the [=TITLE], you have specified a working directory on your harddisk, where the subdirectories for each archive are to be created. These subdirectories are not created at once, but only when you perform any *CVS* operation on a certain CVS archive through the icons of the [=TITLE] folder. For example, if you specified #c:\work# as the working directory during installation of the [=TITLE] and you perform a *CVS* action by using the corresponding [.IDPNL_USAGE_USINGFOLDER archive folder] for an archive called *Odin32*, the subdirectory #c:\work\odin32# will be created automatically. .. ............................................................................. .4 CVS managment directories .. ............................................................................. .an IDPNL_USAGE_CVS_CVSDIRS . When you check out a *CVS* archive to your [.IDPNL_USAGE_CVS_WORKINGDIR working directory], you will notice that under each source directory there exists a directory named *CVS*, which contains three files. These files keep track of what versions of source files you have currently checked out, so that when you commit the changes, that you have made to the source files, *CVS*, knows what to modify in the archive. [=NOTE] .ul compact .at fc=red - *Do not modify the files in the *CVS* management directories.* It is likely that *CVS* cannot properly update your changes to the archive correctly, if these files contain invalid intformation, which may result in loss of data. .at More, a special directory *CVSROOT* exists directly under your *working directory*, which contains the administration database for the archive. These files are to change only by the [=NAME] Administrator. While you can check out and view these files, you won't have write access to commit changes for these files .. ............................................................................. .4 CVS archive modules .. ............................................................................. .an IDPNL_USAGE_CVS_MODULES . The administrator of a *CVS* archive can create administration modules for to ease the handling of large archives. You can imagine moduels being virtual directories, under which the administrator can group certain directories and single files or group of files together in modules, which can for example be checked out and updated in one operation. If you checkout a module, it will always appear as a subdirectory below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of that *CVS* archive. At the same time, each subdirectory already existing within an archive can as well be treaded as a module by specifying its pathname relative to the *working directory*. [=NOTE] .ul compact - Whenever you can perform *CVS* operations onto a single file, you always can perform them on subdirectories or modules, which will cause *CVS* to perform them on all files within and all files in directories below the specified subdirectory or module. - If you want to perform an operation on a complete *CVS* archive, execute the *CVS* command in the root directory of the archive and specify a single dot (placeholder for #current directory#). *CVS* will then recurse into all subdirectories and thus process the whole archive. .. ............................................................................. .4 Using CVS snapshots .. ............................................................................. .an IDPNL_USAGE_CVS_SNAPSHOTS . If you are accessing a CVS archive on the [=NAME] server for the first time or after a while, you may want to avoid to download all the (changed) files within the archive via *CVS* commands. Instead, you can use snapshots from the archive, that have been taken by the *CVS* administrator recently. Such files are provided as zip files on the *netlabs.org* FTP server. Using them requires to download that single snapshot file via FTP and unpacking it in your (empty !) working directory. In order to use the snapshot on your local harddisk, you only have to fix the CVS management directories within the directory structure by executing a simple command first. After that you can perform an update, which will need to fetch much fewer files from the archive directly via *CVS* than without using the snapshot. In order to use a snapshot of a *CVS* archive, perform the following steps: .ul compact - download the snapshot zip file from the [=NAME] server - open the [=TITLE] folder - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_WINDOW] .el - delete all files in the working directory. .at fc=red . [=NOTE] .ul compact - MAKE SURE THAT YOU HAVE COMMITTED ALL FILE CHANGES TO THE ARCHIVE BEFORE DELETING YOUR LOCAL FILES ! .at .el - [.IDPNL_WHAT_INFOZIP unzip] the snapshot zip file into the empty archive. - execute the command .sl compact - *cvsenv $FIX* .el . or execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_FIXSNAPSHOT] .el . in the [=TITLE] folder in order to make the snapshot be useable on your local disk. .. ............................................................................. .4 Global CVS options .. ............................................................................. .an IDPNL_USAGE_CVS_OPTIONS . In order to edit the global *CVS* options used by the [=TITLE], perform the following steps: .ul compact - open the [=TITLE] folder - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_CONFIGCVS] See the *CVS* reference sections for more information: .ul compact - [inf:cvs Default options and the ~/.cvsrc file] .. ----------------------------------------------------------------------------- .3 Using an archive folder .. ----------------------------------------------------------------------------- .an IDPNL_USAGE_USINGFOLDER . The [=TITLE] provides an archive folder for each source archive available on the [=NAME] server. Such a folder contains several icons for a quick and easy access to these archives, alowing you to perform most *CVS* commands without having to use the commandline. You may either enter the names of files and/or directories manually or drag&.drop them onto the icons within the archive folder. Nevertheless you can still do that (and for some complex operations, you have to do so) on a command line, for which an archive folder provides you with an icon for a command window, being completely setup for *CVS* access to that archive. In order to open an archive folder perform the following steps: .ul compact - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - and open the archive folder of the project, on which archive you want to perform *CVS* operations The following Workplace Shell objects are provided within an archive folder: .su H50 More, a shadow to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your computer is created. You can drag&.drop both local files and directories below the *working directory* to the objects in the archive folder. In this case ignore the prompt for file/modulenames. [=NOTE] .ul compact - Of course you will need to have an active internet connection in order to access the [=NAME]. See also .ul compact - [.IDPNL_USAGE_USINGARCHIVE] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 Login .mi IDPNL_INSTALL_WPSOBJ_LOGIN .4 Logout .mi IDPNL_INSTALL_WPSOBJ_LOGOUT .4 Checkout file .mi IDPNL_INSTALL_WPSOBJ_CHECKOUT .4 Fix Snapshot .mi IDPNL_INSTALL_WPSOBJ_FIXSNAPSHOT .4 View file log .mi IDPNL_INSTALL_WPSOBJ_VIEWLOG .4 Query file status .mi IDPNL_INSTALL_WPSOBJ_VIEWSTATUS .4 Add new file .mi IDPNL_INSTALL_WPSOBJ_ADDNEW .4 Update local files .mi IDPNL_INSTALL_WPSOBJ_UPDATE .4 Merge to local files .mi IDPNL_INSTALL_WPSOBJ_MERGE .4 Commit file changes .mi IDPNL_INSTALL_WPSOBJ_COMMIT .4 Tag file .mi IDPNL_INSTALL_WPSOBJ_TAG .4 Generate Change Report .mi IDPNL_INSTALL_WPSOBJ_REPORT .4 Remove file .mi IDPNL_INSTALL_WPSOBJ_REMOVE .4 View modules .mi IDPNL_INSTALL_WPSOBJ_MODULES .4 Window .mi IDPNL_INSTALL_WPSOBJ_WINDOW .. ............................................................................. .. ----------------------------------------------------------------------------- .3 Readonly CVS archive access operations .. ----------------------------------------------------------------------------- .an IDPNL_USAGE_RO . Most users will have readonly access to source archives on the [=NAME] server, as write access is restricted only to the developer of a program or some of the the developers joining the current development team of a larger project. With readonly access, you will only be able to checkout the current state of the project's source. The following sections apply to users with both readonly and read/write permissions: .su H50 See also .ul compact - [.IDPNL_USAGE_USINGFOLDER] - [.IDPNL_USAGE_RW] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 workflow for download of a CVS archive .. ............................................................................. .an IDPNL_USAGE_RO_WORKFLOW . If you just want to have a look at one of the *CVS* archive on the [=NAME] server, the workflow is as follows: .ul - [.IDPNL_USAGE_RO_LOGIN login] into a *CVS* archive of the [=NAME] server. - [.IDPNL_USAGE_RO_CHECKOUT checkout] and/or [.IDPNL_USAGE_RO_UPDATE update] a file from a *CVS* archive on the [=NAME]. In order to speed things up a little bit, you may want to use a [.IDPNL_USAGE_CVS_SNAPSHOTS snapshot] of the archive instead of downloading file by file with *CVS*. If you participate within a project, see also .ul compact - [.IDPNL_USAGE_RO_WORKFLOW] .. ............................................................................. .4 Logging into the CVS server .. ............................................................................. .an IDPNL_USAGE_RO_LOGIN . Before having access to a remote *CVS* archive, you'll have to login to the [=NAME] server. In order to login into a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, for which archive you want to login - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_LOGIN Login] [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs login* .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - If you have readonly access, specify the password #readonly# - If you have read/write access, specify the password being sent to you from your *CVS* archive administrator. - The password, that you specify, is being stored in the file #.cvspass# in the directory being specified as your home directory during the installation of the [=TITLE]. Unless you do a *CVS* logout, this stored password is used to perform *CVS* operations on that archive. It even remains stored and keeps being used, if you interrupt the internet connection or even reboot your system. See also .ul compact - [.IDPNL_USAGE_RO_LOGOUT] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 Logging out of the CVS server .. ............................................................................. .an IDPNL_USAGE_RO_LOGOUT . If you do not longer need access to a *CVS* archive, logout. In order to logout from a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, for which archive you want to login - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_LOGOUT Logout] [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs logout* .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - If you logout of an archive, the password will be deleted from the file #.cvspass# in the directory being specified as your home directory during the installation of the [=TITLE]. - If you log out and are not currently logged in, *CVS* will complain, that it cannot find the appropriate entry in #%HOME%\.cvspass#, as it is already deleted. See also .ul compact - [.IDPNL_USAGE_RO_LOGIN] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 Checkout source files .. ............................................................................. .an IDPNL_USAGE_RO_CHECKOUT . The checkout command will download some files or the whole contents of a *CVS* archive to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of a *CVS* archive. In order to checkout files from a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, of which archive you want to checkout files - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_CHECKOUT Checkout file] .el - specify one or more filenames or module names with the pathname relative to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your harddisk. If you want to checkout a specific revision, specify *-r* ## right before the filename(s). If you do not specify either file- or modulenames, the complete archive will be checked out. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs checkout* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - instead of manually entering the files when being prompted, you also drag&.drop files and directories below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory]. In this case just press enter, when the prompt for filenames appear. - Only the files, that are not already on your system or are outdated, are transferred via internet. - The date- and timestamps of the files represent always the point of time when you downloaded the files. This is due to the fact, that *CVS* does not rely on them. See also .ul compact - [.IDPNL_USAGE_RO_UPDATE] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 Update source files .. ............................................................................. .an IDPNL_USAGE_RO_UPDATE . The update command will download files, that have been modified in the *CVS* archive since you checked them out or updated them the last time, to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of a *CVS* archive. In order to update files from a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, of which archive you want to checkout files - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_UPDATE Update local files] .el - specify one or more filenames or module names with the pathname relative to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your harddisk If you do not specify either file- or modulenames, the complete archive will be updated. [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs update* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - instead of manually entering the files when being prompted, you also drag&.drop files and directories below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory]. In this case just press enter, when the prompt for filenames appear. - Only the files, that are not already on your system or are outdated, are transferred via internet. - The date- and timestamps of the files represent always the point of time when you downloaded the files. This is due to the fact, that *CVS* does not rely on them. See also .ul compact - [.IDPNL_USAGE_RO_CHECKOUT] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 view CVS log of source files .. ............................................................................. .an IDPNL_USAGE_RO_VIEWLOG . You can view the log for all files in the archive, that includes the revision history and tags being given to certain revisions for each file. In order to view the log for files from a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, of which archive you want to checkout files - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_VIEWLOG View file log] .el - specify one or more filenames or module names with the pathname relative to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your harddisk [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs log* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - instead of manually entering the files when being prompted, you also drag&.drop files and directories below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory]. In this case just press enter, when the prompt for filenames appear. - If you do not specify either file- or modulenames, the log will be fetched for the complete archive, which will mostly take some amount of time. See also .ul compact - [.IDPNL_USAGE_RO_CHECKOUT] - [.IDPNL_USAGE_RO_UPDATE] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 view CVS status of source files .. ............................................................................. .an IDPNL_USAGE_RO_VIEWSTATUS . You can view the status for (all) local files in the archive, so that you can determine, which files you have changed locally or which are outdated compared to the archive. In order to view the change status for files from a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, of which archive you want to checkout files - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_VIEWSTATUS Query file status] .el - specify one or more filenames or module names with the pathname relative to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your harddisk [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs status* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - instead of manually entering the files when being prompted, you also drag&.drop files and directories below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory]. In this case just press enter, when the prompt for filenames appear. - If you do not specify either file- or modulenames, the status will be fetched for all files of the complete archive, which will mostly take some amount of time. The file status will report both the revisions of the file on your computer and that of the file in the archive. More, it reports the file status concerning the *CVS* operation, that might be reuired for either retrieving a more actual version or for commiting your changes to the archive. Here is a little excerpt from the *CVS* reference: .p. tsize=5 bold .. - Up-to-date = The file is identical with the latest revision in the repository for the branch in use. .. - Locally Modified = You have edited the file, and not yet committed your changes. .. - Locally Added = You have added the file with add, and not yet committed your changes. .. - Locally Removed = You have removed the file with remove, and not yet committed your changes. .. - Needs Checkout = Someone else has committed a newer revision to the repository. The name of this option is slightly misleading; you will ordinarily use update rather than checkout to get that newer revision. .. - Needs Patch = Like Needs Checkout, but the *CVS* server will send a patch rather than the entire file. Sending a patch or sending an entire file accomplishes the same thing. .. - Needs Merge = Someone else has committed a newer revision to the repository, and you have also made modifications to the file. .. - File had conflicts on merge = This is like *Locally Modified*, except that a previous update command gave a conflict. If you have not already done so, you need to resolve the conflict as described in Conflicts example. .. - Unknown = CVS doesn't know anything about this file. For example, you have created a new file or directory and have not run the *CVS* command add. See also .ul compact - [.IDPNL_USAGE_RO_CHECKOUT] - [.IDPNL_USAGE_RO_UPDATE] - [.IDPNL_USAGE_RW_COMMIT] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 View archive modules .. ............................................................................. .an IDPNL_USAGE_RO_VIEWMODULES . In order to view the modules currently defined for a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, for which archive you want to login - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_MODULES View modules] [=NOTE] .ul compact - The list being displayed reflects the contents of the file #CVSROOT\modules# below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of that *CVS* archive. Make sure that you update that file before reyling on the output. See also .ul compact - [.IDPNL_USAGE_RO_LOGOUT] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 archive Window .. ............................................................................. .an IDPNL_USAGE_RO_WINDOW . Although the [=TITLE] provides an easy to use interface for to handle all *CVS* operations for you, in special cases it might be easier to execute the *CVS* manually on the commandline. For this the [=TITLE] offers an icon, which opens an OS/2 window having setup the complete environment, which is needed to access an archive on the [=NAME] server. You can perform all *CVS* operations within this window. In order to open an *archive OS/2 window* for to access a *CVS* archive on the [=NAME] server via commandline, perform the following steps: .ul compact - make sure that you have an active connection to the internet, if you want to perform remote *CVS* operations within the window - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, which you want to access - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_WINDOW OS/2 window] .. ----------------------------------------------------------------------------- .3 Read/Write CVS archive access operations .. ----------------------------------------------------------------------------- .an IDPNL_USAGE_RW . Developers participating with a project will have (partial) readwrite access to source archives on the [=NAME] server. With such read/write access, they will be able to commit changes to source files either within a whole archive or only within certain directories of an archive, where access restrictions are setup by the [=NAME] Administrator. Beside the sections for [.IDPNL_USAGE_RO] also the following sections apply to users with read/write permissions: .su H50 See also .ul compact - [.IDPNL_USAGE_USINGFOLDER] - [.IDPNL_USAGE_RO] - [.IDPNL_USAGE_RO_WINDOW] - [.IDPNL_WHAT_CVS] .. ............................................................................. .4 workflow for modifications within an CVS archive .. ............................................................................. .an IDPNL_USAGE_RW_WORKFLOW . Developers with read/write access have to follow a certain path in order to modify files in a *CVS* archive on the [=NAME] server. The workflow is as follows: .ul - [.IDPNL_USAGE_RO_LOGIN login] into a *CVS* archive of the [=NAME] server. - [.IDPNL_USAGE_RO_CHECKOUT checkout] and/or [.IDPNL_USAGE_RO_UPDATE update] a file from a *CVS* archive on the [=NAME], if you need to modify a file already existing within the archive. Skip this point, when you need to create a new file. In order to speed things up a little bit, you may want to use a [.IDPNL_USAGE_CVS_SNAPSHOTS snapshot] of the archive instead of downloading file by file with *CVS*. - create or edit the appropriate files with any program. - If you have created a new file or directory, [.IDPNL_USAGE_RW_ADDNEW add] the file or directory to the archive now. Make sure, that you disable keyword expansion for binary files here by specifying the option #-kb# right before the filename. - [.IDPNL_USAGE_RW_MERGE merge] your changes with the changes, that other developers might have committed meanwhile to the archive, and check, if the merged source(s) still work. If you are not sure, wether a file needs a merge or not, request the [.IDPNL_USAGE_RO_VIEWSTATUS CVS file status] for this file. - [.IDPNL_USAGE_RW_COMMIT commit] your changes to the *CVS* archive on the [=NAME] - [.IDPNL_USAGE_RW_TAG tag] the created or modified file(s) with a label, so that others can easily checkout your modifications, no matter how much files you have changed. Ask your [=NAME] administrator for naming conventions for tag names. - [.IDPNL_USAGE_RW_REPORT Generate a change report] and send it to the change report database via email in order to ease the CVS maintainers job to integrate your changes into a new release build. It depends on the project team, wether your project uses such reports or not. If your project team decides not to use change reports, simply ignore this part. .. ............................................................................. .4 add new source files .. ............................................................................. .an IDPNL_USAGE_RW_ADDNEW . Developers often need to be able to add new files and directories to the archive, using the add command. .at fc=red [=NOTE] For this you need to have write access to the *CVS* archive .at In order to add a new file or directory to a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, of which archive you want to add files or directories to - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_ADDNEW Add new file] .el - specify one or more filenames relative to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your harddisk [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs add* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - instead of manually entering the files when being prompted, you also drag&.drop files and directories below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory]. In this case just press enter, when the prompt for filenames appear. .at fc=red - Make sure, that you disable keyword expansion for binary files here by specifying the option #-kb# right before the filename .at .. ............................................................................. .4 merge local files .. ............................................................................. .an IDPNL_USAGE_RW_MERGE . If another developer has committed changes to a file, while you have had checked it out and changed it, you have to merge the changes of others into your version of the file before committing your changes. After *CVS.* merged the changes of the other developers to your local file, you have to make sure, that it still works. (compiles etc.). .at fc=red [=NOTE] .ul compact - For this you need to have write access to the *CVS* archive .at In order to merge file changes in a *CVS* archive on the [=NAME] server to your local file, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, to which archive you have added files or directories to - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_MERGE *&IDH_IDPNL_INSTALL_WPSOBJ_MERGE.*] .el - specify one or more filenames relative to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your harddisk [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs update* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - instead of manually entering the files when being prompted, you also drag&.drop files and directories below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory]. In this case just press enter, when the prompt for filenames appear. - If you are not sure, wether a file needs a merge or not, you can query the [.IDPNL_USAGE_RO_VIEWSTATUS CVS file status] for this file before. - Althouth there exist two icons for updating a local file and merging to a local file within the [=TITLE] folder, they actually execute the same *CVS* command, namely *update*. .. ............................................................................. .4 commit changes to the CVS server .. ............................................................................. .an IDPNL_USAGE_RW_COMMIT . After having [.IDPNL_USAGE_RW_ADDNEW added] new files and directories or modified locally [.IDPNL_USAGE_RO_CHECKOUT checked out] files , you have to commit the changes to the *CVS* archive, otherwise these changes will stay on your local harddisk and noone will see them within the archive. .at fc=red [=NOTE] .ul compact - For committing file changes you need to have write access to the *CVS* archive .at In order to commit changes to a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, to which archive you have added files or directories to - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_COMMIT *&IDH_IDPNL_INSTALL_WPSOBJ_COMMIT.*] .el - specify one or more filenames relative to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your harddisk [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs commit* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - instead of manually entering the files when being prompted, you also drag&.drop files and directories below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory]. In this case just press enter, when the prompt for filenames appear. .. ............................................................................. .4 tag source files .. ............................................................................. .an IDPNL_USAGE_RW_TAG . After having [.IDPNL_USAGE_RW_COMMIT committed] file changes, you should tag the created or modified file(s) with a label, so that others can easily checkout your modifications, no matter how much files you have changed. .at fc=red [=NOTE] .ul compact - For tagging files you need to have write access to the *CVS* archive .at Ask your [=NAME] administrator for naming conventions for tag names. Normally, only the owner of the archive is allowed to freely use all sorts of tag names in order to protect tags for release versions from being moved by accident. Developers participating the project are mostly restricted to use only tag names preceeded by their user id. In order to tag files within a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, of which archive you want to tag files in - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_TAG *&IDH_IDPNL_INSTALL_WPSOBJ_TAG.*] .el - specify the tag name (see comment above for naming conventions) and the #-d# option, if you want to delete a tag - specify one or more filenames relative to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your harddisk [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs tag* # # .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - instead of manually entering the files when being prompted, you also drag&.drop files and directories below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory]. In this case just press enter, when the prompt for filenames appear. - tag operations need not to be commited, as they are directly performed on the CVS archive .. ............................................................................. .4 generate a change report .. ............................................................................. .an IDPNL_USAGE_RW_REPORT . After having [.IDPNL_USAGE_RW_COMMIT committed] file changes, and [.IDPNL_USAGE_RW_TAG tagged] the changed files, you should report this change to the [=NAME] change report database, if your project makes use of them. It depends on the project team, wether your project uses such reports or not. If your project team decides not to use change reports, simply ignore this part. In order to create a change report for a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, of which archive you want to tag files in - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_REPORT *&IDH_IDPNL_INSTALL_WPSOBJ_REPORT.*] Now wait for the internet browser to come up with the change report form. Fill out the entry fields with the appropriate information and submit the form in order to send the change report via email. [=NOTE] .ul compact - You will need to have an active internet connection in order to be able to send an email. - Executing this icon has the same effect like executing the command .sl compact - *cvsreport* .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. .. ............................................................................. .4 remove source files .. ............................................................................. .an IDPNL_USAGE_RW_REMOVE . From while to while you may need to remove files from the archive, because it has become obsolete. In fact, if you call *CVS* to remove a file, it is only marked as being removed, but the file still remains in the archive in order to keep older versions complete. .at fc=red [=NOTE] .ul compact - For marking files as being removed you need to have write access to the *CVS* archive .at In order to mark files as being removed from a *CVS* archive on the [=NAME] server, perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - open the folder called *Current netlabs.org Archives* - open the archive folder of the project, of which archive you want to tag files in - execute the icon .sl compact - [.IDPNL_INSTALL_WPSOBJ_REMOVE *&IDH_IDPNL_INSTALL_WPSOBJ_REMOVE.*] .el - specify one or more filenames relative to the [.IDPNL_USAGE_CVS_WORKINGDIR working directory] of the archive on your harddisk [=NOTE] .ul compact - Executing this icon has the same effect like executing the command .sl compact - *cvs remove* ## .el . within an [.IDPNL_USAGE_RO_WINDOW archive Window]. - instead of manually entering the files when being prompted, you also drag&.drop files and directories below the [.IDPNL_USAGE_CVS_WORKINGDIR working directory]. In this case just press enter, when the prompt for filenames appear. - Remove operations need not to be commited, as they are directly performed on the CVS archive .. ============================================================================= .2 How can I ... ? .. ============================================================================= .an IDPNL_HOW . [=TOPICS] .su V30 .. ----------------------------------------------------------------------------- .3 How can I solve the 'Too many open files' problem ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_SOLVEOPENFILES . If *CVS* displays the message "To many open files", you must increase the default file handle limit of the [.IDPNL_WHAT_EMXRUNTIME]. In order to do so, add the following environment variable to your CONFIG.SYS: .sl compact - *SET EMXOPT=-c -n -h1024* where :parml compact tsize=10 break=none. - *-c* = disables core dumps caused by signals and exceptions (they are only really useful if you use debug versions of a software). .. - *-n* = Suppress popups for exceptions. As emx.dll displays an appropriate error message, popups are not required. .. - *-h1024* = Set OS/2 file handle limit for CVS (and other EMX based programs) to 1024, thus eliminating your current problem. The number must be between 10 and 65536, possibly CVS will also run with a smaller value. See also the file *doc\emxrt.doc* of the [.IDPNL_WHAT_EMXRUNTIME] for further details on values of the *EMXOPT* environment variable. .. ----------------------------------------------------------------------------- .3 How can I update the archive list ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_UPDATELIST . In order to update the list file from the FTP server of *netlabs.org*, just perform the following steps: .ul compact - make sure that you have an active connection to the internet - open the [=TITLE] folder - execute the icon .sl compact - *[.IDPNL_INSTALL_WPSOBJ_UPDATELIST]* See also .ul compact - [.IDPNL_USAGE_LIST_UPDATE] .. ----------------------------------------------------------------------------- .3 How can I view the archive list ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_VIEWLIST . In order to view the archives list file, that is being stored on your computer, perform the following steps: .ul compact - open the [=TITLE] folder - execute the icon .sl compact - *[.IDPNL_INSTALL_WPSOBJ_VIEWLIST]* See also .ul compact - [.IDPNL_USAGE_LIST] - [.IDPNL_USAGE_LIST_UPDATE] .. ----------------------------------------------------------------------------- .3 How can I use an archive folder ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_USEFOLDER .mi IDPNL_USAGE_USINGFOLDER .. ----------------------------------------------------------------------------- .3 How can I login into a netlabs.org CVS archive ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_LOGIN .mi IDPNL_USAGE_RO_LOGIN .. ----------------------------------------------------------------------------- .3 How can I use a netlabs.org CVS archive .. ----------------------------------------------------------------------------- .an IDPNL_HOW_USINGARCHIVE .mi IDPNL_USAGE_USINGARCHIVE .. ----------------------------------------------------------------------------- .3 How can I download source from a netlabs.org CVS archive ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_DOWNLOADSOURCE .mi IDPNL_USAGE_RO_WORKFLOW .. ----------------------------------------------------------------------------- .3 How can I use a CVS snapshot from a netlabs.org CVS archive ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_USESNAPSHOTS .mi IDPNL_USAGE_CVS_SNAPSHOTS .. ----------------------------------------------------------------------------- .3 How can I modify source within an netlabs.org CVS archive ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_MODIFYSOURCE .mi IDPNL_USAGE_RW_WORKFLOW .. ----------------------------------------------------------------------------- .3 How can I perform CVS operations onto a netlabs.org CVS archive ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_CVSACTIONS .mi IDPNL_USAGE_RO_WINDOW .. ----------------------------------------------------------------------------- .3 How can I generate a change report ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_REPORT .mi IDPNL_USAGE_RW_REPORT .. ----------------------------------------------------------------------------- .3 How can I modify global CVS options ? .. ----------------------------------------------------------------------------- .an IDPNL_HOW_CONFIGCVS .mi IDPNL_USAGE_CVS_OPTIONS .. ============================================================================= .2 Limitations .. ============================================================================= .an IDPNL_LIMITATIONS . The following limitations apply to the current version of [=TITLE]: .ul .. - directory names of and within *CVS* archives may currently not include blanks. However this restriction does not exist for filenames. .. - This packages is available only in english. This is due to the reason, that programmers mostly understand english and that development tools, such as the required [.IDPNL_WHAT_CVS *Concurrent Versions System* (CVS)] are also only available in english. .. - the [=TITLE] does not address the need of reserved checkouts, neither within the WPS folder nor in this online document. Neither the *watch* nor the *edit* command is directly supported by the [=TITLE] folder, because this would need at least four more icons and make the folder looking rather confused. .. See the *CVS* reference sections for more information: .ul compact - [inf:cvs Multiple developers] - [inf:cvs Telling CVS to watch certain files] - [inf:cvs How to edit a file which is being watched] .. ============================================================================= .2 Revision history .. ============================================================================= .an IDPNL_REVISIONS . [=TOPICS] .su V30 .. ----------------------------------------------------------------------------- .3 file__id.diz .. ----------------------------------------------------------------------------- .an IDPNL_FILE_ID_DIZ . .fo off .textinclude file_id.diz .fo on .. ----------------------------------------------------------------------------- .3 Version 1.10 .. ----------------------------------------------------------------------------- .an IDPNL_REVISION_HISTORY_110 . _*New:*_ .ul - put NOSA under the [.IDPNL_LEGAL_CDDL Common Development and Distribution License (CDDL)] - joined with NOSA Administrator into one WPI package with same version number - adapted name change from *OS/2 Netlabs* to *netlabs.org* - moved the INF files to a subdirectors INF within the installation of [=TITLE]. Make sure to delete the old INF files from the main directory after having upgraded. - removed the feature of generating an online bugreport, as it was intended to be tested withthe [http://odin.netlabs.org Odin] project, but never used (the required infrastructure never has been setup). - within the whole package updated the email address of the author - modified the [.IDPNL_INSTALL_INSTALL] to - not use the "lock icon" feature anymore - use a new modified watermark alike background bitmap, and that for all generated folders .. ----------------------------------------------------------------------------- .3 Version 1.06 .. ----------------------------------------------------------------------------- .an IDPNL_REVISION_HISTORY_106 . _*New:*_ .ul - all icons with a project folder do not longer use the default command processor in order to execute *cvsenv.cmd*, but always *CMD.EXE*. This was necessary, because certain command processor replacements have serious problems with the dollar sign being used within cvsenv commands. For example, bash as a unix-style command processor treats words beginning with a dollar sign as environment variables... .. - [.IDPNL_USAGE_LIST] is not longer being fetched via functions of the RXFTP.DLL supplied with the TCP/IP package of OS/2, but with the automated mode of plain FTP.EXE instead. . This is a workaround for that fetching this file with the RXFTP.DLL coming with WARP Server for e-business did not work properly. Another workaround is to use RXFTP.DLL from plain WARP 4 client with old versions of [=TITLE]. _*Fixed:*_ .ul - updated the hobbes link to the [.IDPNL_WHAT_EMXRUNTIME] and removed the outdated link to OS/2 Supersite. .. ----------------------------------------------------------------------------- .3 Version 1.05 .. ----------------------------------------------------------------------------- .an IDPNL_REVISION_HISTORY_105 . _*New:*_ .ul - added new sections to this book about the [.IDPNL_WHAT_EMXRUNTIME], wich is a prerequisite for the [.IDPNL_WHAT_CVS]. . See .ul compact - [.IDPNL_WHAT_EMXRUNTIME] - [.IDPNL_PREREQUISITES] - [.IDPNL_HOW_SOLVEOPENFILES] .el - You do not longer need to write the *cvsenv* commands in uppercase. More, you can use abbreviations, mostly with only one letter behind the dollar sign (e.g. $L or $list instead odf $LIST). . Take care though, where two commands start with the same letter: in order to distinct between such commands, you may have to specify more than one letter of the command name. Execute .sl compact - *cvsenv /?* .el . in order to get an overview of all commands. - enhanced *cvsenv* so that you now can use multiple hosts (you might have setup another [=SHORTNAME]-like server for test purposes etc.). Specify multiple hosts separated by commas when the [.IDPNL_INSTALL_INSTALL installation program] asks for the [=SHORTNAME] server. . See also .ul compact - [.IDPNL_USAGE_LIST_UPDATE] .el . - added default .cvsrc file (CVS options), which is installed, if none is present .. - added the following client features .ul compact - [.IDPNL_USAGE_RW_REPORT generate a change report] and send it to the change report database via email. It can be used for projects only though, that the project team has setup such a feature - [.IDPNL_USAGE_CVS_SNAPSHOTS fix a snapshot], that has been previously unpacked in the working directory. .el . - added following icons to the [.IDPNL_USAGE_USINGFOLDER archive folder]: .ul compact - [.IDPNL_INSTALL_WPSOBJ_REPORT] - [.IDPNL_INSTALL_WPSOBJ_FIXSNAPSHOT] .. ----------------------------------------------------------------------------- .3 Version 1.04 .. ----------------------------------------------------------------------------- .an IDPNL_REVISION_HISTORY_104 . First public release .. ============================================================================= .2 Trademarks .. ============================================================================= .an IDPNL_TRADEMARKS . The following trademarks are used in this online help file: .ul compact - *OS/2* is a trademark of IBM Corporation. - *eComStation* is a trademark of Serenity Systems International .. ============================================================================= .2 Credits .. ============================================================================= .an IDPNL_CREDITS . [=TOPICS] .su V30 .. ----------------------------------------------------------------------------- .3 General credits .. ----------------------------------------------------------------------------- .an IDPNL_CREDITS_GENERAL . Credits go to: .ul - all people having helped the development of this program. - all developers, who share and who will share their code through the [=NAME]. You all help the current and wannabe developers of the OS/2 community building better code, participating within internet projects and bringing OS/2 forward with new programs, that we all need. - all developers being ivolved in making .ul compact - [.IDPNL_WHAT_CVS] - [.IDPNL_WHAT_INFOZIP] - [.IDPNL_WHAT_EMXRUNTIME] Without these programs, the [=NAME] would not have been possible.