Hi, On Sat, Aug 02, 2008 at 07:12:25PM +0200, Thomas Schwinge wrote:
> I'd say it should clearly reside in an external module, on its own. As > it is a stand-alone thing, a separate translator. The same could be said about all or most of the other translators presently in the Hurd source tree... I don't really have a strong opinion on making the Hurd build (and repository) more modular in general, or keeping it as is. But as long as it is like now, it's not acceptable to ban some components to different modules, while others are part of the Hurd itself. This inevitably would mean that those outside the main tree will be second class citizens -- less maintaining, less visibility, no inclusion in Debian, more reluctance by users and develorpos to use them or rely on them... Really, there is no reason for the new code to be treated as second class citizens, just because it happens to come later than some other code. And if you are tempted to argue against this on any kind of theoretic grounds, just take a look at the real (and unchanging) situation with hurdextras. The code produced here is too valuable to end up like this. -antrik-
