From: Chris W. <la...@us...> - 2005-03-14 16:46:07
|
Update of /cvsroot/openinteract/OpenInteract2/doc/Manual In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2774 Modified Files: Tutorial.pod TutorialAdvanced.pod Log Message: OIN-152: replace package.conf references in tutorial Index: Tutorial.pod =================================================================== RCS file: /cvsroot/openinteract/OpenInteract2/doc/Manual/Tutorial.pod,v retrieving revision 1.27 retrieving revision 1.28 diff -C2 -d -r1.27 -r1.28 *** Tutorial.pod 26 Feb 2005 05:04:50 -0000 1.27 --- Tutorial.pod 14 Mar 2005 16:45:56 -0000 1.28 *************** *** 96,100 **** book/OpenInteract2/SQLInstall book/OpenInteract2/SQLInstall/Book.pm ! book/package.conf book/MANIFEST.SKIP book/Changes --- 96,100 ---- book/OpenInteract2/SQLInstall book/OpenInteract2/SQLInstall/Book.pm ! book/package.ini book/MANIFEST.SKIP book/Changes *************** *** 106,110 **** You will normally need to edit/add the following: ! book/package.conf # Add name, version, author information book/MANIFEST # Add names of distribution files book/conf/spops.ini # Describe the objects your package uses --- 106,110 ---- You will normally need to edit/add the following: ! book/package.ini # Add name, version, author information book/MANIFEST # Add names of distribution files book/conf/spops.ini # Describe the objects your package uses *************** *** 258,265 **** The class we're using as a SQL installer is held in the ! C<book/package.conf> file. Peek into the file and you should see: ... ! sql_installer OpenInteract2::SQLInstall::Book ... --- 258,265 ---- The class we're using as a SQL installer is held in the ! C<book/package.ini> file. Peek into the file and you should see: ... ! sql_installer = OpenInteract2::SQLInstall::Book ... *************** *** 1062,1066 **** Before you go any further put your info in the relevant areas of ! C<book/package.conf> (next to 'author' and 'url'). =head2 Check your package --- 1062,1066 ---- Before you go any further put your info in the relevant areas of ! C<book/package.ini> (next to 'author' and 'url'). =head2 Check your package *************** *** 1087,1091 **** ACTION: Config required fields ! OK: package.conf ACTION: Config defined modules --- 1087,1091 ---- ACTION: Config required fields ! OK: package.ini ACTION: Config defined modules *************** *** 1121,1125 **** ACTION: Config required fields ! OK: package.conf ACTION: Config defined modules --- 1121,1125 ---- ACTION: Config required fields ! OK: package.ini ACTION: Config defined modules *************** *** 1268,1272 **** Now that we've modified the templates let's install the new ! package. First edit the C<book/package.conf> file to reflect the new version number and add an entry to the top of the 'Changes' file. Next, export it and install the distribution to your website --- 1268,1272 ---- Now that we've modified the templates let's install the new ! package. First edit the C<book/package.ini> file to reflect the new version number and add an entry to the top of the 'Changes' file. Next, export it and install the distribution to your website *************** *** 1420,1424 **** That's pretty simple. Let's package it up and install it to the site. (Remember to first edit C<book/Changes> and ! C<book/package.conf>.) $ oi2_manage package_all --- 1420,1424 ---- That's pretty simple. Let's package it up and install it to the site. (Remember to first edit C<book/Changes> and ! C<book/package.ini>.) $ oi2_manage package_all *************** *** 1562,1566 **** 39: } ! You know the drill: edit C<book/Changes> and C<book/package.conf>, bundle up the package and install it, then restart the server. --- 1562,1566 ---- 39: } ! You know the drill: edit C<book/Changes> and C<book/package.ini>, bundle up the package and install it, then restart the server. *************** *** 1651,1655 **** Right Thing. ! Now edit your C<book/package.conf> and C<book/Changes> files to reflect the updates, bundle the package up and install it: --- 1651,1655 ---- Right Thing. ! Now edit your C<book/package.ini> and C<book/Changes> files to reflect the updates, bundle the package up and install it: *************** *** 1820,1824 **** 6: OpenInteract2::Action::CommonUpdate ); ! Now edit your C<book/package.conf> and C<book/Changes> files to reflect the updates, bundle the package up and install it: --- 1820,1824 ---- 6: OpenInteract2::Action::CommonUpdate ); ! Now edit your C<book/package.ini> and C<book/Changes> files to reflect the updates, bundle the package up and install it: *************** *** 1911,1915 **** 6: <p align="right"><a href="[% add_url %]">Add</a> a new book</p> ! And do your normal C<book/package.conf> and C<book/Changes> editing, then put your new package in the website: --- 1911,1915 ---- 6: <p align="right"><a href="[% add_url %]">Add</a> a new book</p> ! And do your normal C<book/package.ini> and C<book/Changes> editing, then put your new package in the website: *************** *** 1962,1966 **** 4: PROCESS status_message %] ! Now the standard C<book/package.conf> and C<book/Changes> editing, and then upgrade the website package: --- 1962,1966 ---- 4: PROCESS status_message %] ! Now the standard C<book/package.ini> and C<book/Changes> editing, and then upgrade the website package: Index: TutorialAdvanced.pod =================================================================== RCS file: /cvsroot/openinteract/OpenInteract2/doc/Manual/TutorialAdvanced.pod,v retrieving revision 1.7 retrieving revision 1.8 diff -C2 -d -r1.7 -r1.8 *** TutorialAdvanced.pod 12 Mar 2005 21:16:40 -0000 1.7 --- TutorialAdvanced.pod 14 Mar 2005 16:45:56 -0000 1.8 *************** *** 136,140 **** Add these files to your C<MANIFEST>, modify your C<Changes> and ! C<package.conf> and update your site. You can install the SQL structures like this (assuming C<OPENINTERACT2> environment variable is set to your website): --- 136,140 ---- Add these files to your C<MANIFEST>, modify your C<Changes> and ! C<package.ini> and update your site. You can install the SQL structures like this (assuming C<OPENINTERACT2> environment variable is set to your website): |