Github messages for voidlinux
 help / color / mirror / Atom feed
From: thypon <thypon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: fscrypt: also include pam module in package 
Date: Sun, 12 Apr 2020 00:19:49 +0200	[thread overview]
Message-ID: <20200411221949.r1HKWYf-Au-rsAoNNYZj27oUkD8QinRllzXukM1M5uY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20272@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1984 bytes --]

There's a merged pull request on the void-packages repository

fscrypt: also include pam module in package 
https://github.com/void-linux/void-packages/pull/20272

Description:
The previous build style used for fscrypt, go, meant that the fscrypt PAM module, pam_fscrypt.so, wasn't included in the package. This makes PAM integration impossible if the user doesn't compile and install the module themselves.

The /etc/pam.d/fscrypt config file, which is supposed to be created by packagers to allow fscrypt to use the login password, wasn't included in the package either.

The INSTALL.msg file was added to let users know they'd still need to configure some things if they wanted a fully integrated setup. This configuration information is currently held in the Arch Wiki, where it's formatted a bit better than it is in the projects's github page. I felt it disnecessary to repeat the steps in the message, but I can copy them if you feel it's necessary, or add them to the Void Documentation.

I feel this build script has a few hacks, so I wanted to post it here to see if you have any ideas about what can be done to fix it (or if it's ok as it is).

* I added `nostrip` because it didn't build with `nopie`, and then failed during one of the lints.
* `make_install_args`: I couldn't understand what was going on with the original Makefile, but it didn't work unless I had it exactly like this. Anything I tried with setting `DESTDIR` to something made the whole thing go up in flames.
* `make_install_target`: installing only the library avoids having to remove the binary from DESTDIR, because otherwise it appears in the wrong place. The binary is then copied manually in `post_install`.
 
I don't know what Void's instace on this is, but this isn't a reproducible build. I had noticed it when traipsing through the Makefile, where the buildtime is passed as a "define" to the toolchain. The PKGBUILD used by Arch also adds a patch to make the build reproducible.

  parent reply	other threads:[~2020-04-11 22:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-20272@inbox.vuxu.org>
2020-03-22 16:50 ` fscrypt: change build_style to gnu-makefile Duncaen
2020-03-22 18:25 ` ericonr
2020-03-22 23:37 ` ericonr
2020-03-23  5:20 ` ericonr
2020-03-26  6:10 ` ericonr
2020-04-10 19:59 ` [PR PATCH] [Updated] fscrypt: also include pam module in package ericonr
2020-04-10 20:04 ` ericonr
2020-04-10 20:26 ` ericonr
2020-04-10 20:42 ` ericonr
2020-04-10 20:42 ` ericonr
2020-04-11 22:19 ` thypon [this message]
2020-04-11 22:21 ` xtraeme

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=20200411221949.r1HKWYf-Au-rsAoNNYZj27oUkD8QinRllzXukM1M5uY@z \
    --to=thypon@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).