[interchange-cvs] [SCM] Interchange branch, master, updated. c996881100a2f0c5d19439d6bc2e629c468f95ec

Jon Jensen interchange-cvs at icdevgroup.org
Sat May 23 21:28:34 UTC 2009


This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Interchange".

The branch, master has been updated
       via  c996881100a2f0c5d19439d6bc2e629c468f95ec (commit)
       via  a74ec45a18a9cd6103da79f334654a08cc403dbd (commit)
       via  5508b8627720d8858964b1143ae87ffe77e90d46 (commit)
      from  66bc280c5755560032252857f5c013346b9c6e6f (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit c996881100a2f0c5d19439d6bc2e629c468f95ec
Author: Jon Jensen <jon at endpoint.com>
Date:   Sat May 23 15:27:55 2009 -0600

    Reference file in tree, not cvsweb anymore

commit a74ec45a18a9cd6103da79f334654a08cc403dbd
Author: Jon Jensen <jon at endpoint.com>
Date:   Sat May 23 15:27:38 2009 -0600

    s/CVS/CSV/ to fix typo.

commit 5508b8627720d8858964b1143ae87ffe77e90d46
Author: Jon Jensen <jon at endpoint.com>
Date:   Sat May 23 15:26:28 2009 -0600

    Rename README.cvs to README-DEVELOPMENT
    
    Since we're using Git now, show that in the file name. Not using a
    dot-suffix to avoid confusing people with .git (or anything else).

-----------------------------------------------------------------------

Summary of changes and diff:
 MANIFEST                             |    2 +-
 Makefile.PL                          |    2 +-
 README                               |   24 +++--
 README-DEVELOPMENT                   |  108 ++++++++++++++++++++++
 README.cvs                           |  167 ----------------------------------
 README.debian                        |    5 +-
 SPECS/interchange.spec               |    4 +-
 configure                            |    2 +-
 debian/interchange.docs              |    4 +-
 dist/lib/UI/ichelp.txt               |    2 +-
 extensions/benchtimes/bin/benchtimes |    2 +-
 11 files changed, 135 insertions(+), 187 deletions(-)
 create mode 100644 README-DEVELOPMENT
 delete mode 100644 README.cvs

diff --git a/MANIFEST b/MANIFEST
index 38dc9f1..9579b6f 100644
--- a/MANIFEST
+++ b/MANIFEST
@@ -1188,7 +1188,7 @@ Makefile.PL
 MANIFEST			This list of files
 MANIFEST.SKIP
 README
-README.cvs
+README-DEVELOPMENT
 README.debian
 README.rpm-dist
 relocate.pl
diff --git a/Makefile.PL b/Makefile.PL
index e28fdc3..ec81b8c 100644
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -154,7 +154,7 @@ sub copyright_prompt {
 
  Interchange V$VERSION
  
- Copyright (C) 2002-2008 Interchange Development Group.
+ Copyright (C) 2002-2009 Interchange Development Group.
  Copyright (C) 1996-2002 Red Hat, Inc.
  Interchange is free under the terms of the GNU General Public License.
 
diff --git a/README b/README
index b010ecd..10f96d2 100644
--- a/README
+++ b/README
@@ -4,7 +4,7 @@
 
 Interchange 5.7.1
 
-Copyright (C) 2002-2008 Interchange Development Group
+Copyright (C) 2002-2009 Interchange Development Group
 Copyright (C) 1996-2002 Red Hat, Inc.
 
 Originally based on Vend 0.2 and 0.3, copyright 1995-96 by Andrew M. Wilcox.
@@ -47,19 +47,24 @@ Perl with an absolute path to the Perl binary, such as
 
 More information is in the following files and directories:
 
-LICENSE          The text of the GNU General Public License (GPL), under which
-                 the Interchange software is distributed.
+LICENSE
+The text of the GNU General Public License (GPL), under which the Interchange
+software is distributed.
 
-README.rpm-dist  Notes on using Interchange when installed from RPM packages.
+README.rpm-dist
+Notes on using Interchange when installed from RPM packages.
 
-README.debian    Notes on using Interchange when installed from Debian packages.
+README.debian
+Notes on using Interchange when installed from Debian packages.
 
-README.cvs       How to access the CVS repository to track ongoing development.
+README-DEVELOPMENT
+How to access the Git repository to track ongoing development.
 
-WHATSNEW-*       Changes per specified version family.
+WHATSNEW-*
+Changes per specified version family.
 
-UPGRADE          Instructions on how to upgrade from an earlier Interchange
-                 version.
+UPGRADE
+Instructions on how to upgrade from an earlier Interchange version.
 
 -----------------------------------------------------------------------------
 
@@ -150,7 +155,6 @@ formats. This and other information is available at the Interchange home on
 the web:
 
 http://www.icdevgroup.org/
-http://www.icdevgroup.org/xmldocs/
 
 -----------------------------------------------------------------------------
 
diff --git a/README-DEVELOPMENT b/README-DEVELOPMENT
new file mode 100644
index 0000000..cb54f6d
--- /dev/null
+++ b/README-DEVELOPMENT
@@ -0,0 +1,108 @@
+------------------------------------------------------------------------------
+
+                   Tracking Interchange development in Git
+
+------------------------------------------------------------------------------
+
+If you don't want to wait for an official release, you can use Git to follow
+the latest Interchange development.
+
+WARNING: There may be bugs introduced at any time! Thoroughly test any changes
+before incorporating. Better yet, don't use Git changes for anything but
+fixing relevant bugs, and run the latest stable release.
+
+
+Browse Git tree online
+----------------------
+
+To browse the Interchange Git repository online, visit:
+
+http://git.icdevgroup.org/interchange/
+
+
+Clone a local copy
+------------------
+
+See instructions on cloning and working with a local Git working copy at:
+
+http://www.icdevgroup.org/i/dev/download
+
+
+Make a distribution tar file
+----------------------------
+
+It's best to build a distribution tar file to install from, rather than
+installing straight from your Git working copy. To do so:
+
+	$ cd interchange
+	$ perl Makefile.PL nocopy
+	Writing Makefile for Interchange
+	$ make tardist
+    # much output ...
+	$ ls interch*.tar.gz
+	interchange-5.7.1.tar.gz
+
+
+Unpack and install
+------------------
+
+Unpack the tar file and install as normal. See the README file and other
+documentation for help. You should already be familiar with the Interchange
+developer website at:
+
+	http://www.icdevgroup.org/
+
+Make sure you don't put your Git working copy at $HOME/interchange
+and then install on top of it, since $HOME/interchange is the default
+install directory.
+
+
+Updating
+--------
+
+Follow development discussions by joining the interchange-announce and
+interchange-users mailing lists.
+
+Keep track of ongoing code changes by joining the interchange-cvs mailing
+list, or watching the interchange/interchange repository in GitHub.
+
+In many cases, the major differences in the distribution will be easily
+updateable. You can copy any changed files directly to these library
+directories:
+
+	lib/Vend    (and all subdirectories)
+	lib/UI      (and all subdirectories)
+
+You should check the files:
+
+	catalog_after.cfg     (infrequently updated)
+	catalog_before.cfg    (frequently updated)
+	interchange.cfg.dist  (infrequently updated)
+	usertag/*             (infrequently updated)
+
+Finally, you should check differences in the bin/* files. While they
+are not as frequently updated as the lib/* files, they do change. Run
+diffs against the source files in scripts/*.PL, or do another install
+to a blank directory and do a diff to that.
+
+
+Keeping the catalog in sync
+---------------------------
+
+If you are patterning your order methods after one of the template
+catalogs, you will want to check the products/*.txt and products/*.asc
+files for changes. In particular, mv_metadata.asc is used to format
+and present quite a few things in the user interface. You may have
+to merge the databases, but there is an automated admin UI facility
+that can help you do this.
+
+
+Troubleshooting
+---------------
+
+If you get a complaint that a "file is not found" when trying to do a
+'make tardist' or 'make dist', that means your MANIFEST file is out of
+sync with the current codebase. Just do:
+
+	rm MANIFEST
+	make manifest
diff --git a/README.cvs b/README.cvs
deleted file mode 100644
index 1e648c6..0000000
--- a/README.cvs
+++ /dev/null
@@ -1,167 +0,0 @@
-------------------------------------------------------------------------------
-
-                   Tracking Interchange development in CVS
-
-------------------------------------------------------------------------------
-
-If you don't want to wait for an official release, you can use anonymous
-CVS to follow the latest Interchange development.
-
-WARNING: There may be bugs introduced at any time! Thoroughly test any
-changes before incorporating. Better yet, don't use CVS changes for
-anything but fixing present bugs, and run the latest release.
-
-
-Browse CVS tree online
-----------------------
-
-To browse Interchange CVS contents online, simply point your web
-browser to http://www.icdevgroup.org/cgi-bin/cvsweb/interchange/ .
-
-
-Check-out a local copy
-----------------------
-
-You need to have CVS installed on your system, to begin with. It
-comes pre-installed on most free Unix-like systems if you selected
-the development tools at install time. See http://www.cvshome.org/
-for download locations if you don't have it.
-
-If you are already an experienced CVS user, the information is:
-
-	CVSROOT   :pserver:cvs at cvs.icdevgroup.org:/var/cvs
-	password  (none)
-	module    interchange
-
-If you are not experienced with CVS, it is still easy to get going by
-following these steps. First, choose a place to put the local copy you're
-going to check out. A good choice is somewhere in your home directory,
-probably a src/ subdirectory:
-
-	$ cd
-	$ mkdir src
-	$ cd src
-	$ cvs -z3 -d :pserver:cvs at cvs.icdevgroup.org:/var/cvs checkout -P interchange
-
-It will take a while, as there are several megabytes of files to download.
-
-
-Make a distribution tar file
-----------------------------
-
-If it is your first time installing Interchange from the CVS, you will want
-to make a distribution tar file:
-
-	$ cd interchange
-	$ perl Makefile.PL nocopy
-	Writing Makefile for Interchange
-	$ make tardist
-	/usr/local/bin/perl -I/YOUR/PERL/LIB -MExtUtils::Manifest=manicopy,maniread \
-	-e "manicopy(maniread(),'interchange-4.9.x', 'best');"
-	mkdir interchange-5.0.0
-	mkdir interchange-5.0.0/dist
-	....
-	$ ls interch*.tar.gz
-	interchange-5.0.0.tar.gz
-
-
-Unpack and install
-------------------
-
-Unpack the tar file and install as normal. See the README file and other
-documentation for help. You should already be familiar with the Interchange
-developer website at:
-
-	http://www.icdevgroup.org/
-
-Make sure you don't check out your CVS copy into $HOME/interchange
-and then install on top of it, since $HOME/interchange is the default
-install directory.
-
-
-Checking for differences
-------------------------
-
-If you want to see how your current working files compare to the versions
-you checked out from the repository, cd into your checked out CVS copy and
-do:
-
-	cvs diff | less
-
-
-Updating
---------
-
-To update the distribution, change to your checked out CVS directory
-(e.g. src/interchange), and then run:
-
-	$ cvs update -Pd
-	U MANIFEST
-	U WHATSNEW
-	....
-
-In many cases, the major differences in the distribution will be easily
-updateable. You can copy any changed files directly to these library
-directories:
-
-	lib/Vend    (and all subdirectories)
-	lib/UI      (and all subdirectories)
-
-You should check the files:
-
-	catalog_after.cfg     (infrequently updated)
-	catalog_before.cfg    (frequently updated)
-	interchange.cfg.dist  (infrequently updated)
-	usertag/*             (infrequently updated)
-
-Finally, you should check differences in the bin/* files. While they
-are not as frequently updated as the lib/* files, they do change. Run
-diffs against the source files in scripts/*.PL, or do another install
-to a blank directory and do a diff to that.
-
-
-Keeping the catalog in sync
----------------------------
-
-If you are patterning your order methods after one of the template
-catalogs, you will want to check the products/*.txt and products/*.asc
-files for changes. In particular, mv_metadata.asc is used to format
-and present quite a few things in the user interface. You may have
-to merge the databases, but there is an automated admin UI facility
-that can help you do this.
-
-
-Troubleshooting
----------------
-
-If you get a complaint that a "file is not found" when trying to do a
-'make tardist' or 'make dist', that means your MANIFEST file is out of
-sync with the current codebase. Just do:
-
-	rm MANIFEST
-	make manifest
-
-
-More on CVS
------------
-
-It is highly recommended that you create a .cvsrc file in your home
-directory to automatically use common options such as these:
-
-	cvs -z3 -q
-	diff -u
-	update -Pd
-	checkout -P
-
-This directs CVS to (1) automatically compress all data communicated
-between you and our server (saving bandwidth) and be quiet (printing
-out fewer diagnostic messages); (2) show context-sensitive, recursive
-diffs; (3) prune empty directories and create any new directories added
-to the repository since your checkout; and (4) prune empty directories
-during your checkouts.
-
-Please see the CVS website for complete documentation:
-
-	http://www.cvshome.org/
-
-
diff --git a/README.debian b/README.debian
index c9fbf58..30763c3 100644
--- a/README.debian
+++ b/README.debian
@@ -51,9 +51,10 @@ Other Notes
   /bin/false and the password for this user will be disabled. Use 
   su -s /bin/sh if you need to become the Interchange user.
 
-CVS
+Git
 ===
 
-You can build Debian packages directly from CVS with the following commmand:
+You can build Debian packages directly from a Git working copy with the
+following commmand:
 
 dpkg-buildpackage -rfakeroot -uc -us
diff --git a/SPECS/interchange.spec b/SPECS/interchange.spec
index 8784055..c4c9c12 100644
--- a/SPECS/interchange.spec
+++ b/SPECS/interchange.spec
@@ -184,7 +184,7 @@ done
 # Remove admin UI images now that they're in the HTML doc root
 %__rm -rf $RPM_BUILD_ROOT$ICBASE/share/interchange-5
 
-# Clean up empty placeholder files used to keep CVS from pruning away
+# Clean up empty placeholder files used to keep Git from pruning away
 # otherwise empty directories
 find $RPM_BUILD_ROOT -type f -name .empty \( -size 0b -o -size 1b \) -exec %__rm -f \{\} \;
 
@@ -253,7 +253,7 @@ exit 0
 %doc LICENSE
 %doc README
 %doc README.rpm-dist
-%doc README.cvs
+%doc README-DEVELOPMENT
 %doc UPGRADE
 %doc WHATSNEW*
 %config(noreplace) %{_sysconfdir}/logrotate.d/interchange
diff --git a/configure b/configure
index 8581c51..8b10661 100755
--- a/configure
+++ b/configure
@@ -6,7 +6,7 @@ cat <<EOF
 
  Interchange
 
- Copyright 2002-2008 Interchange Development Group (http://www.icdevgroup.org/)
+ Copyright 2002-2009 Interchange Development Group (http://www.icdevgroup.org/)
  Copyright 1996-2002 Red Hat, Inc.
 
  Interchange was originally based on Vend 0.2 and 0.3
diff --git a/debian/interchange.docs b/debian/interchange.docs
index eca098b..b6482b5 100644
--- a/debian/interchange.docs
+++ b/debian/interchange.docs
@@ -1,9 +1,11 @@
 README
-README.cvs
+README-DEVELOPMENT
 UPGRADE
 WHATSNEW-4.5
 WHATSNEW-4.7
 WHATSNEW-4.9
 WHATSNEW-5.1
 WHATSNEW-5.3
+WHATSNEW-5.5
+WHATSNEW-5.7
 debian/CREDITS.debian
diff --git a/dist/lib/UI/ichelp.txt b/dist/lib/UI/ichelp.txt
index 54bef33..46221ce 100644
--- a/dist/lib/UI/ichelp.txt
+++ b/dist/lib/UI/ichelp.txt
@@ -20,7 +20,7 @@ dbupload.main	Database Upload	<p>
<b>Coming soon</b>
</p>
 edit.item	Edit/Create Item	<p> The <b>Edit Item</b> page is used to create or edit a product item. The fields
  displayed on this page are dependant on how the page was set up by your Site
  Administrator or Super User. For more information on the fields displayed on
  this page, see your Site Administrator or Super User.
<p>
<h2>Function</h2>
<b>OK</b><br>
After completing the necessary information on the page, click <b>OK</b> to commit your changes/additions. The page is refreshed and the changes are committed.
<p>
<b>Cancel</b><br>
Abandon entered changes without committing them. The page is refreshed, displaying only the original information.
<p> <b>Auto-Export</b><br>
  Click this checkbox to enable the Auto-Export feature. The Auto-Export feature
  exports the changes you are committing to the tables described on these pages
  to the original flat text file. This feature allows you to keep your original
  files up-to-date and portable. However, while this feature may not hinder the
  system's performance when exporting a small table, exporting a large table may
  slow your system.
<p>
<h2>Features</h2>
The <b>meta</b> link, which is only visible to the Site Administrator or Super
User, is displayed below each field name. This link allows the Site Administrator
or Super User to change the parameters for each field. For more information on
<b>meta</b> links, see the <a href="flex.meta.html">Meta Field Information</a> page.
 edit.page	Edit Page	<p> The <b>Edit Page</b> page allows you to edit the preferences of each Web page
  in your site, including the Interchange Administrator Site. The <b>Edit Page</b>
  page also allows you to view and edit the html source code for the page.
<p>
<h2>Functions</h2>
<b>Preview</b><br>
After completing the necessary information on the <b>Edit Page</b> page, click
this button to preview the page. This function is helpful if you want to view
the page before committing to the changes. The following is a list and description
of the most common fields displayed on this page. If you are unsure of the function
of a field displayed, contact your Site Administrator or Super User.
<p>
<ul>

<li><b>Change Template</b><br>
After choosing a template from the drop-down list, click this button to implement the change. For more information on creating or editing your templates, see <a href="something.html">blah</a>.
<p>
  <li><b>Page Title</b><br>
    The title of the Web page that you are editing/creating.
    <p>
  <li><b>Page Banner</b><br>
    The banner of the Web page that you are editing/creating.
    <p>
  <li><b>Members Only</b><br>
    Limits access to the Web page to customers that have a user account with you.
    If activiated, a user log in page is displayed before the Web page is displayed.
    <p>
  <li><b>Component Before Content</b><br>
    Allows you to specify a marketing device to be displayed before the content
    on this Web page.
    <p>
  <li><b>Component After Content</b><br>
    Allows you to specify a marketing device to be displayed after the content
    on this Web page.
    <p>
  <li><b>Background Color</b><br>
    Allows you to specify the background color of the Web page that you are editing/creating.
    <p>
<li><b>Content</b><br>
    Displays the html source code that corresponds to the Web page that you are
    editing/creating. This is where the content of the Web page is specified.
</ul>

<b>Save</b><br>
After completing the necessary information on the <b>Edit Page</b> page, click this button to commit your changes. The <a href="page.editor.html">Page Editor</a> page is displayed.
<p>
<b>Cancel</b><br>
Abandon changes by clicking this button. The <a href="page.editor.html">Page Editor</a> page is displayed.
 env_vars	Environment Variables	<p>Here you can view the environment of the running Interchange daemon.
Useful only for debugging purposes.
</p>
-export.main	Individual Table Export	<p>
The <b>Individual Table Export</b> page allows you to export any of the internal tables on Interchange to a file on the server.
<p>
<h2>Functions</h2>
<b>Export</b><br>
After selecting the export criteria, click <b>Export</b> to export the table.
The following list describes the <b>Export As</b> available formats.
<ul>

<p>
  <li><b>Current Type/System Default</b><br>
    Types specified in the Interchange configuration files.
<p></p>

<p>
  <li><b>TAB Delimited</b><br>
    First line of the file represents column names. Each line
represents a row, with tab characters separating columns.
<p></p>

<p>
  <li><b>CVS</b><br>
    The same as TAB delimited, but separated by commas and quotes.
<p></p>

<p>
  <li><b>PIPE Separated</b><br>
    The same as TAB delimited, but separated by | characters instead of tabs.
<p></p>

<p>
  <li><b>%%/%%%</b><br>
    One column per line, separated by %% lines, with %%% between rows.
<p></p>
</ul>
+export.main	Individual Table Export	<p>
The <b>Individual Table Export</b> page allows you to export any of the internal tables on Interchange to a file on the server.
<p>
<h2>Functions</h2>
<b>Export</b><br>
After selecting the export criteria, click <b>Export</b> to export the table.
The following list describes the <b>Export As</b> available formats.
<ul>

<p>
  <li><b>Current Type/System Default</b><br>
    Types specified in the Interchange configuration files.
<p></p>

<p>
  <li><b>TAB Delimited</b><br>
    First line of the file represents column names. Each line
represents a row, with tab characters separating columns.
<p></p>

<p>
  <li><b>CSV</b><br>
    The same as TAB delimited, but separated by commas and quotes.
<p></p>

<p>
  <li><b>PIPE Separated</b><br>
    The same as TAB delimited, but separated by | characters instead of tabs.
<p></p>

<p>
  <li><b>%%/%%%</b><br>
    One column per line, separated by %% lines, with %%% between rows.
<p></p>
</ul>
 faq	Frequently Asked Questions	<p> <i><b>Does Interchange do real-time credit card processing?</b></i> <br>
No, but it does interface with real-time payment processing systems, along with transaction management and order management systems of all kinds. 
</p>

<p> <i><b>Interchange is open source, but I don't know how to do computer programming.
  What can I do if I want to add features?</b></i> <br>
There are many Interchange consultants who can help you do this. While we would suggest people involved in Interchange development, as they will readily incorporate your changes into the distribution, there are many fine consultants. Send email to interchange-biz at icdevgroup.org to contact them.
</p>
 flex.meta	Meta information edit	<p> The <b>Meta Information Edit</b> page allows a user to edit the parameters
  of a displayed field. For example, if you click the <b>meta</b> link for the
  <b>Last Name</b> field, the <b>Meta Information Edit</b> page is displayed for
  that field. Editing the parameters in the <b>Meta Information Edit</b> page
  effects the values that will be accepted for the <b>Last Name</b> field. You
  could specify the width of this field, meaning the number of characters accepted,
  as 30 using the <b>Meta Information Edit</b> page. This would limit the length
  of any value entered in the <b>Last Name</b> field to 30 characters.
<p> The <b>Meta Information Edit</b> field is displayed only to Super Users. Exercise
  caution when editing this page.
<p><h2>Features</h2>
<b>OK</b><br>
After entering the necessary values, click <b>OK</b>. The following is a description of some of the displayed fields.
<ul>
<p>
  <li>"Widget Type" specifies the HTML INPUT tag type to use when displaying the
    field in, say, the item editor.
    <p></p>

<p>
  <li>"Width" and "Height" only apply to some of the "Widget Type" options, for
    instance the "Textarea" widget.
    <p></p>

<p>
  <li>"label" is displayed instead of the internal column name. For example, the
    "category" column of the "products" table might have a label of "Product Category."
    <p></p>

<p>
<li>"help" is displayed below the column label, and helps describe the purpose of
the field to the user.
<p></p>

<p>
<li>"help url" can be used to link to a page giving more information on the field.
<p></p>

<p>
  <li>"lookup" can be used when a field is acting like a foreign key into another
    table. In that case, you'll probably want to use some sort of select box as
    the widget type, and if you want to reference multiple rows in the destination
    table, you'll probably want to use a multi-select box, with "colons_to_null"
    as the pre_filter, and "::" as the lookup_exclude.
    <p></p>

<p>
<li>"filter" and "pre_filter" can be used to filter data destined for that field
or data read from that field, respectively.
<p></p>
</ul>
 flex.select	Direct Table Edit: Select for table edit	<p>
Having selected a table to edit, you can now add a new row, edit an existing
row, edit all rows spreadsheet-style, or delete a row.
</p>
diff --git a/extensions/benchtimes/bin/benchtimes b/extensions/benchtimes/bin/benchtimes
index 67d88c2..576a8d8 100755
--- a/extensions/benchtimes/bin/benchtimes
+++ b/extensions/benchtimes/bin/benchtimes
@@ -174,7 +174,7 @@ BIGP: {
 }
 =head1 SEE ALSO
 
-http://cvs.icdevgroup.org/cgi-bin/cvsweb/interchange/extensions/benchtimes
+extensions/benchtimes
 
 =head1 AUTHOR
 


hooks/post-receive
-- 
Interchange



More information about the interchange-cvs mailing list