mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Jon Ringle <jon@ringle.org>
To: ptxdist@pengutronix.de
Cc: ptxdist@pengutronix.com, Jon Ringle <jringle@gridpoint.com>
Subject: Re: [ptxdist] [PATCH v4 1/2] Add libfaketime as a core component of ptxdist for patchin support
Date: Wed, 8 Aug 2018 15:27:50 -0400	[thread overview]
Message-ID: <CAMwGMjx=xgq-GD38fHeBA8pb-S_0QuaOak1gaK5n23D9QyKFbA@mail.gmail.com> (raw)
In-Reply-To: <CAMwGMjyOZi2_x3vj7USWB7DaXPm+gbtGJujBhjfQR6aXyS-Jcw@mail.gmail.com>

On Wed, Aug 8, 2018 at 6:58 AM Jon Ringle <jon@ringle.org> wrote:
> On Wed, Aug 8, 2018 at 5:50 AM Roland Hieber <r.hieber@pengutronix.de> wrote:
>> On Fri, Aug 03, 2018 at 11:44:55AM -0400, jon@ringle.org wrote:
>> > From: Jon Ringle <jringle@gridpoint.com>
>> >
>> > libfaketime will be used during patchin so that committer timestamps always
>> > have a fixed value and therefore making the ${PKG}_SERIES_SHA256 value
>> > repeatable
>> >
>> > The minimal set of source files was picked out of libfaketime-0.9.7
>> >
>> > Signed-off-by: Jon Ringle <jringle@gridpoint.com>
>> > ---
>> >  Makefile.in                           |   14 +-
>> >  scripts/libfaketime/Makefile          |  118 ++
>> >  scripts/libfaketime/faketime.c        |  385 ++++++
>> >  scripts/libfaketime/faketime_common.h |   61 +
>> >  scripts/libfaketime/libfaketime.c     | 2410 +++++++++++++++++++++++++++++++++
>> >  scripts/libfaketime/libfaketime.map   |   10 +
>> >  scripts/libfaketime/time_ops.h        |  104 ++
>>
>> Uh. Does it really make more sense to vendor libfaketime instead of
>> using the package from the host system, like we do it with python, bash,
>> etc.?
>
>
> The reason that this is needed as a core component of ptxdist rather than just being built as a host package is that patchin step uses libfaketime and therefore is potentially needed before even a single package is ever built. What would happen if we just used a host-libfaketime package and someone adds a patch series for libfaketime? (In fact, I actually do have such a patch series locally that I will be sending to the ptxdist ml later). This is a chicken vs egg problem that is resolved by making libfaketime an integral part of ptxdist. The ptxdist usage of libfaketime in the patchin step does not need a patched version of libfaketime (it just needs to set an absolute date time and the libfaketime code I have here does that). It doesn’t need new configuration features or bug fixes for fixing the time manipulation via some specific system call.

Roland, I think I see now what you are getting at. However, do you
think it is ok to ask everyone to install libfaketime on their system
(`sudo apt-get install libfaketime`) before they are able to configure
the next version of ptxdist? On ubuntu 14.04 this package installs the
following files for me:

/usr/lib/x86_64-linux-gnu/faketime/libfaketime.so.1
/usr/lib/x86_64-linux-gnu/faketime/libfaketimeMT.so.1
/usr/share/doc/libfaketime/README.gz
/usr/share/doc/libfaketime/changelog.Debian.gz
/usr/share/doc/libfaketime/copyright

There is nothing here that I see that can be used to properly set the
correct location of the libfaketime.so.1 when setting LD_PRELOAD
environment. It could be in a different location on some other
distribution.
The libfaketime code is fairly small and making it a part of ptxdist
like kconfig is just makes sense to me given the use case where it is
needed

-Jon

_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-08-08 19:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-03 15:44 jon
2018-08-03 15:44 ` [ptxdist] [PATCH v4 2/2] Detect changes in package patch series jon
2018-08-08  9:50 ` [ptxdist] [PATCH v4 1/2] Add libfaketime as a core component of ptxdist for patchin support Roland Hieber
2018-08-08 10:58   ` Jon Ringle
2018-08-08 19:27     ` Jon Ringle [this message]
2018-08-27 16:27 ` Michael Olbrich

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='CAMwGMjx=xgq-GD38fHeBA8pb-S_0QuaOak1gaK5n23D9QyKFbA@mail.gmail.com' \
    --to=jon@ringle.org \
    --cc=jringle@gridpoint.com \
    --cc=ptxdist@pengutronix.com \
    --cc=ptxdist@pengutronix.de \
    /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