pkg kde talk - Jul 2005 - Re: [Pkg-kde-commits] rev 1255 - in people/chrsmrtn: . qt-x11-free qt-x11-free/debian qt-x11-free/debian/maintain qt-x11-free/debian/maintain/man qt-x11-free/debian/patches

* Christopher Martin [Thu, 07 Jul 2005 04:47:29 +0000]:
> --- people/chrsmrtn/qt-x11-free/debian/changelog	2005-07-06 06:58:25 UTC
(rev 1254)
> +++ people/chrsmrtn/qt-x11-free/debian/changelog	2005-07-07 04:47:25 UTC
(rev 1255)
> @@ -0,0 +1,1817 @@
> +qt-x11-free (3:3.3.4-4) unstable; urgency=low
> +
> +  * Move the package to the Debian Qt/KDE team. Thanks to Martin Loschwitz
for
> +    all his work over the years.
> +
> +  +++ Changes by Christopher Martin:
> +
> +  * Add sundry fixes from KDE''s qt-copy. (Closes: #303065)
> +
> +  * No longer build non-threaded libraries. (Closes: #180326)
> +
> +  * Added a libqt3c102-mt-dbg package. (Closes: #235396)
> +
> +  * Fix qt3-designer''s appearance in the KDE menu. (Closes:
#290402)
> +
> +  * Don''t use lib64 on amd64. (Closes: #311562)
> +
> +  * Don''t duplicate the information in the qvfb manpage. (Closes:
#282217)
> +
> +  * Make the Qt3 documentation available from /usr/share/doc/qt3-doc, and
> +    therefore also usable in dwww and doc-central. (Closes: #185900)
> +    (Closes: #284407, #294630)
> +
> +  * Add linguist manpage. Thanks to Jeremy Laine. (Closes: #268882)
> +
> +  * Include createcw source for qt3-designer. (Closes: #305919)
> +
> +  * Add missing qvfbhdr.h. (Closes: #182366)
> +
> +  * Bump libfreetype6-dev build-depends to >= 2.1.10 to work around API
> +    breakage.
> +
> +  * Enable tablet support.
> +
> +  * Build jpeg and mng support into Qt, not as plugins.
> +
> +  * Revamp the OpenGL linking patch, and add patches for gcc4.
> +
> +  * Many minor changes to improve lintian compliance.
> +
> + -- Debian Qt/KDE Maintainers <debian-qt-kde@lists.debian.org>  Wed,
6 Jul 2005 22:36:54 -0400
  Wow, this is lots of good stuff. Way to go, Christopher! :)

  I''d just like your intput about what you consider best to do wrt the
  C++ ABI transition: upload when build-dependencies are ready, _only_
  with the changes needed for the transition, or include all of the
  above as well.

  At first sight, I''d lean towards the first option, but if you
consider
  that the above changes are "safe", well, we could include them as
  well.

  What do you think?

-- 
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
 
We learned that the Linux load average rolls over at 1024. And we
actually found this out empirically.
                -- H. Peter Anvin from kernel.org

--nextPart1295360.j4jjWE0v9t
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On July 11, 2005 19:10, Adeodato Sim=F3 wrote:
>   Wow, this is lots of good stuff. Way to go, Christopher! :)
Thanks, I just hope I haven''t messed anything up! Peer review,
especially,=20
but not exclusively, from Brian Nelson (due to his Qt experience), would be=20
really great.
>   I''d just like your intput about what you consider best to do wrt
the
>   C++ ABI transition: upload when build-dependencies are ready, _only_
>   with the changes needed for the transition, or include all of the
>   above as well.
>
>   At first sight, I''d lean towards the first option, but if you
consider
>   that the above changes are "safe", well, we could include them
as
>   well.
Hmmm, at first I leaned towards making all the changes at once, but as the=20
list of changes kept growing, I began to wonder whether a simple gcc 4.0=20
transition upload would be best, since I don''t feel I really can
myself=20
certify that the changes are quite safe. This would mean two trips through=20
NEW, though.

On the other hand, if people review the changes and certify that
they''re=20
good, then perhaps that would swing the balance back in favour of an=20
all-changes-together upload (which reminds me that the Qt4 package=20
compatibility patches still need to be added - hopefully I''ll get some
time=20
this week). Decisions, decisions...

All said, I certainly would understand if people wanted to act cautiously.

BTW, since I''m a little out of the loop (and will be for a few more
weeks at=20
least, possibly much longer), how is the gcc4 transition going? Are we=20
close to the point where Qt3 can be uploaded? Also, are we proceeding under=20
the assumption that Qt3 is ours? I haven''t heard anything from Madkiss,
but=20
perhaps someone else has talked to him.

Cheers,
Chris

--nextPart1295360.j4jjWE0v9t
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Signed by Christopher Martin <chrsmrtn@freeshell.org>

iD8DBQBC00P7U+gWW+vtsysRAhU0AJ9mwgGX2b28bpf6QwhvX/7msVl/RACfdY6a
eU7XhR9/5eEI6YFXWcL5Yh4=QkX4
-----END PGP SIGNATURE-----

--nextPart1295360.j4jjWE0v9t--

On Tue, Jul 12, 2005 at 04:15:50AM +0000, Christopher Martin
wrote:
> On July 11, 2005 19:10, Adeodato Simó wrote:
> >   Wow, this is lots of good stuff. Way to go, Christopher! :)
> 
> Thanks, I just hope I haven''t messed anything up! Peer review,
especially,
> but not exclusively, from Brian Nelson (due to his Qt experience), would be
> really great.
OK, OK, I''ll try them out as soon as I get a chance.

[...]
> BTW, since I''m a little out of the loop (and will be for a few
more weeks at
> least, possibly much longer), how is the gcc4 transition going? Are we 
> close to the point where Qt3 can be uploaded? 
It looks like the firebird libs need to be transitioned first.  I''m not
sure if anything else is needed.

-- 
Society is never going to make any progress until we all learn to
pretend to like each other.

On Tue, Jul 12, 2005 at 04:15:50AM +0000, Christopher Martin
wrote:
> On July 11, 2005 19:10, Adeodato Simó wrote:
> >   Wow, this is lots of good stuff. Way to go, Christopher! :)
> 
> Thanks, I just hope I haven''t messed anything up! Peer review,
especially,
> but not exclusively, from Brian Nelson (due to his Qt experience), would be
> really great.
I haven''t tested any binaries yet, but I looked at a diff of the
changes
you made and everything looks OK to me so far.  Just a couple things to
point out:

* You changed the "firebird2-dev [darwin-i386 freebsd-i386 ...]"
  dependency to simply "firebird2-dev [i386]".  Do you know why it was
  done that way previously and if your change will have any negative
  effects?

* Since you''re removing libqt3-dev, you might want to make
libqt3-mt-dev
  provide it.  I''m not entirely sure that''s a good idea, but
it''s
  something to consider.

* You should apply the patch in #317500, or otherwise the package will
  FTBFS.

-- 
Society is never going to make any progress until we all learn to
pretend to like each other.

* Christopher Martin [Tue, 12 Jul 2005 04:15:50 +0000]:
> Hmmm, at first I leaned towards making all the changes at once, but as the 
> list of changes kept growing, I began to wonder whether a simple gcc 4.0 
> transition upload would be best, since I don''t feel I really can
myself
> certify that the changes are quite safe. This would mean two trips through 
> NEW, though.
  I propose this: import pristine 3:3.3.4-3 debian/ from qt-x11-free
  into svn:/trunk/packages/qt-x11-free, and commit the necessary changes
  for the C++ ABI transition and (see below) the x.org transition. Then,
  review your changes under people/, and cherry-pick the most urgent and
  safe ones, and review the rest. What do you think? (But see the end of
  this mail first.)
> All said, I certainly would understand if people wanted to act cautiously.
  Yeah. It''s not only being cautious for the sake of it, but in order
to
  have Qt sorted ASAP so that we can put KDE 3.4.1 in unstable. After
  that there should be lots of time to improve Qt3...
> BTW, since I''m a little out of the loop (and will be for a few
more weeks at
> least, possibly much longer), how is the gcc4 transition going? Are we 
> close to the point where Qt3 can be uploaded?
  X.org was uploaded to sid yesterday, and I agreed with vorlon that
  we''ll upload Qt3 as soon as it''s compiled in all
architectures.
> Also, are we proceeding under the assumption that Qt3 is ours? I
> haven''t heard anything from Madkiss, but perhaps someone else has
> talked to him.
  I''ve talked with him in private some days ago and he said it was OK.

* Brian Nelson [Mon, 11 Jul 2005 21:40:53 -0700]:
> It looks like the firebird libs need to be transitioned first.
  If we don''t get a timely fix from the maintainers (i.e., right before
  we''re ready to upload), we''ll disable firebird2 support
until it gets
  fixed. nchip, isaac and vorlon agree with this. (I''ll state this in
  #317314 now.)
> * You changed the "firebird2-dev [darwin-i386 freebsd-i386 ...]"
>   dependency to simply "firebird2-dev [i386]".  Do you know why
it was
>   done that way previously and if your change will have any negative
>   effects?
  
  Guillem Jover confirms that this is wrong. When a patch he''s working
  on gets integrated in dpkg, the long list will be substituted by
  [any-i386].
> * Since you''re removing libqt3-dev, you might want to make
libqt3-mt-dev
>   provide it.  I''m not entirely sure that''s a good idea,
but it''s
>   something to consider.
                                 * * *

  Let''s go over the changes a bit (also, I think it''d be great
to mark
  pending this bugs, so that another person trying to skim the list does
  not have a chance to spend time in those which already have a fix; the
  tagpending script from devscripts is handy to do this):
>  * Move the package to the Debian Qt/KDE team. Thanks to Martin Loschwitz
for
>    all his work over the years.
  I''d s/team/team, as agreed with the maintainer/. Also, I
wouldn''t put
  in Uploaders the standard KDE team line, just let anybody feeling like
  it to add himself.

  Changes that can go in for sure, and which I''ll cherry pick
  immediately:
>  * Add sundry fixes from KDE''s qt-copy. (Closes: #303065)
>  * Fix qt3-designer''s appearance in the KDE menu. (Closes:
#290402)
>  * Don''t use lib64 on amd64. (Closes: #311562)
>  * Add linguist manpage. Thanks to Jeremy Laine. (Closes: #268882)
>  * Don''t duplicate the information in the qvfb manpage. (Closes:
#282217)
  As Brian said, we''ll need PostgreSQL too:
> * You should apply the patch in #317500, or otherwise the package will
>   FTBFS.
  Changes I''ll try to review, as requested:
>  * No longer build non-threaded libraries. (Closes: #180326)
>  * Added a libqt3c102-mt-dbg package. (Closes: #235396)
>  * Make the Qt3 documentation available from /usr/share/doc/qt3-doc, and
>    therefore also usable in dwww and doc-central. (Closes: #185900)
>    (Closes: #284407, #294630)
>  * Include createcw source for qt3-designer. (Closes: #305919)
>  * Add missing qvfbhdr.h. (Closes: #182366)
>  * Bump libfreetype6-dev build-depends to >= 2.1.10 to work around API
>    breakage.
>  * Enable tablet support.
>  * Build jpeg and mng support into Qt, not as plugins.
>  * Many minor changes to improve lintian compliance.
>  * Revamp the OpenGL linking patch, and add patches for gcc4.
  Cheers,

-- 
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
 
When the only tool you have is a hammer, every problem starts to look
like a nail.

* Adeodato Simó [Tue, 12 Jul 2005 19:31:35 +0200]:
>   I propose this: import pristine 3:3.3.4-3 debian/ from qt-x11-free
>   into svn:/trunk/packages/qt-x11-free, and commit the necessary changes
>   for the C++ ABI transition and (see below) the x.org transition. Then,
>   review your changes under people/, and cherry-pick the most urgent and
>   safe ones, and review the rest. What do you think? (But see the end of
>   this mail first.)
  
  I''ve been doing this already...
>   Changes that can go in for sure, and which I''ll cherry pick
>   immediately:
> >  * Add sundry fixes from KDE''s qt-copy. (Closes: #303065)
> >  * Fix qt3-designer''s appearance in the KDE menu. (Closes:
#290402)
> >  * Don''t use lib64 on amd64. (Closes: #311562)
> >  * Add linguist manpage. Thanks to Jeremy Laine. (Closes: #268882)
> >  * Don''t duplicate the information in the qvfb manpage.
(Closes: #282217)
  
  Done. As you know, I''m a big fan of small commits, so that''s
the way I
  did all of these (and marked them pending).
>   As Brian said, we''ll need PostgreSQL too:
> > * You should apply the patch in #317500, or otherwise the package will
> >   FTBFS.
  Done too (slightly different patch).

  Also, I''ve got the x.org transition bits almost sorted out.
  Christopher, I''d like to hear if you had any work on progress re the
  C++ transition, so that I don''t start with it and we end up stepping
  onto each other''s toes. If not, I''ll get it done during
these days,
  unless for some reason you prefer to do it yourself.

  Cheers,

-- 
Adeodato Simó
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
 
The first step on the road to wisdom is the admission of ignorance. The
second step is realizing that you don''t have to blab it to the world.

--nextPart3866241.pYTIrR0Ub9
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On July 12, 2005 17:31, Adeodato Sim=F3 wrote:
>   I propose this: import pristine 3:3.3.4-3 debian/ from qt-x11-free
>   into svn:/trunk/packages/qt-x11-free, and commit the necessary changes
>   for the C++ ABI transition and (see below) the x.org transition. Then,
>   review your changes under people/, and cherry-pick the most urgent and
>   safe ones, and review the rest. What do you think? (But see the end of
>   this mail first.)
Sounds fine to me.
> > Also, are we proceeding under the assumption that Qt3 is ours? I
> > haven''t heard anything from Madkiss, but perhaps someone else
has
> > talked to him.
>
>   I''ve talked with him in private some days ago and he said it was
OK.
OK, glad to hear it.
> * Brian Nelson [Mon, 11 Jul 2005 21:40:53 -0700]:
> > It looks like the firebird libs need to be transitioned first.
>
>   If we don''t get a timely fix from the maintainers (i.e., right
before
>   we''re ready to upload), we''ll disable firebird2 support
until it gets
>   fixed. nchip, isaac and vorlon agree with this. (I''ll state this
in
>   #317314 now.)
>
> > * You changed the "firebird2-dev [darwin-i386 freebsd-i386
...]"
> >   dependency to simply "firebird2-dev [i386]".  Do you know
why it was
> >   done that way previously and if your change will have any negative
> >   effects?
>
>   Guillem Jover confirms that this is wrong. When a patch he''s
working
>   on gets integrated in dpkg, the long list will be substituted by
>   [any-i386].
Looks like I yanked out the type-handling/control.in stuff, but
didn''t=20
finish putting all relevant arches back in. Thanks for catching that.
> > * Since you''re removing libqt3-dev, you might want to make
> > libqt3-mt-dev provide it.  I''m not entirely sure
that''s a good idea,
> > but it''s something to consider.
Why would this be, if no one is using the non-threaded Qt packages?
>   Changes I''ll try to review, as requested:
> >  * No longer build non-threaded libraries. (Closes: #180326)
> >  * Added a libqt3c102-mt-dbg package. (Closes: #235396)
> >  * Make the Qt3 documentation available from /usr/share/doc/qt3-doc,
> > and therefore also usable in dwww and doc-central. (Closes: #185900)
> > (Closes: #284407, #294630)
> >  * Include createcw source for qt3-designer. (Closes: #305919)
> >  * Add missing qvfbhdr.h. (Closes: #182366)
> >  * Bump libfreetype6-dev build-depends to >=3D 2.1.10 to work
around API
> >    breakage.
> >  * Enable tablet support.
> >  * Build jpeg and mng support into Qt, not as plugins.
> >  * Many minor changes to improve lintian compliance.
> >  * Revamp the OpenGL linking patch, and add patches for gcc4.
Thanks. And thanks to Brian for having had a look as well.

Cheers,
Chris

--nextPart3866241.pYTIrR0Ub9
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Signed by Christopher Martin <chrsmrtn@freeshell.org>

iD8DBQBC1JvQU+gWW+vtsysRAr+vAJ9x2lj/3eGZLDxKR0c4pU/TD9kI+ACfXWZQ
vUt3Jwyi7Rp1h6e+Z9tGpbQ=4F9J
-----END PGP SIGNATURE-----

--nextPart3866241.pYTIrR0Ub9--

--nextPart1208558.SLg5j3oqQX
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On July 13, 2005 01:32, Adeodato Sim=F3 wrote:
>   Also, I''ve got the x.org transition bits almost sorted out.
Aside from the switch to libglu1-xorg-dev, have you looked at the splitting=20
out of most of xlibs-static-dev? The changelog line "XXX:
libxinerama-dev,=20
libxkbfile-dev, libxrandr-dev, libxi-dev" suggests you''ve already
done all=20
that work (thanks!), but just haven''t committed it yet.
>   Christopher, I''d like to hear if you had any work on progress re
the
>   C++ transition, so that I don''t start with it and we end up
stepping
>   onto each other''s toes. If not, I''ll get it done during
these days,
>   unless for some reason you prefer to do it yourself.
No, I''ve done nothing on this, so if you have time, all the better :)

Cheers,
Chris

--nextPart1208558.SLg5j3oqQX
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Signed by Christopher Martin <chrsmrtn@freeshell.org>

iD8DBQBC1JvxU+gWW+vtsysRAvu1AKCDcLTGX929W2SmpH8ONElVpOw+bQCghviq
Uhd+KAG5BDK/OAG+qb6Vg3I=0sBB
-----END PGP SIGNATURE-----

--nextPart1208558.SLg5j3oqQX--

* Christopher Martin [Wed, 13 Jul 2005 04:42:55 +0000]:
> On July 12, 2005 17:31, Adeodato Sim? wrote:
> >   Changes I''ll try to review, as requested:
  
  OK, of these I''ve moved to trunk these:
> > >  * Include createcw source for qt3-designer. (Closes: #305919)
> > >  * Add missing qvfbhdr.h. (Closes: #182366)
> > >  * Many minor changes to improve lintian compliance.
  It would be good if you had a look at the commits to check that I
  didn''t leave anything related out (these two revisions: 1324, 1321;
  did you have a chance to have a look at the previous ones as well?)
> > >  * Enable tablet support.
> > >  * Added a libqt3c102-mt-dbg package. (Closes: #235396)
  These two I prefer to leave for -5.
> > >  * Make the Qt3 documentation available from
/usr/share/doc/qt3-doc,
> > > and therefore also usable in dwww and doc-central. (Closes:
#185900)
> > > (Closes: #284407, #294630)
  I haven''t had a chance to look at this. -5 should be fine for it.
> > >  * Revamp the OpenGL linking patch, and add patches for gcc4.
  Mmm, let''s see: 31_gcc4_buildkey seems straightforward and I imagine
  I''ll probably need it when building -4. About 30_gcc4_build, I
suppose
  it''s necessary too, but I have no idea where does it come from. Can
  you explain a bit what is it for?

  And wrt OpenGL, mostly the same: is there a bug where this solution is
  discussed? Also, is it ok to leave it for -5?
> > >  * Bump libfreetype6-dev build-depends to >= 2.1.10 to work
around API
> > >    breakage.
> > >  * Build jpeg and mng support into Qt, not as plugins.
  I''m not against either of these, but I''d like to hear the
rationale
  behind them. Unless strictly necessary, not for -4.
> > >  * No longer build non-threaded libraries. (Closes: #180326)
  As for this one, I have not formed an opinion yet. I suggest we have a
  closer look after the KDE ABI transition is finished.

                                 * * *

  I intend to upload today or tomorrow, hopefully, depending on how fast
  xorg -3 gets built. Will be doing some test builds this evening.

  Cheers,
  
-- 
Adeodato Sim?
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
 
Testing can show the presence of bugs, but not their absence.
                -- Dijkstra

On July 18, 2005 09:51, Adeodato Sim? wrote:
> * Christopher Martin [Wed, 13 Jul 2005 04:42:55 +0000]:
> > On July 12, 2005 17:31, Adeodato Sim? wrote:
> > >   Changes I''ll try to review, as requested:
>
>   OK, of these I''ve moved to trunk these:
> > > >  * Include createcw source for qt3-designer. (Closes:
#305919)
> > > >  * Add missing qvfbhdr.h. (Closes: #182366)
> > > >  * Many minor changes to improve lintian compliance.
>
>   It would be good if you had a look at the commits to check that I
>   didn''t leave anything related out (these two revisions: 1324,
1321;
>   did you have a chance to have a look at the previous ones as well?)
They look complete, but I won''t be absolutely certain until I do a full
comparison between my personal Qt and the copy in trunk, to sort out all 
the changes I made. In retrospect, I wish I''d imported Qt3 to a version
control system before starting to mess with it, since my changes are hard 
to separate - sorry about this.
> > > >  * Enable tablet support.
> > > >  * Added a libqt3c102-mt-dbg package. (Closes: #235396)
>
>   These two I prefer to leave for -5.
Certainly.
> > > >  * Make the Qt3 documentation available from
> > > > /usr/share/doc/qt3-doc, and therefore also usable in dwww
and
> > > > doc-central. (Closes: #185900) (Closes: #284407, #294630)
>
>   I haven''t had a chance to look at this. -5 should be fine for
it.
IIRC it''s just a symlink, so it should be harmless, but it can also
wait.
> > > >  * Revamp the OpenGL linking patch, and add patches for
gcc4.
>
>   Mmm, let''s see: 31_gcc4_buildkey seems straightforward and I
imagine
>   I''ll probably need it when building -4. About 30_gcc4_build, I
suppose
>   it''s necessary too, but I have no idea where does it come from.
Can
>   you explain a bit what is it for?
>
>   And wrt OpenGL, mostly the same: is there a bug where this solution is
>   discussed? Also, is it ok to leave it for -5?
This stuff I borrowed from Fedora''s Qt, and is therefore
"experimental". The
changes to the GL patch make sense, but are more or less untested (so -5 
stuff). The gcc4 build patch was added for reasons of "we''ll
probably need
that when the transition occurs." Not yet having tried to build Qt with 
gcc4, I can''t say whether it really is required or not.
> > > >  * Bump libfreetype6-dev build-depends to >= 2.1.10 to
work around
> > > > API breakage.
> > > >  * Build jpeg and mng support into Qt, not as plugins.
>
>   I''m not against either of these, but I''d like to hear
the rationale
>   behind them. Unless strictly necessary, not for -4.
The libfreetype6-dev change is just to ensure that we and our users dodge 
bug #316031. 2.1.10 is now built on all arches in Sid, so it''s not
really
required. The image plug-in change was a little capricious, I admit, and 
I''ve since left mng as a plug-in, since it''s rarely used
compared to jpeg.
Seems like the usual memory vs. performance trade-off.
> > > >  * No longer build non-threaded libraries. (Closes: #180326)
>
>   As for this one, I have not formed an opinion yet. I suggest we have a
>   closer look after the KDE ABI transition is finished.
Nothing builds against these, so I felt it was time to clean up. This might 
be a change to publicly announce/RFC beforehand, though, so if people 
object we can reassess the situation.
>   I intend to upload today or tomorrow, hopefully, depending on how fast
>   xorg -3 gets built. Will be doing some test builds this evening.
Sounds good; thanks a lot for handling all this.

Cheers,
Chris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 252 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20050718/3347a8e8/attachment.pgp

* Christopher Martin [Mon, 18 Jul 2005 22:40:15 +0000]:
> > > > >  * Revamp the OpenGL linking patch, and add patches for
gcc4.
> >   Mmm, let''s see: 31_gcc4_buildkey seems straightforward and
I imagine
> >   I''ll probably need it when building -4. About
30_gcc4_build, I suppose
> >   it''s necessary too, but I have no idea where does it come
from. Can
> >   you explain a bit what is it for?
> The gcc4 build patch was added for reasons of "we''ll probably
need
> that when the transition occurs." Not yet having tried to build Qt
with
> gcc4, I can''t say whether it really is required or not.
  Seems to build fine here without it.
> The libfreetype6-dev change is just to ensure that we and our users dodge 
> bug #316031. 2.1.10 is now built on all arches in Sid, so it''s not
really
> required.
  OK, then I prefer not to use it.
> The image plug-in change was a little capricious, I admit, and 
> I''ve since left mng as a plug-in, since it''s rarely used
compared to jpeg.
> Seems like the usual memory vs. performance trade-off.
  Fair enough; is png is compiled in, jpg could as well. OTOH, we could
  ship the styles as plugins, opinions?
> >   I intend to upload today or tomorrow, hopefully, depending on how
fast
> >   xorg -3 gets built. Will be doing some test builds this evening.
> Sounds good
  xorg -3 has FTBFS on several arches, so...

-- 
Adeodato Sim?
    EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621
 
In my opinion, the most fruitful and natural play of the mind is in
conversation. I find it sweeter than any other action in life; and if I
were forced to choose, I think I would rather lose my sight than my
hearing and voice.
                -- Michel de Montaigne

On July 19, 2005 08:54, Adeodato Sim? wrote:
> * Christopher Martin [Mon, 18 Jul 2005 22:40:15 +0000]:
> > The gcc4 build patch was added for reasons of "we''ll
probably need
> > that when the transition occurs." Not yet having tried to build
Qt with
> > gcc4, I can''t say whether it really is required or not.
>
>   Seems to build fine here without it.
That''s good. Perhaps it was included to work-around a compiler problem
in an
earlier gcc4.
>   Fair enough; is png is compiled in, jpg could as well. OTOH, we could
>   ship the styles as plugins, opinions?
Sounds very reasonable, though I haven''t tested it (yet).
> > >   I intend to upload today or tomorrow, hopefully, depending on
how
> > > fast xorg -3 gets built. Will be doing some test builds this
evening.
> >
> > Sounds good
>
>   xorg -3 has FTBFS on several arches, so...
-4 seems to be doing better, though.

Cheers,
Chris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 252 bytes
Desc: not available
Url :
http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20050721/8ea3a2ba/attachment.pgp