From: Karel Zak <kzak@redhat.com>
To: Carlos Santos <unixmania@gmail.com>
Cc: util-linux@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux v2.35
Date: Mon, 27 Jan 2020 21:21:52 +0100 [thread overview]
Message-ID: <20200127202152.4jh2w4chch37wgee@ws.net.home> (raw)
In-Reply-To: <CAJ4jsafKGLntP-uKj-+kVY=xGk9FTPuw98ntsAEEpMFR8Ub6zQ@mail.gmail.com>
On Mon, Jan 27, 2020 at 01:29:47PM -0300, Carlos Santos wrote:
> On Mon, Jan 27, 2020 at 10:40 AM Karel Zak <kzak@redhat.com> wrote:
> >
> > On Mon, Jan 27, 2020 at 02:34:38PM +0100, Karel Zak wrote:
> > > On Fri, Jan 24, 2020 at 04:16:47PM -0300, Carlos Santos wrote:
> > > > I noticed that it comes due to sys-utils/hwclock-parse-date.y, which
> > > > was taken from gnulib. Would it be possible to take the file from an
> > > > previous version of gnulib that was still under GPLv2?
> > >
> > > I have checked it again and all history of the file in git is with v3,
> > > and import old version also means import many bugs....
> > >
> > > Maybe the best would be to use our lib/timeutils.c:parse_timestamp().
> > > It does not provide support for so many date-time formats, but the
> > > basic format like "2012-09-22 16:34:22" (and subsets) is supported.
> > >
> > > IMHO it's better to introduce a small backward compatibility issue than
> > > rely on hwclock-parse-date.y or execute date(1) like old versions.
> >
> > or we can use #ifdef to keep it backwardly compatible for normal
> > distros where v3 is not problem and lib/timeutils.c:parse_timestamp()
> > with v2 for the rest ... at least for v2.35.1.
>
> Does parse_timestamp support localization, like getdate(3) does?
No, it's really simple digits based date-time like "2012-09-22 16:34:22".
getdate(3) is maybe another choice for future versions, for 2.35.1 is
parse_timestamp() good enough to avoid GPLv3.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2020-01-27 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 10:57 [ANNOUNCE] util-linux v2.35 Karel Zak
2020-01-24 19:16 ` Carlos Santos
2020-01-25 10:51 ` Karel Zak
2020-01-25 11:19 ` Carlos Santos
2020-01-26 16:59 ` J William Piggott
2020-01-26 17:50 ` Carlos Santos
2020-01-27 16:13 ` Karel Zak
2020-01-27 16:38 ` Carlos Santos
2020-01-27 20:18 ` Karel Zak
2020-01-27 13:34 ` Karel Zak
2020-01-27 13:40 ` Karel Zak
2020-01-27 15:25 ` Karel Zak
2020-01-27 16:29 ` Carlos Santos
2020-01-27 20:21 ` Karel Zak [this message]
2020-01-28 19:24 ` Sami Kerola
2020-01-30 11:17 ` Karel Zak
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=20200127202152.4jh2w4chch37wgee@ws.net.home \
--to=kzak@redhat.com \
--cc=unixmania@gmail.com \
--cc=util-linux@vger.kernel.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).