From: Jes Sorensen <jes.sorensen@gmail.com>
To: ebiggers@kernel.org
Cc: linux-fscrypt@vger.kernel.org, kernel-team@fb.com,
Jes Sorensen <jsorensen@fb.com>
Subject: [PATCH 0/2] fsverity-utils Makefile fixes
Date: Fri, 15 May 2020 16:56:47 -0400 [thread overview]
Message-ID: <20200515205649.1670512-1-Jes.Sorensen@gmail.com> (raw)
From: Jes Sorensen <jsorensen@fb.com>
Hi,
This set goes on top of the libfsverity changes from Eric.
One deals with the Makefile not cleaning up the library when running
'make clean'.
The second removes the forced override of CFLAGS and CPPFLAGS. This
really shouldn't be forced like it was, since package managers and
builders should be able to specify their preferred flags.
With these applied, I am able to build an rpm of fsverity-utils which
provides fsverity-utils and fsverity-utils-devel.
Should we bump the version to 1.1 or 1.0.1 or something too?
Once this is pushed to the official branch, I'll do an updated package
for Fedora Rawhide and do another pull-request for the RPM code.
Cheers,
Jes
Jes Sorensen (2):
Fix Makefile to delete objects from the library on make clean
Let package manager override CFLAGS and CPPFLAGS
Makefile | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.26.2
next reply other threads:[~2020-05-15 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 20:56 Jes Sorensen [this message]
2020-05-15 20:56 ` [PATCH 1/2] Fix Makefile to delete objects from the library on make clean Jes Sorensen
2020-05-20 2:42 ` Eric Biggers
2020-05-15 20:56 ` [PATCH 2/2] Let package manager override CFLAGS and CPPFLAGS Jes Sorensen
2020-05-20 2:54 ` Eric Biggers
2020-05-20 20:00 ` Jes Sorensen
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=20200515205649.1670512-1-Jes.Sorensen@gmail.com \
--to=jes.sorensen@gmail.com \
--cc=ebiggers@kernel.org \
--cc=jsorensen@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-fscrypt@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).