Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Newer
Older
100644 109 lines (71 sloc) 3.239 kB
e9d7464 @jonjensen Development moved from CVS to Git
jonjensen authored
1 ------------------------------------------------------------------------------
2
3 Tracking Interchange development in Git
4
5 ------------------------------------------------------------------------------
6
7 If you don't want to wait for an official release, you can use Git to follow
8 the latest Interchange development.
9
10 WARNING: There may be bugs introduced at any time! Thoroughly test any changes
11 before incorporating. Better yet, don't use Git changes for anything but
12 fixing relevant bugs, and run the latest stable release.
13
14
15 Browse Git tree online
16 ----------------------
17
18 To browse the Interchange Git repository online, visit:
19
20 http://git.icdevgroup.org/interchange/
21
22
23 Clone a local copy
24 ------------------
25
26 See instructions on cloning and working with a local Git working copy at:
27
28 http://www.icdevgroup.org/i/dev/download
29
30
31 Make a distribution tar file
32 ----------------------------
33
34 It's best to build a distribution tar file to install from, rather than
35 installing straight from your Git working copy. To do so:
36
37 $ cd interchange
38 $ perl Makefile.PL nocopy
39 Writing Makefile for Interchange
40 $ make tardist
41 # much output ...
42 $ ls interch*.tar.gz
43 interchange-5.7.1.tar.gz
44
45
46 Unpack and install
47 ------------------
48
49 Unpack the tar file and install as normal. See the README file and other
50 documentation for help. You should already be familiar with the Interchange
51 developer website at:
52
53 http://www.icdevgroup.org/
54
55 Make sure you don't put your Git working copy at $HOME/interchange
56 and then install on top of it, since $HOME/interchange is the default
57 install directory.
58
59
60 Updating
61 --------
62
63 Follow development discussions by joining the interchange-announce and
64 interchange-users mailing lists.
65
66 Keep track of ongoing code changes by joining the interchange-cvs mailing
67 list, or watching the interchange/interchange repository in GitHub.
68
69 In many cases, the major differences in the distribution will be easily
70 updateable. You can copy any changed files directly to these library
71 directories:
72
73 lib/Vend (and all subdirectories)
74 lib/UI (and all subdirectories)
75
76 You should check the files:
77
78 catalog_after.cfg (infrequently updated)
79 catalog_before.cfg (frequently updated)
80 interchange.cfg.dist (infrequently updated)
81 usertag/* (infrequently updated)
82
83 Finally, you should check differences in the bin/* files. While they
84 are not as frequently updated as the lib/* files, they do change. Run
85 diffs against the source files in scripts/*.PL, or do another install
86 to a blank directory and do a diff to that.
87
88
89 Keeping the catalog in sync
90 ---------------------------
91
92 If you are patterning your order methods after one of the template
93 catalogs, you will want to check the products/*.txt and products/*.asc
94 files for changes. In particular, mv_metadata.asc is used to format
95 and present quite a few things in the user interface. You may have
96 to merge the databases, but there is an automated admin UI facility
97 that can help you do this.
98
99
100 Troubleshooting
101 ---------------
102
103 If you get a complaint that a "file is not found" when trying to do a
104 'make tardist' or 'make dist', that means your MANIFEST file is out of
105 sync with the current codebase. Just do:
106
107 rm MANIFEST
108 make manifest
Something went wrong with that request. Please try again.