<?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>67460</bug_id>
          
          <creation_ts>2004-10-13 14:04 0000</creation_ts>
          <short_desc>VDKBuilder 2.0.2 builds VDK lib, not VDK builder</short_desc>
          <delta_ts>2005-04-15 07:10:03 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>Development</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>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>johan.verrept@advalvas.be</reporter>
          <assigned_to>gustavoz@gentoo.org</assigned_to>
          

      

      
          <long_desc isprivate="0">
            <who>johan.verrept@advalvas.be</who>
            <bug_when>2004-10-13 14:04:45 0000</bug_when>
            <thetext>The vdkbuilder 2.0.2 ebuild builds the VDK lib, not VDKBuilder. This seems solved for later versions.

Reproducible: Always
Steps to Reproduce:
1.
2.
3.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>chriswhite@gentoo.org</who>
            <bug_when>2004-10-13 19:02:59 0000</bug_when>
            <thetext>I think I&apos;m going to simply remove this.  I&apos;ve upgraded VDK lib/builder
to the latest version.  Basically what happened is that at around 2.0.2,
the vdk lib and vdkbuilder teams split their source.  There&apos;s now
vdk.sourceforge.net and vdkbuilder.sourceforge.net.  I felt I should at least
bump the ebuilds though.. as they were horribly out of date :).  One more thing
though:

sparc team: the only thing that&apos;s preventing removal of 2.0.2 is that it&apos;s the
only stable sparc build you guys have.  this was stable marked wayyyyyyy long
ago by: manson@gentoo.org who I don&apos;t see as an active dev anymore.  2.0.3 is
stable on x86, so you might wish to give that a try.  2.4.0 is the latest
unstable, but I haven&apos;t had a chance to truly test it.  A good test case that
I can think of is to follow the vdkbuilder tutorials on the vdkbuilder site
and make sure that everything works ok.  Thanks ahead of time.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>gustavoz@gentoo.org</who>
            <bug_when>2004-10-18 15:07:42 0000</bug_when>
            <thetext>Keyworded vdkbuilder-2.4.0 ~sparc.
2.0.3 doesn&apos;t even build.
Other sparc devs: we should aim 2.4.0 to stable if chris is ok with it.
Haven&apos;t tried 2.0.5 but i have that gut feeling it won&apos;t build.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>gustavoz@gentoo.org</who>
            <bug_when>2004-11-01 14:09:20 0000</bug_when>
            <thetext>dev-libs/vdk-2.4.0 &amp; dev-util/vdkbuilder-2.4.0 sparc stable.
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2005-04-11 10:02:33 0000</bug_when>
            <thetext>gus you want this, since chris is no longer a dev?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>gustavoz@gentoo.org</who>
            <bug_when>2005-04-15 07:10:03 0000</bug_when>
            <thetext>Bumped vdk &amp; vdkbuilder 2.4.0 to x86 stable.
This should fix the issues.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>