public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Warner <antarus@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] timezone configuration - why copying, not symlinking /etc/localtime ?
Date: Sat, 20 Mar 2021 22:56:20 -0700	[thread overview]
Message-ID: <CAAr7Pr-CsUYpDHBOTPMozFpJcpMZrPFrhaYAjuw-S9xe_zNVXg@mail.gmail.com> (raw)
In-Reply-To: <ueeg96ppt@gentoo.org>

On Sat, Mar 20, 2021 at 10:27 PM Ulrich Mueller <ulm@gentoo.org> wrote:
>
> >>>>> On Sun, 21 Mar 2021, Alec Warner wrote:
>
> >> Which doesn't imply that we deliberately break things.
>
> > Not sure I follow.. how is updating the handbook breaking anything?
>
> Both configurations (regular file and symlink) work just fine, and
> sys-libs/timezone-data supports them. I don't see a good reason why we
> would suddenly declare the regular file to be an invalid option.

https://bugs.gentoo.org/737914 seems to imply for some upstreams, it
being a file is not a valid option anymore?

(I'm ignoring the logic of that decision of course, but this was the
original reason this was raised.)

-A

>
> Ulrich


  reply	other threads:[~2021-03-21  5:56 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20 15:37 [gentoo-dev] timezone configuration - why copying, not symlinking /etc/localtime ? Andreas K. Huettel
2021-03-20 16:04 ` Nils Freydank
2021-03-20 19:10   ` William Hubbs
2021-03-21  4:18     ` Ulrich Mueller
2021-03-21  4:48       ` Alec Warner
2021-03-21  5:27         ` Ulrich Mueller
2021-03-21  5:56           ` Alec Warner [this message]
2021-03-21  7:23             ` Ulrich Mueller
2021-03-21  7:58       ` James Le Cuirot
2021-03-22  8:59         ` Andreas Sturmlechner
2021-03-22 20:18           ` Lars Wendler
2021-03-23  3:01             ` Andreas Sturmlechner
2021-03-22 22:54       ` Andreas K. Huettel
2021-03-23  7:22         ` Jaco Kroon
2021-03-23 11:31         ` Rich Freeman
2021-03-27 21:43           ` Joshua Kinard
2021-03-27 22:16             ` James Le Cuirot
2021-03-27 22:40               ` Joshua Kinard
2021-03-28  9:25                 ` James Le Cuirot
2021-03-28 23:46                   ` Joshua Kinard
2021-03-29  8:06                     ` James Le Cuirot
2021-04-22 18:14                       ` Marek Szuba
2021-04-22 18:18                 ` Marek Szuba
2021-03-28  0:32             ` William Hubbs
2021-03-28  2:51               ` Joshua Kinard
2021-03-28 20:05                 ` William Hubbs
2021-03-28 23:31                   ` Joshua Kinard
2021-03-29  6:07                     ` William Hubbs
2021-03-28  1:00             ` Rich Freeman
2021-03-28  1:58               ` Joshua Kinard
2021-03-21 23:58 ` Thomas Deutschmann
2021-03-22  2:06   ` Mike Gilbert
2021-03-22  3:06     ` Thomas Deutschmann
2021-03-22  3:19       ` Thomas Deutschmann
2021-03-22  4:07       ` Mike Gilbert
2021-03-22  2:49 ` Mike Gilbert

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=CAAr7Pr-CsUYpDHBOTPMozFpJcpMZrPFrhaYAjuw-S9xe_zNVXg@mail.gmail.com \
    --to=antarus@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ulm@gentoo.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