[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Weechat-dev] [task #10042] Protect scripts modified locally to be overr
From: |
rettub |
Subject: |
[Weechat-dev] [task #10042] Protect scripts modified locally to be overridden by weeget |
Date: |
Tue, 05 Jan 2010 19:15:13 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.16) Gecko/2009121610 Iceweasel/3.0.6 (Debian-3.0.6-3) |
URL:
<http://savannah.nongnu.org/task/?10042>
Summary: Protect scripts modified locally to be overridden
by weeget
Project: WeeChat
Submitted by: rettub
Submitted on: Tue 05 Jan 2010 07:15:12 PM GMT
Category: scripts
Should Start On: Tue 05 Jan 2010 12:00:00 AM GMT
Should be Finished on: Tue 05 Jan 2010 12:00:00 AM GMT
Priority: 5 - Normal
Status: None
Privacy: Public
Percent Complete: 0%
Assigned to: None
Originator Name:
Originator Email:
Open/Closed: Open
Discussion Lock: Any
IRC nick: rettub
_______________________________________________________
Details:
As said in the summary, if you modify a scripts locally, weeget's upgrade
function is quite useless.
1st solution could be to make it possible marking a script as 'hold', and
then if doing an upgrade, download the script, but save it e.g. as
'scriptname.ext.new'. (explicit hold)
2nd, store modification time of installed scripts, and while doing an
upgrade, check current mtime of the script and compare it to that stored one,
if current mtime is newer, use solution for saving described under #1.
(implicit hold)
Finally, throw a hint if script couldn't be overwritten during upgrade.
Surely, implementing something like #1 *and* #2 would be best :)
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/task/?10042>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Weechat-dev] [task #10042] Protect scripts modified locally to be overridden by weeget,
rettub <=