Re: Bug#217067: Impossible to display non-European languages
От | Ron |
---|---|
Тема | Re: Bug#217067: Impossible to display non-European languages |
Дата | |
Msg-id | 20031025062654.GC27721@hank обсуждение исходный текст |
Ответ на | Re: Bug#217067: Impossible to display non-European languages (Jean-Michel POURE <jm@poure.com>) |
Ответы |
Re: Bug#217067: Impossible to display non-European languages
|
Список | pgadmin-hackers |
I've trimmed the cc list to something a bit more appropriate for this. On Thu, Oct 23, 2003 at 09:37:23AM +0200, Jean-Michel POURE wrote: > This user base makes it possible for us to detect and fix the main Unicode > bugs in wx. As a result we publish our own version of wx, until the fixes are > integrated in wx. > > Whenever you prepare wx2.6, we would appreciate to discuss before releasing it > on Debian. To make sure that a working wx2.6 version is used. You will _really_ need to get your fixes into 2.5 well before 2.6 is released. The first release of 2.6 will mandate a freeze on binary incompatible changes to that branch and all but the most obvious and safe bugfixes will have to go into 2.7 after that. If pgadmin does not work with an unpatched 2.6 then you are going to be in a world of pain wrt to distributing it in Debian (and probably the other distros too, though I can't speak for them). We had a major disaster when 'stable' wxPy released depending on the unstable wx2.3 and I'll not be keen to repeat such an episode, even for an app as important as you indicate pgadmin to be. My best recommendation would be that you get an idea (from wx-dev) of when people would like to see 2.6 frozen (the borland thing will surely be pushing this in ways the code alone might not mandate) and then work very hard to see that all your important patches are incorporated in one way or another before then. I have a responsibility to the maintainers of other wx-using apps to be extremely hesitant to accept any patches that aren't in cvs for inclusion in the .debs. Not only might it break their compatibility on other platforms, but it might break their app entirely with no chance for prior testing. The bottom line basically is that either you guys will need to fork wx entirely and support your own version, or work to merge your branch with the mainstream before the stable release is made. Sorry, but as much as I'd love to help you guys get your app into the next Debian stable release, I just can't make the .debs a leverage point for patches that haven't been accepted into cvs yet. If you want them in the 2.6 debs, you're going to have to get them past the gauntlet of wx-dev first. > Could you point > me out the Debian list where the wx stuff is discussed? There isn't one as such, (other than wx-dev) but I have a cc list of the wx app maintainers that I usually post to when I'm about to change anything controversial, or when it all hits the fan in a big way. The last time it got used was for the what to do about gtk2 question. I'm not sure if any of this helps you at all, but I hope it sheds a bit of light on the path to follow. cheers, Ron
В списке pgadmin-hackers по дате отправления: