Package: jack / 3.1.1+cvs20050801-31

54_check_cont_failed_query.patch Patch series | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
I don't see any good reason why cont_failed_query would turn on
query_on_start and set_id3tag.  After all, all this option is supposed to
do is to cause jack not to fail when FreeDB is unssuccfully queried -
however, it should be up to users to initiate the query.


diff -urN jack-3.1.1+cvs20050801~/jack_checkopts.py jack-3.1.1+cvs20050801/jack_checkopts.py
--- jack-3.1.1+cvs20050801~/jack_checkopts.py	2006-04-07 20:02:26.000000000 +0200
+++ jack-3.1.1+cvs20050801/jack_checkopts.py	2006-04-07 20:03:32.000000000 +0200
@@ -50,9 +50,6 @@
     if cf2.has_key('query_on_start') and cf2['query_on_start']['val']:
         cf.rupdate({'set_id3tag': {'val': 1}}, "check")
 
-    if cf2.has_key('cont_failed_query') and cf2['cont_failed_query']['val']:
-        cf.rupdate({'query_on_start': {'val': 1}, 'set_id3tag':{'val': 1}}, "check")
-
     if cf2.has_key('create_dirs') and cf2['create_dirs']['val']:
         cf.rupdate({'rename_dir': {'val': 1}}, "check")