While merging FlowScan emerge check if rrdtool version is not 1.2. But if rrdtool is not installed, emerge fail at configure because it doesn't find rrdtool. Reproducible: Always Steps to Reproduce: 1.emerge -C rrdtool (optional, to make sure rrdtool isn't installed) 2.emerge FlowScan 3. Actual Results: emerge fail while configure. Expected Results: Merging FlowScan without asking for rrdtool. I think problem is due to the DEPEND clause: " !=net-analyzer/rrdtool-1.2*" If no rrdtool emerge would not merge rrdtool and then it fails. So I try this workaround: emerge "<rrdtool-1.2*" FlowScan and it works well. I think we just need to replace "!=" by "<" to close this bug.
Created attachment 65533 [details, diff] FlowScan-1.006-r1.ebuild.diff
Created attachment 65582 [details, diff] patch for FlowScan ebuid IMHO We can't leave the line "!=rrdtool-1.2*" in RDEPEND and DEPEND to solve our problem. First, it's useless since its implied by "<rrdtool-1.2*". Second it doesn't force portage to merge rrdtool. Removing this line shouldn't cause any trouble and it's far more easy to read and maintain.
Thanks for reporting. I had fixed in my local version but never moved it onto CVS :( Let me know if any more problems.
(In reply to comment #2) > First, it's useless since its implied by "<rrdtool-1.2*". It is not useless. If you add the block, it won't merge unless you manually unmerge rrdtool-1.2.x. The way things were left, rrdtool will receive a forced downgrade if the user has a 1.2.x version. Also, we should probably work on SLOTting rrdtool since some programs work with 1.0.x and some with 1.2.x.
