Summary: | sys-auth/pam_mount fix crypt use flag | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Sander Sweers <Sander.Sweers> |
Component: | [OLD] Core system | Assignee: | Hanno Böck <hanno> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | CC: | hkmaly, mattst88 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
pam_mount 2.8 ebuild patch
configure fix Ebuild patch pam_mount-2.10 |
Description
Sander Sweers
2011-04-11 19:36:28 UTC
Created attachment 269515 [details, diff]
configure fix
This fixes the unconditionally enabling of crypt{o,setup}.
Created attachment 270297 [details, diff]
Ebuild patch pam_mount-2.10
* Add more dependencies and/or min version per install.txt and configure.ac
* Add selinux and ssl use flags and required econf variables
* move to EAPI 4 (I hope I got all of it)
The new version 2.10 fixes all the build system issues so the patch is not needed anymore. So please also consider this as a version bump :-).
I have been running this with no issues.
(Sorry it took so long) Thanks for the patch! I just committed it and also split out common dependencies into a COMMON_DEPEND. Marking as FIXED. Let me know if you spot anything wrong. Well, the minimum required version are either not updated or too high. libhx should be >=3.6 but new ebuild >=3.10.1 libxml2 should be >=2.6 but ebuild has none openssl should be >= 0.9.8 but ebuild has none I pulled all these number from the *tarball's* confugure.ac, checked against configure. Yes TRUNK has a requirement of libhx 3.10.1 but not version 2.10. Also lsof is not used anymore since version 0.45 (2008!) and ofl is used instead... hence my patch removed this from from RDEPEND. (In reply to comment #4) > Well, the minimum required version are either not updated or too high. Thanks a lot for the comments. I've added version dependencies for libxml2 and openssl and removed the RDEPEND on lsof, but I've left the libhx dependency at 3.10.1. Since these versions of libhx and pam_mount aren't stabilized on any architecture, and libhx isn't depended on by anything else in the tree other than pam_mount, I don't think it's a problem to require the latest libhx. (In reply to comment #5) > I don't think it's a problem to require the latest libhx. What is the point of (R)DEPEND then? Why not have all packages require the latest version available. The whole point of DEPEND is to have the minimum version to make the package build/run. Anyway, I am done arguing about this. (In reply to comment #6) > (In reply to comment #5) > > I don't think it's a problem to require the latest libhx. > > What is the point of (R)DEPEND then? Why not have all packages require the > latest version available. The whole point of DEPEND is to have the minimum > version to make the package build/run. > > Anyway, I am done arguing about this. Does this cause some kind of problem? Usually libhx and pam_mount releases are made about the same time, and libhx is only in the tree as a dependency to pam_mount. It doesn't seem like a problem to consider these as more-or-less a single package. But since it seems to upset you, I'll change the required libhx version. |