From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] housekeeping: removal of menu items for no longer available addons
Date: Mon, 03 Apr 2023 14:07:16 +0200 [thread overview]
Message-ID: <20230403120717.3420425-1-adolf.belka@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1539 bytes --]
- removal of EX-addonsvc.menu entry in config/menu/ as the lfs file for this could not be
found in the IPFire git repo all the way back to CU30
- removal of EX-addonsvc.menu, EX-asterisk.menu and EX-bluetooth.menu which are no longer
in IPfire for two years or longer.
Signed-off-by: Adolf Belka <adolf.belka(a)ipfire.org>
---
| 5 -----
config/rootfiles/common/configroot | 3 ---
2 files changed, 8 deletions(-)
delete mode 100644 config/menu/EX-addonsvc.menu
diff --git a/config/menu/EX-addonsvc.menu b/config/menu/EX-addonsvc.menu
deleted file mode 100644
index 99db1f002..000000000
--- a/config/menu/EX-addonsvc.menu
+++ /dev/null
@@ -1,5 +0,0 @@
- $subipfire->{'11.addonsvc'} = {'caption' => 'Addon Services',
- 'uri' => '/cgi-bin/addonsvc.cgi',
- 'title' => 'Addon Services',
- 'enabled' => 1,
- };
diff --git a/config/rootfiles/common/configroot b/config/rootfiles/common/configroot
index bc979cf2c..84b3f4b1e 100644
--- a/config/rootfiles/common/configroot
+++ b/config/rootfiles/common/configroot
@@ -117,10 +117,7 @@ var/ipfire/menu.d/40-services.menu
var/ipfire/menu.d/50-firewall.menu
var/ipfire/menu.d/60-ipfire.menu
var/ipfire/menu.d/70-log.menu
-#var/ipfire/menu.d/EX-addonsvc.menu
#var/ipfire/menu.d/EX-apcupsd.menu
-#var/ipfire/menu.d/EX-asterisk.menu
-#var/ipfire/menu.d/EX-bluetooth.menu
#var/ipfire/menu.d/EX-guardian.menu
#var/ipfire/menu.d/EX-mpfire.menu
#var/ipfire/menu.d/EX-samba.menu
--
2.40.0
next reply other threads:[~2023-04-03 12:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 12:07 Adolf Belka [this message]
2023-04-03 12:07 ` [PATCH] xfsprogs: Update to version 6.2.0 Adolf Belka
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=20230403120717.3420425-1-adolf.belka@ipfire.org \
--to=adolf.belka@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