Hey all,
I would like to propose something, but first I want to explain the
context. I am working on (and using a pre-version of) a Hobix Debian
package. In this package setup I used to disable the `upgrade' command
because that would obviously conflict with the package system. I have
disabled it by replacing the function by a "puts" that prints a message
suggesting that the user updates the system.
However, in the current version the upgrade command also removes
metadata files[1] and this still needs to be done. But what if user A
upgrades and user B still has weblogs with incorrect metadata files. So
I propose to version the metadata files with, say, an integer X and
adapt the following commands (assuming a previous installed Hobix to
support version Y, with Y < X).
* upgrade:
- Try to get a new hobix (if any).
- Remove the metadata files if the current supported metadata
version X is bigger than the version of the current files, Y.
* upgen, regen, list, post, ...
- If no metadata exists, it is created with version X.
- Complain if metadata is still version Y, while Hobix now uses
version X, suggest user to use the upgrade command.
This way, Hobix will always get to deal with metadata of a version it
understands and I can disable the actualy getting and installing Hobix
via the web but not the code removing metadata if it is too old.
Thoughts?
Kind regards,
Paul
fn1. With metadata files, I refer to index.search and index.hobix.
--
Student @ Eindhoven | email: [EMAIL PROTECTED]
University of Technology, The Netherlands | JID: [EMAIL PROTECTED]
>>> Using the Power of Debian GNU/Linux <<< | GnuPG key ID: 0x50064181
_______________________________________________
Hobix-is-the-way mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/hobix-is-the-way
