--nextPart8159536.oiQP0eUcOX
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On February 24, 2007, Kevin Krammer wrote:
> If the signal to packager is that kdebase without tools is consider enough
> for a dependency of a kde-core metapackage, then tools like kdialog,
> kread/kwriteconfig need to be in runtime.
>
> If the signal is that this is purely a matter of internal organisation and
> that packages should treat binaries in tools like binaries in runtime, e.=
g.
> have them both in a kdebase-bin package, then I see no problem.

i think this is up to packagers at the end of the day no matter what we do.=
=20
this simply helps categorize things "properly". a proper kde-core metapacka=
ge=20
would indeed include runtime/ and tools/ (and apps/ too, imho), but=20
the -minimal dependency- from kdebase for an end-user application is=20
runtime/.

jakob is quite right about the oddness of including only some scripting=20
requirements and not others, but i figured i wouldn't go there ... now that=
=20
someone has, it's quite true as far as showing why we don't shove every=20
scripting support facility into runtime/ ... or maybe we do and include=20
things like the kommander runtime.

speaking of kommander, i'd personally like to see it in kdebase/tools/ (or=
=20
runtime/tools/, whatever) so that it's more dependably reliable. if we ship=
=20
kdialog, not shipping kommander is a bit odd. we provide kdialog in part=20
because of xdialog, no doubt, but kommander is ++xdialog so not having it=20
there seems like we're missing an opportunity.

just imagine how much more popular kommander utilities would be if everyone=
=20
had the runtime? =3D)

i'm cc'ing the kommander team as this is my invitation to them to discuss t=
his=20
possibility.

=2D-=20
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

=46ull time KDE developer sponsored by Trolltech (http://www.trolltech.com)

--nextPart8159536.oiQP0eUcOX
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQBF4J6O1rcusafx20MRAnZbAKCOab8jIN+LYi37bu1ZVkmZWW+PHwCgh5DB
oweWVvy2fELF9Zdu4mO0SnI=
=mJWI
-----END PGP SIGNATURE-----

--nextPart8159536.oiQP0eUcOX--