On 3/4/20 7:54 PM, Christian Boltz wrote: > Hello, > > Am Mittwoch, 4. März 2020, 18:19:26 CET schrieb José Iván López > González: >> I have described a possible solution here >> https://gist.github.com/joseivanlopez/bcf7185904922afae7d93f7518192864 >> . Feedback is welcome. > > Let me make a boring counter-proposal ;-) > > Sooner or later, (nearly) everything will move from /etc/ to /usr/etc/ > Therefore I'd simply grep -r /etc/ in the code of all YaST modules, > and prepare them to work with both /etc/ and /usr/etc/ > > In the time you'd need to write a check method, you'll already have > updated 5 YaST modules ;-)
TL;DR: This is not as simple as a team of 10+ experienced developers overlooking the possibility of simply running "grep" and/or "sed" on the source code and be done. Long and sad version: You seem to assume the migration from /etc to /usr is something all the packages in the distribution are doing in a compatible and homogeneous way, so we can adapt YaST in advance. Reality couldn't be more different. Every single piece of software is defining a different hierarchy of directories with a different order of priority and completely different rules about how each file (or each entry/section inside a file) overrides each other. We cannot adapt YaST in advance. Unfortunately is not as simple as "stop reading /etc and start reading /usr/etc with /etc as a direct fallback". We have to wait for the software to make the switch and then analyze which funny combination of directories, files and rules they have chosen before adapting YaST. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions -- To unsubscribe, e-mail: yast-devel+unsubscr...@opensuse.org To contact the owner, e-mail: yast-devel+ow...@opensuse.org
