From: Duncaen <Duncaen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [RFC] Split php package into php7 and php8
Date: Mon, 28 Jun 2021 18:16:32 +0200 [thread overview]
Message-ID: <20210628161632.tthG27X3HIixCMdT4W6m3GcSpxA2WP9M29AskaY-zfA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31678@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
New comment by Duncaen on void-packages repository
https://github.com/void-linux/void-packages/issues/31678#issuecomment-869820069
Comment:
> I was thinking of making that folder part of the xbps-alternatives, so it stays consistent for everything?
With configuration files if they are changed xbps won't delete the configuration file and therefor won't be able to delete the directory, xbps would not error out because it currently does not take alternatives into account for file checks, but if it would do that it would simply error out saying that the "type" of `/etc/php` changed from directory to symlink, but it is not able to delete the directory because it contains files not removed by any package.
next prev parent reply other threads:[~2021-06-28 16:16 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-27 11:31 [ISSUE] " the-eater
2021-06-28 16:05 ` Chocimier
2021-06-28 16:08 ` the-eater
2021-06-28 16:14 ` the-eater
2021-06-28 16:16 ` Duncaen [this message]
2021-06-28 16:17 ` Duncaen
2021-06-28 16:19 ` the-eater
2021-06-28 16:26 ` Duncaen
2021-06-28 16:27 ` Duncaen
2021-06-28 16:28 ` Duncaen
2021-06-28 16:49 ` Chocimier
2021-06-28 16:56 ` the-eater
2021-06-28 16:57 ` the-eater
2021-07-13 0:10 ` jonagoldman
2021-08-05 16:14 ` MrFastDie
2021-08-05 23:51 ` jchook
2021-10-08 16:52 ` Chocimier
2021-12-18 2:21 ` jchook
2021-12-18 2:25 ` jchook
2021-12-18 2:26 ` jchook
2022-02-04 14:19 ` TinfoilSubmarine
2022-04-29 10:33 ` [ISSUE] [CLOSED] " paper42
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=20210628161632.tthG27X3HIixCMdT4W6m3GcSpxA2WP9M29AskaY-zfA@z \
--to=duncaen@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).