next up previous contents
Next: 2.3 Keeping things up Up: 2. Version Control Previous: 2.1 Old versions

2.2 PaPCo core v. PaPCo modules

Any version control will only be implemented for PaPCo core - the modules remain the responsibility of the module author. As PaPCo has grown, it has provided more and more functionality, which not all the existing modules support, as they were written earlier. That does not mean that older modules do not work at all, only that they do not make full use of the functionality that PaPCo can support.

Initially all modules had been written by the author of this document, but as PaPCo gets used more widely more and more modules are being written by other authors. It is up to the provider of a module to support it. We will attempt to include as many modules as possible in the distribution, and to make sure that they are functional. But it is up to the module provider to keep us up to date on his/her module development.

We will endeavor to make any changes in the PaPCo core transparent to older modules: they should still work, albeit without some of the newer functionality. However, at times this may not be possible, and small edits may be needed to make your existing module work with the new version of PaPCo. We will try to keep the user informed of such occurrences - ons such case for PaPCo 09 is documented here (2.7.3).


next up previous contents
Next: 2.3 Keeping things up Up: 2. Version Control Previous: 2.1 Old versions
Reiner Friedel
1999-02-03