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

Probably because it's not ready for the consumer market. Corporate desktops, yes, but home users with scanners, digital cameras, and other assorted bit and pieces without specific Linux drivers in the box, no.

For the most part I must agree with you. When I started using SuSE back in 7.1 it had somethings that were nice compared to the present versions, but obviously lacked in other areas that have been the focus of the newer/newest versions. One of the things that personally bothered me with no more yast1 since 8.0. I used to like it because you could point it at "any" directory that had rpms in it and you could use it as a general purpose installer/updater. This was especially nice if your video card driver had a problem, as well as gui updates done in init 3. I know that the latest kernel has many more drivers, so USB and other similar things are coming along. I have also had better luck with 3rd party party programs since 8.1 (and 8.2, despite gcc 3.3, 8.2 has been working well). Also, the latest version of Wine (coming with 8.2) actually is much better. I ran some games in it that did very well, games that had definite problems before now run pretty smoothly. There was a change to the way the new kernel handled things with Wine that was discussed both by the SuSE devs, Wine devs, and some other hackers. It had to do with __errno and __errno.h and the way Wine works with this. I have yet to notice anything problematic however. Perhaps it's just me, but I kinda get the feeling that SuSE will be focusing on something of a merge of sorts with the general versions and the Office Edition verson they sell for corporate office use. In the Office Edition they include the CodeWeaver's plugins - so they have licensed it. But I don't think this is going to happen with the Personal/Pro editions because of cost/support/license issues. But, this may change. I know that many home/SOHO users want to run Win apps. In the Office Edition you can do this a lot better out of the box. The CodeWeavers stuff has a gui installer/admin interface that comes with the Office Edition. The other issue is a more unified installer, something along the lines that comes with Windows (it's a 3rd party app - but pretty much everyone uses it, you know - InstallShield). Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+dfrZ7WVLiDrqeksRAvJdAKDa4tjZLoAmRNEfCFx31dzZXtT8QgCeK3Eg xgWV3i/TRx8Y+19eWfw7ftc= =KJf5 -----END PGP SIGNATURE-----

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

What I do is: I search for the rpm file in the Konquerer filemanager, click on the file, and a new button appears with the text 'Install Package with YAST'. This works very nice, and is much like Windows when (double) clickiing on a .exe file. (I am running 8.1). And it does work in 'any' directory. --

That's single package only though. In YaST1 I could hilight serveral. And a comparision between my installed and the ftp versions was done. So, updating the new kde would have been like this, hilight all "new" packages in base while in init 3, after install run SuSEconfig, repeat for dev packages, and then apps. With the konq/YaST2 option it's one package and only one package, Now at least they have included a "yast.source" list in the kde directorys on the SuSE ftp site (so you "change source location" and then move the kde source list to the top) that can be added to the Yast and will enable you to install package groups. Close, but not quite as flexible as it was previously. Cheers, Curtis. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+dlLI7WVLiDrqeksRAs8AAJ90xnpxsCn+ea8Zs0QZd0w7DhN0nQCfVxKU XauWhe8QZ6CiGYaV7ECy01k= =WcyK -----END PGP SIGNATURE-----

In a previous message, Carlos E. R. wrote:

The 03.03.17 at 22:40, Frits Wüthrich wrote:

...

What I do is: I search for the rpm file in the Konquerer filemanager, click on the file, and a new button appears with the text 'Install Package with YAST'.

Yes, but that installs a single package. With the old yast1, you could point it to any directory and install any of the rpms on it, choosing which you wanted and which not, on a single operation.

Also, this only works if you use Konqueror. We Gnome users do exist. Really! John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Valley of the Kings: ransack an ancient Egyptian tomb but beware of mummies!

Frits Wüthrich writes:

What I do is: I search for the rpm file in the Konquerer filemanager, click on the file, and a new button appears with the text 'Install Package with YAST'. This works very nice, and is much like Windows when (double) clickiing on a .exe file. (I am running 8.1). And it does work in 'any' directory.

That does not help when there are version dependencies involved. For example if you already have X-123.rpm and X-dev-123.rpm installed and you have a directory containing X-456.rpm and X-dev-456, just installing one at a time causes YaST to complain "X-dev-123 requires X = 123, please resolve this dependency problem." With just 2 this is not too bad, but when there are more complex interdependencies it is inconvenient at the very least.

The 03.03.22 at 13:10, Curtis Rey wrote:

Of course one can always tell YaST2 to ignore the dependencies and then install the packages, but this sometimes gets cranky.

Perhaps ignore the first time, the start Yast again to check for dependencies. Highly inlelegant... -- Cheers, Carlos Robinson