Opposition to removing old KWin themes?

Jos Poortvliet jospoortvliet at gmail.com
Wed Jul 28 09:15:38 BST 2010

On Tuesday 27 July 2010 11:36:15 Sune Vuorela wrote:
> On 2010-07-27, Ryan Rix <ry at n.rix.si> wrote:
> > --nextPart1479901.1coHzoFMlS
> > Content-Type: Text/Plain;
> >   charset="iso-8859-1"
> > Content-Transfer-Encoding: quoted-printable
> >
> > On Tue 27 July 2010 00:04:47 Sune Vuorela wrote:
> >> Both are compiled code, and that should not be shipped over GHNS.
> >
> > Good bye applets on kde-look? Yes, most of them are scripted now, but many=
> >=20
> > *are* compiled code still.
> >
> > Not saying you arne't right, but just saying that more compiled stuff goes=
> >=20
> > over GHNS than you think :)
> yes. also good bye applets on kde-look, at least to be distributed over
> There should not be distributed compiled code thru GHNS, as it will lead
> to various hard-to-trace segfaults and stuff.

GHNS was never meant to distribute compiled code. Plasma applets can be written in any language - GHNS currently just lacks the ability to properly detect if it can install something (javascript, python, perl etc) or not (compiled code with no package for the relevant platform). With the openSUSE buildserver integration coming to kde-apps and kde-look you can easily build packages for 11 platforms at once (mostly versions of suse, ubuntu, mandriva and fedora). This should make it possible for a revised ghns to even distribute compiled code (eg app store like). Pretty cool stuff. Even Win and Mac should at some point be supported.

So GHNS simply lacks the ability to detect if a package is properly installable before it downloads it (this also goes for content where the download link redirects to some webpage where you can download the stuff, instead of to a file). This doesn't mean it doesn't work in many cases, and hopefully frank and the other GHNS peeps can fix this in the future.


More information about the kde-core-devel mailing list