This was discussed in the past in: http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg31489.html The attached diff will make needed changes for merging avahi and zerconf USE flags in simply "zeroconf", this will be interesting for a lot of people that tends to suffer blockers because of their USEs in make.conf, as a lot of different combinations of zeroconf, bonjour, avahi, mdnsresponder, howl are being used. Reproducible: Always
Created attachment 180318 [details, diff] cups.ebuild.diff The changes are the following: 1. Move to EAPI=2, this allows to simply a bit more the ebuild in some phases 2. Depend on net-dns/avahi[mdnsresponder-compat], this allows to drop USE flag checking in pkg_setup 3. Apply patches in src_prepare phase, this way, unpack ${A} && cd "${S}" can be dropped 4. Run configure in src_configure 5. As "avahi" USE flag is dropped and "zeroconf" USE flag has a more general sense, I use "has_version" for setting neededservices variable ____ Maybe "good-gs" stuff in pkg_postinst could be also dropped if cups would PDEPEND on ghostscript* compiled with "cups" USE flag, but I am not sure about how should I do that, as seems that virtual/ghostscript doesn't have any USE flag, maybe an option would be depend on any of the ghostscript with something like: || ( app-text/ghostscript-gpl[cups] app-text/ghostscript-esp[cups] app-text/ghostscript-gnu[cups] ) But I am not sure if this is the proper way to go :-/ Thanks for the information
*** Bug 268415 has been marked as a duplicate of this bug. ***
Created attachment 195741 [details, diff] A simple clean up This patch to cups-1.3.10-r1.ebuild removes the message for avahi requiring the mdnsresponder-compat use flag, and gets portage to require that flag. (So that after enabling the use flag, portage knows that avahi requires that package to be re-emerged). Was about to file it under a new bug, but since this bug is about cleaning up, I wasn't sure if I should.
Many thanks to both of you for your patches, fix is in >=cups-1.4 in CVS.
