Mercurial > traipse_dev
comparison upmana/ReadMe.txt @ 47:52f6a38f8885 traipse_dev
Update Manager 0.6.7 (Initial Release). Getting ready to implement it now.
Default Check on repos does *NOT* work. Manifest works, Repos work. Main does not
show panel or menu item, so if Auto or No are check, user will *NOT* see the Update
Manager unless they edit their manifest.xml
| author | sirebral |
|---|---|
| date | Thu, 06 Aug 2009 03:31:21 -0500 |
| parents | |
| children |
comparison
equal
deleted
inserted
replaced
| 46:599f727e3833 | 47:52f6a38f8885 |
|---|---|
| 1 Welcome to Update Manager 0.6.7!!! | |
| 2 | |
| 3 This is the first isntallment of Update Manager for the OpenRPG Virtual Game Table. The package includes several files that allow users to install Update Manager as a package into other softwares that use Mercurial. The package itself includes | |
| 4 | |
| 5 updatemana.py ## The Update Manager | |
| 6 manfiest.py ## A clone of the Plugin Database file (plugindb.py) from the OpenRPG Project | |
| 7 validate.py ## Currently unused but it is here for future packaging, from the OpenRPG Project | |
| 8 xmltramp.py ## From the OpenRPG Project | |
| 9 __init__.py ## So you can copy the upmana folder and import updatemana.py anywhere | |
| 10 tmp folder ## Used to protect files during a repository update | |
| 11 default_ignorelist.txt ## An empty txt, needed in case users cannot create their own ignorelist.txt | |
| 12 default_manifest.xml ## A nearly empty XML file. Used to hold Update Manager information. | |
| 13 | |
| 14 The code is incomplete in this version, but the pieces that are missing have notes in remarks on how to complete them. | |
| 15 | |
| 16 So what can you do with Update Manager? If you have a project that you want to serve to users and user Mercurial as a way to deliver updates, Update Manager allows you to deliver those updates without the fear of creating a problem with user sentiment. Users will be able to (when completed) access their Control tab and update to any revision or any branch that has been served via a repoistory. Users also have the option to protect files from being overwritten during updates, or not update at all! | |
| 17 | |
| 18 If you have a development team you can use Update Manager as a speedy way to surf through your branches and revisions. |