From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] [TRACKING] Setting up directories in runit services vs. xbps INSTALL/hooks
Date: Fri, 29 Apr 2022 04:12:51 +0200 [thread overview]
Message-ID: <20220429021251.h156iec2IHxhoDznXiQ_cOhuRoInWYlj4co1x9yoAnw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-660@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 810 bytes --]
Closed issue by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/660
Description:
There is no policy or standard for the preferred method to create certain directories and permissions.
I personally think its better to setup permissions once using `make_dirs` or the `INSTALL` script.
First reason is that if the service fails and the run script runs every second its just a waste of time.
Second reason is that if the admin changes some permissions some services tend to just blindly recursively `chown` or `chmod` directories making it impossible to setup different permissions without
changing the run script.
Directories on `tmpfs` are an exception.
https://github.com/void-linux/void-packages/pull/571
https://github.com/void-linux/void-packages/pull/5
prev parent reply other threads:[~2022-04-29 2:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-660@inbox.vuxu.org>
2020-05-23 17:02 ` CameronNemo
2020-05-23 23:33 ` sgn
2020-05-23 23:34 ` sgn
2022-04-15 0:50 ` github-actions
2022-04-29 2:12 ` github-actions [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=20220429021251.h156iec2IHxhoDznXiQ_cOhuRoInWYlj4co1x9yoAnw@z \
--to=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).