From kde-core-devel  Tue Nov 21 20:48:53 2006
From: Kevin Krammer <kevin.krammer () gmx ! at>
Date: Tue, 21 Nov 2006 20:48:53 +0000
To: kde-core-devel
Subject: Re: Okular moving
Message-Id: <200611212148.53231.kevin.krammer () gmx ! at>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=116414582713005
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart1365523.sdbmxhKeqy"

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

On Tuesday 21 November 2006 21:03, Leo Savernik wrote:
> Am Dienstag, 21. November 2006 12:18 schrieb Kevin Krammer:
> > > The current grouping gives invaluable hints to packagers which
> > > applications to bundle into meta-packages. If essential applications
> > > are moved out of "KDE - The Desktop Environment", we again have to re=
ly
> > > on distributors to grab those essentials from KEG and link them in
> > > their meta-packages.
> >
> > It mainly depends if packagers use the source packages we release or if
> > they do direct checkouts based on tags. In the first case repository
> > organisation can be different to release grouing, in the later we have =
to
> > adjust repository organisation to release needs.
>
> Is that true? Do the source packages really divert from what's contained =
in
> the svn-modules? I mean are they recomposed such that kdegraphics.tar.bz2,
> for instance, contains packages from, say, KEG? (I frankly don't know, i
> never build from source packages.)

No.but they could if we wanted to have installation packages tailored to us=
er=20
needs and still have source modules tailored to developer needs.

In developer terms: the source packages would be views on the repository da=
ta=20
modell

> > > Even worse, it will lead to a segregation of our user base as
> > > distributor x may choose suitable application A, while distributor y
> > > may choose suitable application B for the same purpose.
> >
> > I am sorry to tell you, but distributors already do this. There can be
> > huge differences between what we release and what the users get.
>
> True, but this doesn't inhibit KDE from providing a policy for "KDE - The
> Desktop Environment"'s constituents as intended by its makers. Currently,
> this policy becomes manifest in the release notes by listing the source
> packages. These can rightfully be considered to represent "KDE - The
> Desktop Environment". Distributors may chose to neglect that fact but they
> can't pretend they didn't know.

Just wanted to make sure everybody understands that "will lead to" is no=20
longer an option as it has already happend.

Cheers,
Kevin

=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart1365523.sdbmxhKeqy
Content-Type: application/pgp-signature

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

iD8DBQBFY2Y1nKMhG6pzZJIRApiOAJ9oD6Oin3WT1UHIRhXN5mKzjo2r6wCfRZpX
9E646VpgOi8zrBysdrybxVo=
=ycU4
-----END PGP SIGNATURE-----

--nextPart1365523.sdbmxhKeqy--