On Wed, Jun 16, 2004 at 08:25:02PM +0200, Dominique Devriese wrote:
-snip-
> About the issues we were discussing:
>
> * get rid of non-mt packages
> -> Could save quite some buildd time, but might upset some people
> still depending on it. I wouldn't do it yet for Qt 3.0
> personally.
Dominique Devriese <[EMAIL PROTECTED]> writes:
> Brian Nelson writes:
>
> Summarizing: Qt is a very complex package, and there are good
> reasons for most, if not all split-ups.
>>>
I'm still unconvinced of that.
>>>
>>> Fine, I'm not going to keep arguing with you over this. IMHO, a
Brian Nelson writes:
Summarizing: Qt is a very complex package, and there are good
reasons for most, if not all split-ups.
>>
>>> I'm still unconvinced of that.
>>
>> Fine, I'm not going to keep arguing with you over this. IMHO, as
>> you've demonstrated above, you don't seem to know Qt
Dominique Devriese <[EMAIL PROTECTED]> writes:
> Brian Nelson writes:
>
>> Chris Cheney <[EMAIL PROTECTED]> writes:
>>> On Tue, Jun 15, 2004 at 05:43:33PM -0700, Brian Nelson wrote:
Why do you insist so stubbornly on maintaining the package? You
don't take very good care of it, and
Dominique Devriese <[EMAIL PROTECTED]> writes:
>> One of the reasons I'm so ornery when it comes to the Debian Qt
>> packages is that much of this stuff was discussed before the split
>> and there seemed to be a consensus that there were a lot of problems
>> with it, yet it was done anyway without
> > For instance, you could put #warning pragmas at the top of each
> > obsolete header so that the compiler spits out a warning when one is
> > used.
>
> I personally fail to see how this would be superior rather than
> complementary.
1. it achieves the original aim of alerting developers to th
Brian Nelson writes:
qt3-apps-dev: stuff you need when you're going to be doing
special things with embedding Qt designer and stuff. Almost
noone needs this.
>>
>>> "Special things"? What the hell are "special things"?
>>
>> As I said: embedding Qt designer and stuff.
>>
>>> And t
Brian Nelson writes:
> Chris Cheney <[EMAIL PROTECTED]> writes:
>> On Tue, Jun 15, 2004 at 05:43:33PM -0700, Brian Nelson wrote:
>>>
>>> Why do you insist so stubbornly on maintaining the package? You
>>> don't take very good care of it, and you've said in the past that
>>> you don't even do any
Dominique Devriese <[EMAIL PROTECTED]> writes:
> Brian Nelson writes:
>
>>> qt3-dev-tools: a number of binaries ( note: architecture dependent,
>>> so you don't want them in an arch independent headers package ) for
>>> normal development with Qt
>
>> Who said we need a arch-indep headers package
Chris Cheney <[EMAIL PROTECTED]> writes:
> On Tue, Jun 15, 2004 at 05:43:33PM -0700, Brian Nelson wrote:
>>
>> Why do you insist so stubbornly on maintaining the package? You don't
>> take very good care of it, and you've said in the past that you don't
>> even do any Qt development.
>
> If you
Chris Cheney <[EMAIL PROTECTED]> writes:
>> You also seem to ignore non-multithreaded use of the qt libraries,
>> even though there are still applications depending on this. You seem
>> to not want to support embedded cross-development, again without
>> considering people who need this.
>
> There
On Tue, Jun 15, 2004 at 05:43:33PM -0700, Brian Nelson wrote:
>
> Why do you insist so stubbornly on maintaining the package? You don't
> take very good care of it, and you've said in the past that you don't
> even do any Qt development.
If you saw Qt before a few of us beat on it around April 2
On Tue, Jun 15, 2004 at 02:40:57PM -0700, Brian Nelson wrote:
> Martin Loschwitz <[EMAIL PROTECTED]> writes:
>
> >> >> Also, you must only be talking about qt3-assistant, qt3-qtconfig,
> >> >> qt3-linguist, and qt3-designer.
> >> >
> >> >> What you've said doesn't apply to headers, and who the h
On Tue, Jun 15, 2004 at 11:08:52AM +0200, Dominique Devriese wrote:
> Brian Nelson writes:
>
> >> qt3-dev-tools: a number of binaries ( note: architecture dependent,
> >> so you don't want them in an arch independent headers package ) for
> >> normal development with Qt
>
> > Who said we need a a
Martin Loschwitz <[EMAIL PROTECTED]> writes:
> On Tue, Jun 15, 2004 at 02:40:57PM -0700, Brian Nelson wrote:
>> Martin Loschwitz <[EMAIL PROTECTED]> writes:
>>
>> If your Qt package were properly maintained, I wouldn't bother you with
>>
> So you admit you are bothering? That's a point to start.
On June 15, 2004 18:27, Martin Loschwitz wrote:
> The only serious trouble in Qt3 until some days ago was that XCursor
> made it imposslbe to compile Qt3. Nothing else. You need to distinguish
> between "I think they are poorly maintained" and "they are poorly
> maintained".
I'm not qualified to j
Martin Loschwitz <[EMAIL PROTECTED]> writes:
>> >> Also, you must only be talking about qt3-assistant, qt3-qtconfig,
>> >> qt3-linguist, and qt3-designer.
>> >
>> >> What you've said doesn't apply to headers, and who the hell knows
>> >> what the difference between qt3-dev-tools, qt3-apps-dev, e
On Tue, Jun 15, 2004 at 02:40:57PM -0700, Brian Nelson wrote:
> Martin Loschwitz <[EMAIL PROTECTED]> writes:
>
> If your Qt package were properly maintained, I wouldn't bother you with
>
So you admit you are bothering? That's a point to start.
> this. However, I think it's been in quite poor con
On Mon, Jun 14, 2004 at 10:14:29AM -0700, Brian Nelson wrote:
> Dominique Devriese <[EMAIL PROTECTED]> writes:
>
> > Brian Nelson writes:
> >
> IMO, the reason for the missing files is the ridiculous number of
> superfluous packages Qt has been split into. Is it really
> necessary
Brian Nelson writes:
>> qt3-dev-tools: a number of binaries ( note: architecture dependent,
>> so you don't want them in an arch independent headers package ) for
>> normal development with Qt
> Who said we need a arch-indep headers package anyway? I don't know
> of any other library packages in
Dominique Devriese <[EMAIL PROTECTED]> writes:
> Brian Nelson writes:
>
IMO, the reason for the missing files is the ridiculous number of
superfluous packages Qt has been split into. Is it really
necessary to have libqt3-mt-dev, libqt3-headers,
libqt3-compat-headers, qt3-dev-t
Brian Nelson writes:
>>> IMO, the reason for the missing files is the ridiculous number of
>>> superfluous packages Qt has been split into. Is it really
>>> necessary to have libqt3-mt-dev, libqt3-headers,
>>> libqt3-compat-headers, qt3-dev-tools, qt3-designer, qt3-apps-dev,
>>> qt3-linguist, qt3
Dominique Devriese <[EMAIL PROTECTED]> writes:
> Brian Nelson writes:
>
>> Christopher Martin <[EMAIL PROTECTED]> writes:
>>> On June 13, 2004 12:44, Brian Nelson wrote:
For one, they're missing the qaccessible.h header. It appears to
missing from the 3.2.3 packages as well.
>>>
>>> Mar
Brian Nelson writes:
> Christopher Martin <[EMAIL PROTECTED]> writes:
>> On June 13, 2004 12:44, Brian Nelson wrote:
>>> For one, they're missing the qaccessible.h header. It appears to
>>> missing from the 3.2.3 packages as well.
>>
>> Martin, there seem to be a few other bugs open regarding mis
Christopher Martin <[EMAIL PROTECTED]> writes:
> On June 13, 2004 12:44, Brian Nelson wrote:
>> For one, they're missing the qaccessible.h header. It appears to
>> missing from the 3.2.3 packages as well.
>
> Martin, there seem to be a few other bugs open regarding missing files.
> qvfbhdr.h is
On June 13, 2004 12:44, Brian Nelson wrote:
> For one, they're missing the qaccessible.h header. It appears to
> missing from the 3.2.3 packages as well.
Martin, there seem to be a few other bugs open regarding missing files.
qvfbhdr.h is missing - #182366. tabwidget.png should also allegedly ex
Martin Loschwitz <[EMAIL PROTECTED]> writes:
> Developers, please test these packages heavily and report anything you see --
> whether the packages work fine, whether they fix bugs you reported before, and
> of course whether they rise new bugs. There are some minor things on my TODO;
> if these
Christopher Martin writes:
> Generally, there are a large number of bugs open that should be
> dealt with one way or another - people have requested dbg packages,
Just a note that I maintain unofficial debug packages of qt, kdelibs,
kdebase and occasionally ( when I happen to build them ) other k
Christopher Martin writes:
> Hello, Thanks for making these packages available. They're working
> very well, but I did notice a few small things.
Dito, thanks a lot for reconsidering, Martin.
> libqt3-mt-dev now pulls in several database libraries. Is this
> avoidable somehow?
Agree with this.
Hello,
Thanks for making these packages available. They're working very well, but
I did notice a few small things.
libqt3-mt-dev now pulls in several database libraries. Is this avoidable
somehow?
Also, the Kmenu now has a problem wherein there is a gap between it and
its submenus. Also, the
Fellow users, fellow developers!
I am proud to announce the availability of official Qt 3.3 beta packages for
the Debian GNU/Linux Distribution. The packages have version 3.3.2-0pre1 and
have been uploaded to the experimental-archive some hours ago. As they contain
new components (database plug
31 matches
Mail list logo
