From: Daniel Weismueller <daniel.weismueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH] Add backup/include for cups
Date: Fri, 11 Mar 2022 13:57:01 +0100 [thread overview]
Message-ID: <20220311125701.7468-1-daniel.weismueller@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]
To solve the behavior discribed in bug 12404 I added the path
/var/ipfire/cups to the backup.
Signed-off-by: Daniel Weismueller <daniel.weismueller(a)ipfire.org>
---
config/backup/includes/cups | 1 +
config/rootfiles/packages/cups | 1 +
lfs/cups | 3 +++
3 files changed, 5 insertions(+)
create mode 100644 config/backup/includes/cups
diff --git a/config/backup/includes/cups b/config/backup/includes/cups
new file mode 100644
index 000000000..445413c2f
--- /dev/null
+++ b/config/backup/includes/cups
@@ -0,0 +1 @@
+/var/ipfire/cups
diff --git a/config/rootfiles/packages/cups b/config/rootfiles/packages/cups
index f9d15bc8b..1143df6d5 100644
--- a/config/rootfiles/packages/cups
+++ b/config/rootfiles/packages/cups
@@ -837,6 +837,7 @@ usr/share/locale/zh_CN/cups_zh_CN.po
#usr/share/man/man8/lpmove.8
var/cache/cups
var/cache/cups/rss
+var/ipfire/backup/addons/includes/cups
#var/ipfire/cups
var/ipfire/cups/cups-files.conf
var/ipfire/cups/cups-files.conf.default
diff --git a/lfs/cups b/lfs/cups
index 99c9c8887..5c5aef5f8 100644
--- a/lfs/cups
+++ b/lfs/cups
@@ -94,6 +94,9 @@ $(TARGET) : $(patsubst %,$(DIR_DL)/%,$(objects))
cd $(DIR_APP) && ln -v -sf /usr/bin/smbspool /usr/lib/cups/backend/smb
+ install -v -m 644 $(DIR_SRC)/config/backup/includes/cups \
+ /var/ipfire/backup/addons/includes/cups
+
# install initscript
$(call INSTALL_INITSCRIPT,cups)
cp -fv $(DIR_SRC)/config/cups/cupsd.conf /var/ipfire/cups/
--
2.34.1
next reply other threads:[~2022-03-11 12:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 12:57 Daniel Weismueller [this message]
2022-03-19 22:05 ` 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=20220311125701.7468-1-daniel.weismueller@ipfire.org \
--to=daniel.weismueller@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