hey,<br><br>i am considering how to optify liqbase and its components.<br>the issue I have is I don't want all the apps to need to change and do not want 100s of symlinks and added complexity when only 1 is needed.<br>
<br>assuming the following packages:<br>libliqbase<br>liqflow<br>liqtorch<br>liqcalendar<br>onedotzero<br>liqbase-playground<br>etc<br>* (lots more)<br><br>everything I would need optifying could be done with a single item<br>
<br>/usr/share/liqbase/*<br><br>into<br><br>/opt/liqbase/*<br><br>(or whatever the path needs to be)<br><br>this should with 1 symlink or hardlink and will cure all liqbase /opt situations:<br><br>/usr/share/liqbase/*<br>
/usr/share/liqbase/libliqbase/*<br>/usr/share/liqbase/liqflow/*<br>/usr/share/liqbase/liqtorch/*<br>/usr/share/liqbase/liqcalendar/*<br>/usr/share/liqbase/*/*<br><br>however, I don't know the best place or time to put this in.<br>
<br>also, what would happen if a new app came out from some other party who did /optification themselves?<br>(ie, they optify /usr/share/liqbase/newapp which technically already exists in /opt/liqbase/newapp by virtue of its parent)<br>
<br>i thought about doing it in the libliqbase package, but don't know how it would handle updating the .deb etc between versions in the future.<br>i have considered make a simple "libliqbase_optifier" package which the library depends and which would do the necessary transfer but will hopefully not need updating often.<br>
<br>thoughts, ideas, suggestions?<br><br>should I just go with the normal splash 100s of optify symlinks?<br><br>gary<br><br><br><br><br><br>