From: pullmoll <pullmoll@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: New package: fah-7.5.1
Date: Sat, 11 Apr 2020 03:56:35 +0200 [thread overview]
Message-ID: <20200411015635.GcHRV6mtuI4GfCtUsoF6oZtMq6moTNwWI4EEx9uflXE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20615@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 793 bytes --]
There's a merged pull request on the void-packages repository
New package: fah-7.5.1
https://github.com/void-linux/void-packages/pull/20615
Description:
Folding@Home debian packages collection which installs FAHClient service,
FAHControl, FAHCoreWrapper, and FAHViewer binaries.
The license of FAHClient does not allow redistribution thus set this
package to restricted.
I'm not sure if this is really required and whether I did it right, i.e. set `repo=nonfree` and `restricted=yes`.
This certainly needs a review because I'm quite unexperienced with `vsv` + `system_user` packages. I got it running locally as normal user but not yet as service with `--run-as=_fah` and the system user home `/var/lib/_fah`.
So far I can only tell the binaries basically work on Void x86_64.
prev parent reply other threads:[~2020-04-11 1:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 18:17 [PR PATCH] " pullmoll
2020-04-04 10:54 ` reback00
2020-04-04 10:58 ` [PR PATCH] [Updated] " pullmoll
2020-04-04 11:07 ` pullmoll
2020-04-04 11:29 ` [PR PATCH] [Updated] " pullmoll
2020-04-04 11:32 ` pullmoll
2020-04-05 1:11 ` Piraty
2020-04-05 15:22 ` pullmoll
2020-04-05 15:27 ` [PR PATCH] [Updated] " pullmoll
2020-04-05 16:06 ` pullmoll
2020-04-05 21:25 ` Piraty
2020-04-06 4:52 ` pullmoll
2020-04-06 17:35 ` pullmoll
2020-04-06 17:36 ` pullmoll
2020-04-08 15:49 ` silvernode
2020-04-11 1:45 ` [PR PATCH] [Updated] " pullmoll
2020-04-11 1:56 ` pullmoll [this message]
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=20200411015635.GcHRV6mtuI4GfCtUsoF6oZtMq6moTNwWI4EEx9uflXE@z \
--to=pullmoll@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).