<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>225957</bug_id>
          
          <creation_ts>2008-06-11 18:59 0000</creation_ts>
          <short_desc>dev-cpp/gtkmm should not build tests with FEATURES=-test</short_desc>
          <delta_ts>2008-07-16 08:51:43 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Ebuilds</component>
          <version>unspecified</version>
          <rep_platform>All</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          <blocked>226259</blocked>
          
          <everconfirmed>1</everconfirmed>
          <reporter>flameeyes@gentoo.org</reporter>
          <assigned_to>gnome-mm@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>flameeyes@gentoo.org</who>
            <bug_when>2008-06-11 18:59:59 0000</bug_when>
            <thetext>See my post at http://blog.flameeyes.eu/articles/2008/06/11/please-dont-build-your-examples-by-default . It would be nice if gtkmm avoided building tests when the user has FEATURES=-test.

By the way, the examples USE flag is useless, it builds examples and demos but those _are not installed_, thus it only waste the users&apos; time as the compiled code is discarded right away. I&apos;d suggest getting rid of the USE flag.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>remi@gentoo.org</who>
            <bug_when>2008-06-12 09:49:44 0000</bug_when>
            <thetext>I know about the tests, cairomm is also affected by the same bug (see bug #224187)

This is on my todo, I just need to get around to actually doing it :)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>flameeyes@gentoo.org</who>
            <bug_when>2008-06-12 10:10:47 0000</bug_when>
            <thetext>Hope you don&apos;t mind if I actually file bugs or these issues :) This way you are reminded of them in your TODO, and I&apos;m sure they won&apos;t be overlooked :)
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>remi@gentoo.org</who>
            <bug_when>2008-06-12 11:22:14 0000</bug_when>
            <thetext>Actually I hadn&apos;t noticed that gtkmm was affected too. So yeah, if you have more nitpicks like this, keep filing bugs :)

I&apos;ll try to do another gnome-mm bug fixing spree Real Soon (tm)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>swapon@gmail.com</who>
            <bug_when>2008-06-13 22:31:50 0000</bug_when>
            <thetext>reported upstream in: http://bugzilla.gnome.org/show_bug.cgi?id=538226 </thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>remi@gentoo.org</who>
            <bug_when>2008-07-16 08:50:54 0000</bug_when>
            <thetext>Fixed in CVS with a minor caveat.

FEATURES=test will install 4 of the test programs&apos; code into /usr/share/doc. This bug has been fixed in trunk and gtkmm 2.13.x no longer has that issue. Since it&apos;s only a few simple C++ files, it&apos;s not really bothering me.

If anyone really wants it fixed, I can backport the patch, but I just don&apos;t see the point.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>remi@gentoo.org</who>
            <bug_when>2008-07-16 08:51:43 0000</bug_when>
            <thetext>and for the record, this was the current behavior and nobody had noticed/cared until now :P</thetext>
          </long_desc>
      
    </bug>

</bugzilla>