3 ms·
Multiple 404 on that page: http://www.rubydoc.info/github/yast/yast-yast2/ http://www.rubydoc.info/github/yast/yast-yast2/ http://yast-core.readthedocs.org/en
by code_research 11y ago
Multiple 404 on that page:
http://www.rubydoc.info/github/yast/yast-yast2/ http://www.rubydoc.info/github/yast/yast-yast2/
http://yast-core.readthedocs.org/en/latest/ http://yast-core.readthedocs.org/en/latest/
I am not trying to make you angry, but I think I put the finger right on the place where it hurts very much.
There is no clear documentation about what yast does or what it will not do - basically a blackbox. Maybe it will change apache config. Maybe not. Who knows.
- rbrownsuse 11y ago:) fair point..I'll let the YaST team know (or you could if you happen to be on freenode, they live in the #yast channel) Users know - YaST doesn't change stuff without telling you, that was the point I was trying to make earlier. Users of YaST no longer have to worry about it silently taking over config files, it either co-exists or doesn't do anything without telling the user with great big pop-up boxes first