public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Frank Crawford <frank@crawford.emu.id.au>
To: git-commits@fedoraproject.org
Subject: [rpms/safekeep] epel10.3: Add README.Fedora
Date: Sun, 22 Nov 2026 04:01:29 GMT	[thread overview]
Message-ID: <179532008970.1.11413577091116730842.rpms-safekeep-23193f229ed2@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/safekeep
Branch : epel10.3
Commit : 23193f229ed267682bd94b57ef71e210154613ec
Author : Frank Crawford <frank@crawford.emu.id.au>
Date   : 2026-11-22T14:53:48+11:00
Stats  : +21/-0 in 1 file(s)
URL    : https://src.fedoraproject.org/rpms/safekeep/c/23193f229ed267682bd94b57ef71e210154613ec?branch=epel10.3

Log:
Add README.Fedora

---
diff --git a/README.Fedora b/README.Fedora
new file mode 100644
index 0000000..017c5aa
--- /dev/null
+++ b/README.Fedora
@@ -0,0 +1,21 @@
+Safekeep is designed such that the same script can be used on both the 
+backup server (which initiates backups from clients), as well as on 
+individual clients to handle client specific tasks such as 
+dedicated ssh key generation and client-side backup processes such as dump. 
+
+As a result, on Fedora safekeep is packaged in such a way that Fedora 
+clients which want to communicate with a safekeep managed backup server 
+can choose to install the safekeep-client subpackage to ensure correct 
+safekeep client configuration. This safekeep-client subpackage does not 
+itself install any additional files at this time. But it does ensure 
+that the correct client side applications are in place for safekeep 
+managed backup services.
+
+It is recommended that all computers acting as safekeep clients install 
+the safekeep-client subpackage, even though at this time it is 
+technically optional if the necessary components such as an ssh server, 
+coreutils and util-linux are installed correctly on the client Fedora 
+system. In future version of safekeep the safekeep-client package may 
+become necessary for correct client operation.
+
+

                 reply	other threads:[~2026-11-22  4:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=179532008970.1.11413577091116730842.rpms-safekeep-23193f229ed2@fedoraproject.org \
    --to=frank@crawford.emu.id.au \
    --cc=git-commits@fedoraproject.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