Hey it appears your recent changes to ~x86 lilo have messed up my system deps (thus breaking my 'world' ;/) and is trying to force me to patch the kernel for support I could care less about. I use vanilla/grsec-2.4.x and I'm not keen on having to patch my kernel sources just because device-mapper exists. Now from reading the ebuild it looks like you could tie this support into an existing USE flag vs forcing it on * portage/profiles/use.local.desc:sys-kernel/gentoo-sources:evms2 - adds EVMS 2.0 support drop EVMS 1.2.1 # devmapper-patch (boot on evms/lvm2) Maybe you could change it to something like. IUSE=evms2 .... DEPEND=">=sys-apps/sed-4 dev-lang/nasm >=sys-devel/bin86-0.15.5 evms2? ( >=sys-libs/device-mapper-1.00.08 )" .... src_unpack() { ... cd ${S}; use evms2 && epatch ${FILESDIR}/${P}-devmapper_gentoo.patch I've tested and it appears to work just fine and should meet the needs of everybody..
Note: I don't know if you would want evms or evms2. I just called it evms2 so I could continue building world.
well .. it's needed for lvm too and ppl who use lvm won't neccesarily have evms(2) in their USE .. new USE-flag for device-mapper maybe? does that make sense? regards
Sure anything makes sense and long as device-mapper is not forced on us. Might want to shorten it's name up (your call).. USE=devmap maybe
I second this. lilo is haunting my `emerge -Upv world` for several weeks now and I am *NOT* going to patch my vanilla 2.4 kernel just for that.
Created attachment 30780 [details] An ebuild file for lilo-22.5.8 This ebuild makes the use of device-mapper optional ("devmap" USE flag, devs: change the flag name as you see fit). Message informing about this is also displayed before emerge begins (from src_unpack() ).
Created attachment 30781 [details, diff] A patch for -r3 ebuild diffed against -r2
added as -r3
The -r3 ebuild is broken, you need to write devmap? ( >=sys-libs/device-mapper-1.00.08 )" instead of devmap? (>=sys-libs/device-mapper-1.00.08)" (with additional whitespace)
And, by the way: Building lilo against libdevmapper does not require the kernel to have device-mapper. (PS: I want to be able to reopen bugs... *sigh*)