On 8/06/2013 8:32 PM, Jerry wrote: > On Sat, 08 Jun 2013 15:42:23 +1000 > Kubilay Kocak articulated: > >> I had to backport the fix because the new pam_mount 2.13 version >> requires libmount. Let upstream know that FreeBSD doesn't have >> libmount, and request they make it optional and configurable >> (--without-libmount configure option for example), even if it >> disables certain functionality. > > Maybe it is just me; however, wouldn't it make more sense for FreeBSD to > acquire "libmount" and thereby eliminate the whole problem to begin > with, not to mention losing potential functionality? >
If that's the whole problem, and if it makes sense, absolutely. Though not explicit, my advice was based on the following: a) That my cherry-picked patch is likely only an interim measure. b) That the easiest thing an end-user could do to contribute to a solution is to notify the authors that portability would help. c) We can no longer track pam_mount updates given the recent addition of libmount as a hard dependency. d) that libmount (part of util-linux) is likely quite Linux centric and not useful in FreeBSD terms. I may be wrong here. The root cause of Janets reported issue is only a LIB_DEPENDS pointing to a specific library version (unnecessarily) and a libhx port that has moved on that pam_mount didn't support. But definitely, there may be more 'longer term' solutions such as what you eluded to. koobs _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
