<?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>101088</bug_id>
          
          <creation_ts>2005-08-02 05:20 0000</creation_ts>
          <short_desc>[uclibc] libperl-5.8.7 depends (again) upon groff</short_desc>
          <delta_ts>2005-10-27 20:56:31 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>2005.0</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          <bug_file_loc>http://pastebin.ca/19061</bug_file_loc>
          
          
          <priority>P2</priority>
          <bug_severity>major</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>phreak@gentoo.org</reporter>
          <assigned_to>embedded@gentoo.org</assigned_to>
          <cc>perl@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>phreak@gentoo.org</who>
            <bug_when>2005-08-02 05:20:44 0000</bug_when>
            <thetext>Unpacked a fresh uclibc-hardened stage1 for bootstraping purposes.
Changed my ACCEPT_KEYWORDS to ~x86 and begun the bootstrapping.
After that the &apos;emerge -e system&apos; seems to b0rk, just because ~groff (1.19.1-r2)
fails (see bug #98187 for reference).

After changing the libperl ebuild (so it only checks noman if ublibc_elibc is
unset), the emerge -e works fine.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>phreak@gentoo.org</who>
            <bug_when>2005-08-02 05:21:42 0000</bug_when>
            <thetext>Created an attachment (id=64930)
Change the DEPEND to !uclibc_elibc? ( !features_noman ( ..
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>koon@gentoo.org</who>
            <bug_when>2005-08-03 01:57:59 0000</bug_when>
            <thetext>The infamous groff is back...
Same problem in dev-lang/perl

The problem needs to be fixed in stable :
- sys-devel/libperl-5.8.6-r1
- dev-lang/perl-5.8.6-r5

Reassigning to embedded</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>mcummings@gentoo.org</who>
            <bug_when>2005-08-03 17:08:58 0000</bug_when>
            <thetext>Anyone talk to spanky about this? I think this was his addition to the libperl
ebuild. And what about the perl ebuild itself?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2005-08-03 17:20:37 0000</bug_when>
            <thetext>SpanKY is on the embedded list</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2005-08-04 20:53:18 0000</bug_when>
            <thetext>rather than dance around this all the frickin time, why does libperl need groff ?

libperl will build and install just fine w/out it (after all, libperl is just
the perl library, it doesnt install any manpages with it)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2005-08-04 21:17:12 0000</bug_when>
            <thetext>also, i just tested perl-5.8.7, and the only difference is that if you have
groff installed, you get the blib/man3/Unicode::Normalize.3pm manpage ...
</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>mcummings@gentoo.org</who>
            <bug_when>2005-08-08 08:17:39 0000</bug_when>
            <thetext>Historyically (I want to say at drobbins&apos; insistance, but that could be foggy
memory talking) the libperl and perl ebuilds were kept as identical - build
style was determined by the PN, otherwise there was no difference in the two.

Whatever. The libperl ebuild only builds the so file - needs the same patches,
but so long as the dep doesn&apos;t affect the outcome (and in this case, groff
obviously doesn&apos;t) there&apos;s no problem in dropping the dep and the headaches all
together</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>koon@gentoo.org</who>
            <bug_when>2005-08-08 08:19:28 0000</bug_when>
            <thetext>As a workaround, the perl and libperl ebuilds are now back to &quot;!uclibc_elibc? (
groff )&quot; which should prevent them from breaking.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>vapier@gentoo.org</who>
            <bug_when>2005-10-27 20:56:31 0000</bug_when>
            <thetext>beu has been so kind as to punt groff completely</thetext>
          </long_desc>
      
          <attachment
              isobsolete="0"
              ispatch="0"
              isprivate="0"
          >
            <attachid>64930</attachid>
            <date>2005-08-02 05:21 0000</date>
            <desc>libperl-5.8.7.diff</desc>
            <filename>libperl-5.8.7.diff</filename>
            <type>text/plain</type>
            <data encoding="base64">SW5kZXg6IGxpYnBlcmwtNS44LjcuZWJ1aWxkCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KLS0tIGxpYnBlcmwtNS44Ljcu
ZWJ1aWxkCShyZXZpc2lvbiAxKQorKysgbGlicGVybC01LjguNy5lYnVpbGQJKHdvcmtpbmcgY29w
eSkKQEAgLTgwLDcgKzgwLDcgQEAKIAogUkVTVFJJQ1Q9InRlc3QiCiAKLURFUEVORD0iIWZlYXR1
cmVzX25vbWFuPyAoIHN5cy1hcHBzL2dyb2ZmICkKK0RFUEVORD0iIWVsaWJjX3VjbGliYz8oICFm
ZWF0dXJlc19ub21hbj8gKCBzeXMtYXBwcy9ncm9mZiApICkKIAliZXJrZGI/ICggc3lzLWxpYnMv
ZGIgKQogCWdkYm0/ICggPj1zeXMtbGlicy9nZGJtLTEuOC4wICkiCiAKQEAgLTM1OCw0ICszNTgs
MyBAQAogCQlmaQogCWZpCiB9Ci0K
</data>        

          </attachment>
    </bug>

</bugzilla>