From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter =?utf-8?q?M=C3=BCller?= To: development@lists.ipfire.org Subject: Question regarding orphaned files on existing IPFire installations Date: Sat, 19 Mar 2022 17:05:01 +0000 Message-ID: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============8098600379249727072==" List-Id: --===============8098600379249727072== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hello development folks, while preparing some of the last Core Updates, I frequently came across rootf= ile changes, or patches making some files previously shipped (and therefore prese= nt on existing IPFire installations) obsolete. By accident, I stumbled across some of these files again, and would therefore= like to raise the question of what to do with them. Should I, being in responsible= for a certain Core Update, delete these via the update.sh script? (This would mean to check every rootfile change for deleted files, and includ= e them in an 'rm' block in the update.sh script. I am willing to put that effort in,= but want to make sure this is desired.) Also, I recently came across some scripts such as ovpn-ccd-convert no longer = needed. For whatever reason, /usr/share/GeoIP/ is also still present on all IPFire ma= chines I administer, although it should have been deleted during the update to Core = 140. If I come across such incidents, should I include them in the 'rm' block of an update.sh script as well? Threads regarding full filesystems come up at https://community.ipfire.org/ on a regular, but not worryingly frequency. I am getting the feeling that we are= not always cleaning up leftovers during updates as thorough as we could to. :-) Thanks, and best regards, Peter M=C3=BCller P.S.: Also, I am back in action, and can take care of Core Update 167 (or 166= , if there is something left to do on it), if desired. Just drop me a line. --===============8098600379249727072==--