I'm going to push out a new -r2 of mt-daapd later tonight, with avahi support (in howl-compatibility mode). Can someone please use.mask avahi useflag and then restore the keyword on the ebuild _if it's the case_ as the debug useflag requires a package that's not marked ~ppc-macos and repoman doesn't like it (the marking was done by vapier, don't ask me why). Thanks, Diego
I don't know exactly why vapier keyworded it, but some "mjc" apparently tested the package. CC-ing vapier. Diego, please drop the keyword at least from the new revision you push out. % eunst USE="debug" emerge -pv mt-daapd These are the packages that I would merge, in order: Calculating dependencies - !!! All ebuilds that could satisfy "dev-util/efence" have been masked. !!! One of the following masked packages is required to complete your request: - dev-util/efence-2.4.14 (masked by: ~ppc keyword) - dev-util/efence-2.4.11 (masked by: missing keyword) - dev-util/efence-2.4.13-r1 (masked by: ~ppc keyword) For more information, see MASKED PACKAGES section in the emerge man page or section 2.2 "Software Availability" in the Gentoo Handbook. !!! (dependency required by "media-sound/mt-daapd-0.2.3-r1" [ebuild])
(In reply to comment #0) > Can someone please use.mask avahi useflag and then restore the keyword on the > ebuild _if it's the case_ If the debug issue is resolved, you're free to add the avahi mask, or better, just file a bug with a keywording request, perhaps it "just compiles".
you're too new to remember mjc, he's a former dev at any rate, the only way around the debug issue is to wrap it in !ppc-macos? () but that sucks
on second thought, the efence depend is bogus and should be punted from the ebuild the only thing it does is add -lefence it LDFLAGS ... a user could just as easily do the same thing the --enable-debug configure flag is also bogus as the only thing it does is add some more -W options to CFLAGS
So what does -lefence do?
(In reply to comment #3) > you're too new to remember mjc, he's a former dev Ah... google is great. Right. -Wall rulez :)
uhh, -lefence makes the package link against the efence library ... thats how efence works, you simply link against it ... you dont have to include any files or define any macros at build time thus a user could get the same exact effect (with any package) by doing: LDFLAGS=-lefence emerge booga hence why i make the statement that controlling efence support via USE flags is bogus, all you're doing is tweaking LDFLAGS you could change the logic to be: use debug && append-ldflags -lefence instead of doing '--enable-efence'
I had to re-install again OSX on the ibook so I can't test it right now, so I'll mask the useflag for now. I've moved the ~ppc-macos keyword to -r3 and dropped the efence thingy.
thanks dad i'll include some efence info for gentoo-dev
(In reply to comment #8) > I'll mask the useflag for now. I've moved the ~ppc-macos keyword to -r3 and > dropped the efence thingy. Cool! Can you file a bug against the library that's not ~ppc-macos, so someone will eventually pick it up, please?
