<?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>6758</bug_id>
          
          <creation_ts>2002-08-20 02:45 0000</creation_ts>
          <short_desc>aspell should install a dictionary</short_desc>
          <delta_ts>2005-07-17 13:06:51 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>1.2</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>sindian@gentoo.org</reporter>
          <assigned_to>seemant@gentoo.org</assigned_to>
          <cc>sindian@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>sindian@gentoo.org</who>
            <bug_when>2002-08-20 02:45:54 0000</bug_when>
            <thetext>I think the aspell ebuild should tell the user that she must install a
dictionary before she can use aspell. I&apos;ve seen other ebuilds that emit similar
warnings. I think it would be a good idea in this case. 

Alternatively, we could detect the user&apos;s locale and install a default
dictionary for her. I suppose we could model this process after the way aspell
finds a dictionary to use when it is run. It first checks the LC_MESSAGES
environment variable and then the LANG environment variable if LC_MESSAGES is
not set. If neither of these vars are set, it defaults to en_US. Just a thought.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2002-08-22 21:34:19 0000</bug_when>
            <thetext>great idea.

we&apos;re toying with the idea of a PDEPEND (post-depend) or some such, so I may
leave it at that.  We really need a LANG thingy in /etc/make.conf</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>sindian@gentoo.org</who>
            <bug_when>2002-08-22 23:49:56 0000</bug_when>
            <thetext>Those are both good ideas. If I can help in implementing them, let me know.

Arun (aka sindian)</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2002-08-23 04:52:21 0000</bug_when>
            <thetext>for now, a note is added in pkg_postinst()

I will, however, leave this bug report until the PDEPEND thing is implemented
(after Gentoo 1.4 comes out) and LANGS is implemented in make.conf</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2002-12-15 14:52:18 0000</bug_when>
            <thetext>ok, we&apos;re closer to getting this achieved. portage can now handle post depends
(PDEPEND). Now, when ACCEPTED_LANGS is something portage is aware about, then we
can get the rest of this implemented.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>seemant@gentoo.org</who>
            <bug_when>2003-01-16 07:41:21 0000</bug_when>
            <thetext>ok PDEPEND is now a legitimate portage characteristic -- we just need to sort
out the lang issue and this can become reality

*** This bug has been marked as a duplicate of 9988 ***</thetext>
          </long_desc>
      
    </bug>

</bugzilla>