The langpack should Require: a font capable of rendering that language, i.e.

Must build the langpack only if there is a font available in fedora to render that language.Must build the langpack only if the locale is supported by glibc (locale -a).See Packaging/Extensions langpack rpm guidelines Messing with ARCH_FLAGS is a sure way to create a non-functional.The fedora tarball must only be imported by the package maintainer and it should be checked out with ooocvs.core, -base, -writer, the various langpacks, etc The Fedora structure should be split similarly to the upstream structure, e.g.

OOE680m6 was the cvs tag for the upstream 2.1.0-6 rpms, so the fedora rpms must be 2.1.0-6.X where X is the fedora rpm version Retain the upstream rpm version as the base fedora version, e.g.OOX680mY, then it becomes acceptable to import into rawhide at this stage, but not during the development SRC680_mY stage. When releases it's first master workspace along the release branch, i.e.be aggressively pursued upstream to either get then accepted and merged, or clearly refused.or if the changes is not upstreamable then contain the fedora bug id in the patch name instead.or if the patch or related patchset has been accepted into upstream then name the patch as the workspace name.contain the upstream issuezilla id in the patch name and added to our upstream fedora applied-patches tracker id if not merged into upstream yet.Minimize differences from upstream, ideally we should have no fedora-specific patches at all.

3 openoffice org