Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.
Summary: Review Request: ecryptfs-utils - Linux eCryptfs utilities
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=218556
------- Additional Comments From kevin(a)tummy.com 2007-06-08 13:07 EST -------
I thought I had addressed this issue with the --disable-rpath
configure flag. I don't think there's anything funny in my makefiles
that should re-introduce it.
Yeah, me too. Will investigate more...
It makes sense to link these statically. I will make it so in the
next
ecryptfs-utils release.
Well, not sure they need to be static... I think the idea was to move the
libraries from /usr/ to /lib|/lib64. That would allow them to work fine for
people who have /usr on a remote fs or the like.
It sounds like the key modules shipping with the ecryptfs-utils
package would best be statically linked too.
Again, not sure static is needed, simply move them to a /lib/ecryptfs/ instead
of /usr/lib/
Notting: Any input on static vs simply moving to /lib ?
Thanks for looking at this Mike!
Re: kernel requires vs. conflicts; conflicts is what we've
historically done in
packages such as initscripts, hal, and so on that don't work with older >kernels.
ok, can leave the Conflicts for now.
--
Configure bugmail:
https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.