From: Adrian Bunk <bunk@stusta.de>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] libtool: allow for use of reproducible_build bbclass
Date: Fri, 12 Jul 2019 12:19:55 +0300 [thread overview]
Message-ID: <20190712091955.GA21468@localhost> (raw)
In-Reply-To: <CAJTo0LaE0JvnsF9uTshyiXMzX5X6+2tzkx3jxjN1vdWFSDNAZg@mail.gmail.com>
On Fri, Jul 12, 2019 at 09:33:59AM +0100, Burton, Ross wrote:
> On Fri, 12 Jul 2019 at 07:30, Adrian Bunk <bunk@stusta.de> wrote:
> > Debian has already done a lot of work regarding reproducible,
> > so checking there for existing patches first is always a good idea.
>
> To expand on this for people who don't know how to mine Debian: first,
> identify the source package. In this case it's libtool but otherwise
> you can search packages.debian.org. Then search
> https://sources.debian.org/patches for libtool and you find
> https://sources.debian.org/patches/libtool/2.4.6-10/no_hostname.patch/.
Another useful resource is https://tracker.debian.org/
https://tracker.debian.org/pkg/libtool has some useful links,
e.g. "browse source code" (links to sources.debian.org)
or "reproducibility" (see if it is reproducible in Debian unstable).
> Ross
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2019-07-12 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 20:27 [PATCH 1/1] libtool: allow for use of reproducible_build bbclass Joe Slater
2019-07-11 20:44 ` Adrian Bunk
2019-07-11 21:55 ` Burton, Ross
2019-07-12 1:51 ` Slater, Joseph
2019-07-12 6:30 ` Adrian Bunk
2019-07-12 8:33 ` Burton, Ross
2019-07-12 9:19 ` Adrian Bunk [this message]
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=20190712091955.GA21468@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.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.