[yast-devel] Warning for opening YaST components from non-standard path
Hi! I've implemented a new functionality to emit warning into the log file if YaST is loading e.g. namespace from non-standard location (/usr/share/YaST2/ prefix). This should avoid problems with forgotten files in /y2update or ~/.yast2. If you want to silence the warning, set Y2SILENTSEARCH environment variable. It's available in yast2-core > 2.17.12 (not in factory yet). Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Stanislav Visnovsky wrote:
Hi!
I've implemented a new functionality to emit warning into the log file if YaST is loading e.g. namespace from non-standard location (/usr/share/YaST2/ prefix).
This should avoid problems with forgotten files in /y2update or ~/.yast2.
If you want to silence the warning, set Y2SILENTSEARCH environment variable.
It's available in yast2-core > 2.17.12 (not in factory yet).
Stano
very clever! :-) Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Ehlo,
I've implemented a new functionality to emit warning into the log file if YaST is loading e.g. namespace from non-standard location (/usr/share/YaST2/ prefix).
This should avoid problems with forgotten files in /y2update or ~/.yast2.
Could this be basically a first step to what feature #305261 ("Remove or ignore outdated files in /y2update") requests? B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter
Dňa Monday 22 September 2008 12:21:21 Katarina Machalkova ste napísal:
Ehlo,
I've implemented a new functionality to emit warning into the log file if YaST is loading e.g. namespace from non-standard location (/usr/share/YaST2/ prefix).
This should avoid problems with forgotten files in /y2update or ~/.yast2.
Could this be basically a first step to what feature #305261 ("Remove or ignore outdated files in /y2update") requests?
Well, this is very simple solution to the same issue. The real solution would be able to attach a version to the API so the module loader can avoid mismatches. That's much more work. Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Duncan Mac-Vicar Prett -
Katarina Machalkova -
Stanislav Visnovsky