From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: christian@klarinett.li
Cc: Christian Hitz <christian.hitz@bbv.ch>,
Martin Bark <martin@barkynet.com>,
Christian Hitz via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 2/2] package/zic: enable installation on target
Date: Tue, 26 Mar 2024 17:10:20 +0100 [thread overview]
Message-ID: <20240326171020.1290064d@windsurf> (raw)
In-Reply-To: <2e226b32ddd0dbfde7aa120b5263c638@klarinett.li>
Hello Christian,
On Tue, 26 Mar 2024 17:03:20 +0100
christian@klarinett.li wrote:
> > Thanks, but for a patch like this, we definitely need a non-empty
> > commit log. Why do you need zic on the target, what is the use-case?
>
> When we configure a time zone on our device's GUI we use the standard
> time zones. This gives us the usual benefits e.g. automatic daylight
> saving time switching.
> We also need to support an API that wants to set the "time zone" by
> specifying the offset in minutes from GMT. The given information
> is not enough to reliably selecting one of the existing time zones.
> Instead, when the time zone is set over this API we dynamically create
> and configure a "Custom" time zone with the given offset. For this
> we use the `zic` tool on target.
Thanks for the explanation. I'm not too familiar with time zone stuff
(or in fact, I did have a look a long time ago, but I forgot the
details of how it works), bu your explanation seems to make sense :-)
> >> +define ZIC_INSTALL_STAGING_CMDS
> >> + $(INSTALL) -D -m 644 $(@D)/tzfile.h
> >> $(TARGET_DIR)/usr/include/tzfile.h
> >
> > So just the header file is needed, no library is installed?
>
> Actually, this is not required at all. I'll drop it in v2.
OK, then you can drop ZIC_INSTALL_STAGING = YES as well.
> Thanks for the review. I'll update the patch and will send a v2.
Perfect, thanks!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-26 16:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 14:56 [Buildroot] [PATCH 1/2] package/zic: add hash for existing patch Christian Hitz via buildroot
2024-02-28 14:56 ` [Buildroot] [PATCH 2/2] package/zic: enable installation on target Christian Hitz via buildroot
2024-03-26 14:44 ` Thomas Petazzoni via buildroot
2024-03-26 16:03 ` christian--- via buildroot
2024-03-26 16:10 ` Thomas Petazzoni via buildroot [this message]
2024-03-26 16:37 ` [Buildroot] [PATCH v2] " Christian Hitz via buildroot
2024-03-26 14:43 ` [Buildroot] [PATCH 1/2] package/zic: add hash for existing patch Thomas Petazzoni via buildroot
2024-03-26 16:06 ` christian--- via buildroot
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=20240326171020.1290064d@windsurf \
--to=buildroot@buildroot.org \
--cc=christian.hitz@bbv.ch \
--cc=christian@klarinett.li \
--cc=martin@barkynet.com \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.