public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Question regarding orphaned files on existing IPFire installations
Date: Sat, 19 Mar 2022 17:05:01 +0000	[thread overview]
Message-ID: <f4d541bb-0cd7-703b-b950-be428d29d981@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]

Hello development folks,

while preparing some of the last Core Updates, I frequently came across rootfile
changes, or patches making some files previously shipped (and therefore present 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 include 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 machines
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üller

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.

             reply	other threads:[~2022-03-19 17:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-19 17:05 Peter Müller [this message]
2022-03-21 11:40 ` Michael Tremer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f4d541bb-0cd7-703b-b950-be428d29d981@ipfire.org \
    --to=peter.mueller@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox