On Mon, 24 Jan 2005 [EMAIL PROTECTED] wrote: > Have you considered building separate conflicting packages; one with Java and > C# support and one without like the old gettext?
No, because that would still keep Bug#244215 unfixed, not to mention such duplication would confuse a lot of people. The Debian gettext should support as many programming languages as possible, as the author intended it to be. Since you ask, there are several reasons why I have been ignoring Java so far: a) gcj was the only available Java compiler. b) gcj produced incorrect code when creating libintl.jar. c) gcj was not even available for all the architectures. Problems a) and b) are now solved by using jikes-classpath. Using gcj as well fixes Bug#244215 without requiring a virtual machine being present. Problem c) is not really a problem by itself, but an added complexity, but once I realized that Bug#244215 would be fixed by using gcj, I decided to conditionalize the build-dependencies using the appropriate syntax. BTW: There are packages with C# support in experimental, in case you want to know how they will look like when they will become "official" (i.e. when they are uploaded for unstable). This time the normal dependencies will not change, only the build-dependencies. If this is not adequate for your needs, bear in mind that this is free software. You are not only free to improve the software to suit your needs, you are also free to remove unwanted features. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
