I have built an RPM
for the Mitel SME server which makes it fairly trivial to install TWiki.
One issue that has come up is how to handle upgrades and backups.
The RPM has the normal TWiki files (and some additional stuff to ensure that you can enable and disable TWiki over a web interface, and to automagically insert the right stuff into the Apache config file.
The problem is how to handle an upgrade. Any changes will be overwritten by the rpm version. Also, the e-smith backup mechanism tries to backup only datafiles. This would require a split of new versus modified files. Or perhaps multiple RPMs.
Does anyone see a clean way to do this?
-- BradHards - 17 May 2002
Sorry I cannot help - but if I understand it correctly, this is right move into SimplerTWikiDistribution.
-- PeterMasiar - 18 May 2002
for the Mitel SME server which makes it fairly trivial to install TWiki.
One issue that has come up is how to handle upgrades and backups.
The RPM has the normal TWiki files (and some additional stuff to ensure that you can enable and disable TWiki over a web interface, and to automagically insert the right stuff into the Apache config file.
The problem is how to handle an upgrade. Any changes will be overwritten by the rpm version. Also, the e-smith backup mechanism tries to backup only datafiles. This would require a split of new versus modified files. Or perhaps multiple RPMs.
Does anyone see a clean way to do this?
-- BradHards - 17 May 2002
Sorry I cannot help - but if I understand it correctly, this is right move into SimplerTWikiDistribution.
-- PeterMasiar - 18 May 2002 
Edit | Attach | Topic revision: r2 - 2002-05-18 - PeterMasiar
Site map
Blog web
Create New Topic
Index
Search
Advanced search
My topics of interest
Changes
Major changes only
All tags
Notifications
RSS Feed
Statistics
Preferences
Community 
Readme first
Developers News
How you can help
Community roles
#twiki IRC
Lima Release
Feature Proposals
Bugs Changes
Categories 
Account 
Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.Copyright © 1999-2026 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.