i've to use sendfile instead of sendfile64 on unionfs, this ebuild adds a useflag for enabling/dissabling 'long file size'.
Created attachment 82682 [details] lighttpd-1.4.10-r1 with new useflag useflag lfs (long file sizes) added
Created attachment 98432 [details, diff] LFS patch for lighttpd 1.4.11 lighttpd 1.4.11 already supports 'lfs' USE-flag. I made this patch to explicitly state that we support 'lfs' and fixed the build script to use use_enable instead of hard coded --enable-lfs. (http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1)
here is the problem: if you add the lfs useflag people updating might miss functionality, since lfs would stop working for them as they don't automatically have the lfs useflag enabled. and nolfs useflags are prohibited by policy... bugger... IIRC portage is going to support per package useflag defaults sometime in the future. anyway, thats the reason why this is not an easy fix. (actually one could argue, that this is a bug in unionfs rather then lighttpd ;) this bug stays open, because we plan on doing something about this in the future. thanks
(In reply to comment #3) > this bug stays open, because we plan on doing something about this in the > future. > thanks For some reason I was still using an older pre-release lighttpd ebuild from some old overlay. Now that I disabled the overlay, I noticed that the lfs useflag is always on in the current version. Sorry, my bad. Is it possible to switch lfs on by default in the current profile and allow changing it in the ebuild? I did a recursive grep on portage tree and it seems not many packages are actually using it. A more fine grained solution would be to add per package default useflags in the profile.
Enabling the lfs USE flag by default? Not without either sticking it in default USE for a majority of profiles (won't fly) or kicking the portage people to add support for it on a per-ebuild basis. Resolving LATER.
