PlaneShift
Fan Area => Fan Art => Topic started by: Seytra on January 26, 2005, 08:56:17 pm
-
Everyone who has made custom models, skins, screens or whatever, might be interested in the new feature of the updater: ignore readonly files.
Before that, it was necessary to copy the custom files to their folders after each update. Now it is possible to have the updater simply ignore (thus not update) them by setting the \"read-obnly\" attribute on these files.
This is done, for example, by richt-clicking on the file in the Explorer, selecting \"Properties\", then checking the \"readonly\" box and then hitting \"OK\" or \"Apply\". You can undo this anytime the exact same way, but simply un-check the box.
Enjoy!
-
*Bump*
This is really nice to know!
Edit: This is post #666 8o
-
Yep, but it has a downside. When you\'ll want to edit the files and continue your work, you\'ll have to mark them writable again. And repeat as many times as you run the updater under the same risk of deletion.
The best way is too use some unique naming patterns (prefixes) and/or separate dirs for your stuff. That way you can toggle their attributes easily, without affecting other data/art that populates the dirs.
here\'s how I run the updater:
navaden@lynxlynxsp planeshift $ cat updater.sh
#!/bin/bash
chmod a-w data/effects/effectslist.xml
chmod -R a-w data/effects/misc/
chmod -R a-w art/effects/moje/
./updater -auto
chmod a+w data/effects/effectslist.xml
chmod -R a+w data/effects/misc/
chmod -R a+w art/effects/moje/
Of course, winwoes users are very impaired :P
-
Awesome. Thanks for the info Seytra. :P
-
@ Zeraph and Icefalcon: Thanks, it\'s good to see that it\'s useful. :)
Originally posted by lynx_lupo
Yep, but it has a downside. When you\'ll want to edit the files and continue your work, you\'ll have to mark them writable again. And repeat as many times as you run the updater under the same risk of deletion.
The best way is too use some unique naming patterns (prefixes) and/or separate dirs for your stuff. That way you can toggle their attributes easily, without affecting other data/art that populates the dirs.
Uh, I of course didn\'t mean to imply that the modified files shoud be stored solely in the respective PS folders. :P
The PS folders would contain a copy only, while the actual work file(s) are somewhere else (except for files that must be tested in PS, like XML stuff, but these should also be backed-up :P ).
It is mainly intended to save the hassle of repeatedly replacing the files, not as a back-up strategy. ;)
Originally posted by lynx_lupo
chmod a+w
You are granting write permission to everyone? Tsk, tsk. ;)
Originally posted by lynx_lupo
Of course, winwoes users are very impaired :P
No, actually, they\'re not: there is a handy cmdline program called \"attrib\", which is the Windoze equivalent of *N*X chmod. :D