In the newly released ebuild 2004.10.1 there's a method to give a flag '--with-ethereal=/path/to/ethereal' to configure. This doesn't work when the USE flag 'ethereal' is not specified. Then '--without-ethereal=/path/to/inexistent/ethereal' is given to configure, letting it fail. This can be fixed by making the added '=/path...' going to '' when the USE flag is not set. Reproducible: Always Steps to Reproduce: 1. USE="-ethereal" emerge \=kismet-2004.10.1 Actual Results: "econf --without-ethereal=/path/to/not/existing/ethereal" fails. Expected Results: "econf --without-ethereal" should be called
Created attachment 42635 [details, diff] Proposed patch to -r1 This is a short patch for making this error go away. But i really don't know if it fits the coding style... There's certainly something i forgot...
By the way, there's a fresh ethereal out there. Maybe this should be integrated in a -r1, as the ethereal version is hardcoded and forces a downgrade at the moment. As this is not the reason why i disabled the 'ethereal' USE flag I don't have a proposed patch for this ;-)
Thank you for reporting this - I've fixed it in CVS.
