Re: ITP: libi18n-charset-perl
This would mean I've to change mine too, otherwise we loose the
functionality in your package (i.e. the charsets your version is
adding). Maybe you can contact your upstream authors to contact mine
to get the charsets added to the upstream version of my package.
So, for now I'll add the charsets to my package. After that you can
remove the Charset module from your package. Ok?
"Jaldhar H. Vyas" <firstname.lastname@example.org> writes:
> Still I think I should change mine just to avoid redundancy.
> Jaldhar H. Vyas <email@example.com>
> On 1 Jun 1999, Ardo van Rangelrooij wrote:
> > Hi,
> > Good news! We both don't have to anything. The Charset module in the
> > wdg-html-validator package is first of all used as "Charset" and not
> > as "I18N::Charset", so perl will search for Charset. Further, the
> > perl script using Charset adds its private perl lib directory tree to
> > the @INC module search path, so perl will first search in that private
> > directory tree and find Charset there.
> > I can now safely upload libi18n-charset-perl without doing any harm to
> > your package. :)
> > Thanks,
> > Ardo
> > --
> > Ardo van Rangelrooij
> > home email: firstname.lastname@example.org, email@example.com
> > home page: http://www.tip.nl/users/ardo.van.rangelrooij
> > PGP fp: 3B 1F 21 72 00 5C 3A 73 7F 72 DF D9 90 78 47 F9
Ardo van Rangelrooij
home email: firstname.lastname@example.org, email@example.com
home page: http://www.tip.nl/users/ardo.van.rangelrooij
PGP fp: 3B 1F 21 72 00 5C 3A 73 7F 72 DF D9 90 78 47 F9