On Fri, Aug 28, 2020 at 10:20:12AM +0100, Stuart Henderson wrote:
> On 2020/08/27 20:51, Chris Bennett wrote:
> > I just found a bunch of new Locale perl modules added to the depends
> > list.
> >
> > They all have empty man pages from no PODs.
> > About 20ish ports, most are just relevant data files for each language.
> >
> > Should I just delete these from the PLISTs or is there an easier way to
> > prevent their generation?
> >
> > I'll submit the new dependencies for these, then I need to send the
> > rest, which are just perl data modules.
> >
> > Should I send them individually or one email with all attached?
> > I can also put those up somewhere else if that is preferable.
> >
> > I'll submit one for approval first, if it's OK, then the rest are the
> > same except for the data for each langugage.
> >
> >
> > Locale::CLDR and family of Locale::CLDR::Locales::
>
> For the data files I suggest an arrangement like
>
> textproc/p5-Locale-CLDR-Locales
> textproc/p5-Locale-CLDR-Locales/lang1
> textproc/p5-Locale-CLDR-Locales/lang2
> textproc/p5-Locale-CLDR-Locales/lang3
>
> etc. The Makefile should be mostly common between ports and can be handled
> in textproc/p5-Locale-CLDR-Locales/Makefile.inc. Look at editors/vim-spell
> or devel/pear-Date-Holidays for ideas. This is easier to review and easier
> to handle if things change in the future.
>
That helps. I looked those over and the mozilla i18n. I see what to work
toward. Had to re-read some man pages after looking at these.
I'll pull together something small with several langs and see if that
works. If that method works OK, I'll do the whole bunch.
The man page problem is from the modules only having just enough of a
POD to name the package. Nothing else.
Thanks,
--
Chris Bennett
No comments:
Post a Comment