[PATCH] gnu: remove boinc-server.

  • Open
  • quality assurance status badge
Details
One participant
  • Vitalii Koshura
Owner
unassigned
Submitted by
Vitalii Koshura
Severity
normal
V
V
Vitalii Koshura wrote on 13 Sep 19:30 +0200
(address . guix-patches@gnu.org)
20240913173052.19493-1-lestat.de.lionkur@gmail.com
boinc-server is not supposed to be installed this (or any other) packaged way.
Also, it uses a completely different versioning scheme.
I don't see any value keeping it here, thus with this patch I suggest to remove it completely.

Signed-off-by: Vitalii Koshura <lestat.de.lionkur@gmail.com>
---
gnu/packages/distributed.scm | 14 --------------
1 file changed, 14 deletions(-)

Toggle diff (24 lines)
diff --git a/gnu/packages/distributed.scm b/gnu/packages/distributed.scm
index b07acfd863..5430d1428f 100644
--- a/gnu/packages/distributed.scm
+++ b/gnu/packages/distributed.scm
@@ -83,17 +83,3 @@ (define-public boinc-client
(home-page "https://boinc.berkeley.edu/")
;; BOINC is distributed as LGPL3+, with some individual modules under GPL3+.
(license (list license:lgpl3+ license:gpl3+))))
-
-(define-public boinc-server
- ;; XXX The server and client packages duplicate many files such as /lib.
- ;; TODO: consolidate them?
- (package (inherit boinc-client)
- (name "boinc-server")
- (arguments
- (list
- #:configure-flags
- #~(list "--disable-client"
- "--disable-manager")
- #:parallel-build? #f))
- (inputs (list curl `(,mariadb "dev") openssl zlib))
- (propagated-inputs (list perl python-wrapper))))
--
2.34.1
V
V
Vitalii Koshura wrote on 20 Oct 13:20 +0200
(address . 73243@debbugs.gnu.org)
CAECimMVeiOxzLLs+Fqj2ZyFHj7izMQ8LGZ8N09+kep8v7SLauA@mail.gmail.com
Hello maintainers,

Any chance to get this at least reviewed?
Thank you in advance.

Best regards,
Vitalii Koshura
Attachment: file
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 73243@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 73243
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch