>>>>> On Wed, 22 Jun 2016, Daniel Campbell wrote:

> Sounds decent to me. Will any eclasses be affected?

Certainly l10n.eclass will need some tweaking.

> What sort of changes will need to be made in ebuilds? I ask so I
> have a list of packages I can draw up that need this changed so I
> can get things done when everything's in place with the guide.

For the simple two- and three-letter language codes it will be only
renaming from linguas_* to l10n_*. Composite codes like pt_BR have the
underscore replaced by a hyphen (i.e., pt-BR now). There are very few
cases containing a script or variant subtag:

   ca-valencia - Catalan (Valencian)
   kmr-Latn - Northern Kurdish (Latin script)
   sr-Latn - Serbian (Latin script)

Presumably these will require some special conditions (in most ebuilds
they are already special now with their old LINGUAS syntax).

I'll file a tracker bug later. Currently there are 170 packages having
linguas_* use conditionals in SRC_URI or *DEPEND. As soon as these are
converted to use l10n_* instead, we can do the rest in one atomic
commit, along with the removal of LINGUAS from USE_EXPAND.

Ulrich

Attachment: pgp3KqMzdWAsA.pgp
Description: PGP signature

Reply via email to