| Revision 18218,
966 bytes
checked in by ghudson, 21 years ago
(diff) |
|
This commit was generated by cvs2svn to compensate for changes in r18217,
which included commits to RCS files with non-trunk default branches.
|
| Line | |
|---|
| 1 | This is the Scrollkeeper Open Documentation Cataloging System. |
|---|
| 2 | |
|---|
| 3 | The following modules are included: |
|---|
| 4 | |
|---|
| 5 | Scrollkeeper_cl, the Content List handling system in the cl subdir. |
|---|
| 6 | |
|---|
| 7 | Scrollkeeper_toc, the Table Of Contents extraction utility from DocBook |
|---|
| 8 | files in the toc subdir. |
|---|
| 9 | |
|---|
| 10 | Installation |
|---|
| 11 | ------------ |
|---|
| 12 | For installation instructions, see the INSTALL file. |
|---|
| 13 | |
|---|
| 14 | Notes |
|---|
| 15 | ----- |
|---|
| 16 | |
|---|
| 17 | 1) PROBLEM WITH RPM POST-INSTALL SCRIPTS FOR SCROLLKEEPER < 0.3.3 |
|---|
| 18 | Note that RPM's from 0.2 to 0.3.1 shipped with a post-install script to remove |
|---|
| 19 | the ScrollKeeper database when ScrollKeeper is uninstalled. However, due to |
|---|
| 20 | the order in which RPM executes its scripts, the database is removed after the |
|---|
| 21 | new database is built. Thus, the user is left without a database. This |
|---|
| 22 | problem is fixed starting with ScrollKeeper 0.3.3. However, any upgrade where |
|---|
| 23 | the old RPM has version 0.2 to 0.3.1 will exhibit this problem. One solution |
|---|
| 24 | is to execute "scrollkeeper-rebuilddb" after the upgrade is finished. |
|---|
| 25 | |
|---|
Note: See
TracBrowser
for help on using the repository browser.
