RFC pkg-autotools: introduce infra to gettextize packages (branch yem/gettextize)
Get series with b4
b4 am 20140410231919.2538fac1@skateVersions newest first
- v1 RFC Latest0 of 3 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 3 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [PATCH 0/3] [RFC] pkg-autotools: introduce infra to gettextize packages (branch yem/gettextize)
Dear Yann E. MORIN,
Quoted 11 lines · Yann E. MORIN
This small series introduces the gettextize of a package as an optional sequence in the autotools package infra.
WARNING! Completely untested, only an RFC!
Currently, wget is the sole user, and the way it is done for wget is just working by chance (see commit log of path 3 for the complete explanations.)
So, move the gettextization to the pkg-autotools infra, so we have a chance to do it correctly and consistently across packages.
I haven't looked at the details. But to me, when only one package needs something, it is *way* too early to make changes to the common infrastructure. Especially when there is a solution that allows to solve the problem by making changes to the package .mk file itself.
I believe changes to the package infrastructure should only be made when:
* There is really no solution to solve the particular problem at the package .mk file level;
* There are a sufficient (say 5 or 10 maybe) packages that have a similar problem, and therefore factorization would make sense.
So far, I don't really see a compelling reason to complexity the package infrastructure just for the need of one particular package. Need that may very well be transient, because a future bump of wget will most likely remove the need for the gnulib patch, therefore for the autoreconf.
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com