36

Then those issues need to be fixed

Here's an issue on Bugzilla for sound packages, but its for Kcontrol: https://bugs.kde.org/show_bug.cgi?id=13949

Angel Blue01 wrote:Then those issues need to be fixed

I totaly agree!

There's so much stuff that could be distributed via GHNS/KNewStuff that it's ridiculous they're not! I understand that it's probably not always easy to implement it, but it'd make everything so much better!

I do not want to slow you down, but I'm quite sure this won't fix (in Bugzilla-speak) because it opens a giant security hole (as in: big enough for Trudy to slip through).

Take Plasma widgets: Script widgets may only use a safe portion of the Plasma API, and (because of the nature of script language implementations) they're not able to access any system functions. Our developers ensure that the API exposed to scripted widgets is just big enough to be useful, and small enough to not be unsafe.

This is not true for compiled stuff. It might always #include anything and break your system (or just comprise it in any other form). Of course, this is true for everything you download and compile, but if you compile something manually, you think twice about whether you trust this code. On the other side, GHNS stuff is just seen as "content" by the most users, and we've seen earlier how malicious "content" can overwhelm users (even JPGs have already been used in trojan attacks).

When you download and compile stuff, it takes a lot of time to find the app. But then you do "download, mkdir build, cd build, cmake .., make, sudo make install". That is not a progress of thinking twice. KNewStuff can speed up the searching. The time for compiling is only a few seconds shorter.
Also in Python or Ruby you can import some files and then you can modify the filesystem. What's the difference?

In my own opinion this is very important thing to make Linux more user-friendly.

I install Kubuntu 9.04 recently and I just want that basic functionality is out-of-box. If I want to have system where I need to configure a lot of thinks I install Debian.
And I can't tell to my friends that they have to compile plasmoids before they can use it. It is too difficult for more of them and it's take too much time to resolve dependency problem. Instead of that I don't have time to install new version of plasmoids with I'm using.

I'm not expert of compiling things, but If you compile plasmoid in e.g. Kubuntu with KDE 4.2.2 I can use it in openSuse with KDE 4.2.2 too.

If you are worry about security it is possible to make KNewStuff security policy - e.g. moderator have to accept plasmoid before it is make available to install by KDE widget.

A packagemanager is also a security-hole.

Couldn't the thread be moved back to the main-forum? It's really hot stuff and who is interested in this silly bugzilla-suggestion? Nobody.

Sorry, there was not edit-button.

Here’s a silly thought…

Would moving to Bodega help in any way?

Regarding the sharing of the binary executables, this could probably be done by Nix or similar package manager. Nix is a purely functional package manager and if there is a correct binary ready on the servers, it pulls that, if not it compiles locally.