[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Qt Changes ahead - Info for package maintainers + developers



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Montag, 10. Februar 2003 12:42, Ben Burton wrote:
> > OTOH Qt should be found fine through the search pathes
> > admin uses for looking through configure for it automatically.
>
> So you're saying that even if debianrules isn't updated, things should
> still build?  So this means that calc and I *don't* need to reupload our
> modules, yes?

I did a recompile of Qt, arts, kdelibs and kdebase and the rest of my stuff 
still works fine. I think kdebase and kdelibs still need updating, at least 
kdelibs because of the designer and plugin stuff - but I don't see any 
specifics there yet why you need to do that. 

To be on the safe side I would rebuild from the branch *after* we changed the 
Qt packages. We're still fiddling out some minor issues like that the static 
development files for libdesigner and co are shredded useless through 
dh_strip :-)

Please wait with rebuild after Martin has fixed the issues and uploaded his qt 
packages to incoming. Calc, we need to still fix the dh-make template in 
kdelibs to make sense for third party packages by shipping a correct 
debiandirs file in it.
>
> (Though of course given that this is the first upload in nine months,
> we'll almost certainly be reuploading some time soon; I just want to be
> sure I understand the implications of this change.)

You may want to switch to the above mentioned debiandirs file or update the 
ones from the in your third party apps packages, but it should even work 
without doing that.

Ralf
>
> Ben.

- -- 
We're not a company, we just produce better code at less costs.
- --------------------------------------------------------------------
Ralf Nolden
nolden@kde.org

The K Desktop Environment       The KDevelop Project
http://www.kde.org              http://www.kdevelop.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+R5vUu0nKi+w1Ky8RAvXWAJ9qfAbaTI6UHAgGIbJUbsl3ZlGMGACfdivw
B2zV5XNsPTNAWxbkLfdjvRQ=
=MJ9q
-----END PGP SIGNATURE-----




Reply to: