[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KDE Development Policy
From:       Ingo =?iso-8859-1?q?Kl=F6cker?= <ingo.kloecker () epost ! de>
Date:       2002-03-09 17:40:08
[Download RAW message or body]

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

On Saturday 09 March 2002 17:37, Stephan Kulow wrote:
> On Samstag, 9. März 2002 16:33, Matthias Welwarsky wrote:
> > blatantly ignorant. Did you think about the translators or the
> > documentation writers? Will the change affect them, too? Will they
> > be able to handle the situation?
>
> Actually we only commited this after Lauri confirmed it works for
> her. We also expect our translators/doc writers to update qt on their
> own, why do you think autoconf is that special?

The difference is that qt is in qt-copy (and therefore it's as easy as 
cd $QTDIR; cvs up; make -f Makefile.cvs; configure <some options>; make 
<some packages>) but autoconf wasn't on cvs.kde.org the last time I 
checked. Luckily I could install the SuSE 7.3 autoconf.rpm on SuSE 7.2. 
But I'm quite experienced and our translators might have difficulties 
with this especially if there isn't an appropriate rpm (or whatever) 
for their distribution.
But as this issue has been solved in the meantime (Thanks Stephan!) 
everything is fine again.

> We didn't ask to
> compile the kernel with some extraordinary option - we only asked to
> install a m4 macro package.

Installing is probably not the problem. But before you can install it 
you have to find it in the first place. A link to this package and some 
information about how to install it would have been very nice.

Regards,
Ingo

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8ikj4GnR+RTDgudgRAtTRAKCT7JybDvx9l0jKEHXciOxHLhATxACgzUyp
w1gj14Wq2y2hI3zGNS60aDw=
=B52j
-----END PGP SIGNATURE-----
[prev in list] [next in list] [prev in thread] [next in thread]