Date: Thu, 07 Dec 2000 00:26:39 +0900 From: Tatsumi Hosokawa <hosokawa@itc.keio.ac.jp> To: yokota@zodiac.mech.utsunomiya-u.ac.jp Cc: keichii@peorth.iteration.net, hosokawa@FreeBSD.org, current@FreeBSD.org Subject: Re: Progress report: Multilingual sysinstall for -current Message-ID: <86zoi91sgg.wl@ringo.FromTo.Cc> In-Reply-To: In your message of "Wed, 06 Dec 2000 20:25:30 %2B0900" <200012061125.UAA27235@zodiac.mech.utsunomiya-u.ac.jp> References: <86g0k2q7gz.wl@ringo.FromTo.Cc> <20001206034625.A40075@peorth.iteration.net> <200012061125.UAA27235@zodiac.mech.utsunomiya-u.ac.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
At Wed, 06 Dec 2000 20:25:30 +0900, Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> wrote: > > >As we wait for libh development, I do not think we should exert > >efforts to try for another solution. This tends to allow for > >slack in further development of better products. > >A good example would be a proposal by Alfred Pernstein to slightly > >modify RELENG_4 SMP for the duration of SMPNG development. The proposal > >was not well accepted due to the reason I stated above. > > > >We really should concentrate on libh as a complete and _clean_ solution. > > Sure, libh is a better solution. But, don't you think it's still good > to have something working until it will become available. Multilingual sysinstall project started when FreeBSD is 2.0.5, and maintained in PAO-like style, but it's very larger patch than PAO (especially, it replaces almost all messages in release/sysinstall/menus.c) and it makes that "keeping current" work very difficult. Almost all code of this project is written when FreeBSD is 2.x, and it's in "maintainance-only" phase for years. If it's on -current tree, our work can be easier, and many developpers other than us also can do this work. If this makes us the spare time, perhaps we can help libh work. I don't think sysinstall is better solution, but it's available now. I'll glad to cvs delete this code entirely, if we can use better solution. > >In addition, the purpose of putting localized sysinstall in -CURRENT > >is rather dubious. -CURRENT/HEAD is a developers' branch, people > >who use this branch should be able to read English and the system > >error messages. If they cannot install the system with English > >sysinstall, I would have doubts on their programming and testing ability. > > > >People who run -CURRENT should be able to read and write English to > >understand the code comments, report bugs, and post to the lists in English. > > I think you are missing the point here. As you point out, the -current > is for developers; it's for development and for testing. I don't > think Tatsumi wants -current users to use I18N sysinstall to install > -current, but, rather wants them to have a look at the code and test > it. My main target is RELENG_4 and I hope this won't live until 5.x-RELEASE. It's in -current for only testing purpose. > >I would have no objections to L10N'ized sysinstall being maintained in > >the same way that PAO is maintained. The boot floppies and iso images > >can be put up somewhere for download, and maintained in RELENG_4. > > Why should it be in RELENG_4? If it's maintained in -current and > regularly MFCed to RELENG_4, it is exposed to wide audience of > -current developers and -stable users. That will attract more > comments and bug reports, and will also minimize the delay between > regular releases of FreeBSD and I18N/L10N sysinstall for them; the > delay normally associated with L10N sysinstall (and PAO) after regular > FreeBSD releases. And the delay has been prolonged sometimes because only a few developper was busy :-). > >Normally, I would welcome any I18N/L10N efforts in FreeBSD. > >However, the FreeBSD Project's official position paraphrased is > >"If you don't know what to do with -CURRENT, don't install it." > > See my comments above. > > >Combined with the point that we should not divert efforts from libh, > >I hold the opinion that we should not import this. > > I don't think importing multilingual sysinstall will detract effort > from libh. You see, even if it is maintained separately from the > -current, it has its own maintainers and developers. I expect they > are the same people who will maintain and develop I18N sysinstall when > it is imported to the -current. They may or may not be libh > developers at the same time. But, I don't think I18N sysinstall is > suddenly needing a large army of developers and will steal them from > the libh developer base. Yes. Programmers are needed when some change in source tree break this code and we can find it easier if it's in -current tree. Otherwise, only translators are needed for maintainance of *.TXT, *.hlp, and catalog files. > >Finally, still many thanks and applause to Tatsumi and others > >for this work. > > The same from me to them too. Thank you ! hosokawa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86zoi91sgg.wl>