On Wed, Dec 06, 2006 at 11:21:11PM +0100, Roland Mainz wrote: > Danek Duvall wrote: > > > Given that the messages won't be translated until we start approaching FCS, > > can we simply postpone the message build for a couple of builds? > > The question is... who can decide that ?
I believe the C-Team can. > In general it would be nice to have the messsage generation running that > the i18n/l10n people can take a look at it and check whether it is > working or whether any corrections/improvements are neccesary I'm sure that someone here can facilitate that before the messages make it into the official build, if you want to get that ball rolling. > The message generation is centralised in > usr/src/lib/libast/Makefile.libastl10n and can be disabled there. The > quiz is if there is a way to automate this in a way that we don't have > to edit SUNW0on each time we turn the l10n catalog generation on or > off... I don't think so, short of generating SUNW0on's prototype files on the fly, which is, I think, more than we want to do here. They'll only have to change once, with the addition of the catalogs. > > Will ksh93 be in its own self-contained package that can easily be added to > > a build machine on receipt of the flag-day message? > > I am trying to avoid creating new packages for that as this would collide > with Rainer Orth's work in the package database.... Hunh. Okay. > but I could provide a binary tarball for the build machines on demand... That would be convenient, I think, saving build machine maintainers from having to do a full upgrade. Thanks, Danek
