[opensuse-factory] Yast improvment ide?
Hi, I just want to air an idea regarding Yast. We are using SLES and openSUSE in the company as our main Linux offering.Yast is the keys to why we use those in stead of anything else. But it's no supprise that most of our newcommers have never used Linux before (We are a 90% SW company and still....) Yast is then a very good starting point for them. One thing that is an obstacle is that not all services that Yast can provide are easily visible and this is where my ide comes inn. would it be possible/nice etc. to have an extra tab in the Yast Controll Senter section that reads something like "Uninstalled servers and services". In this sectio would all uninstalled yast options be listed. I think this would greatly help newcommers to find their way around all the possibilities that are present. If there is anyone else who thinks this might be usefull, then I'll add it as an improvement suggestion. cu / birger.... Devoteam Telecom Norway AS --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Birger Kollstrand napsal(a):
Hi,
I just want to air an idea regarding Yast.
We are using SLES and openSUSE in the company as our main Linux offering.Yast is the keys to why we use those in stead of anything else.
But it's no supprise that most of our newcommers have never used Linux before (We are a 90% SW company and still....)
Yast is then a very good starting point for them. One thing that is an obstacle is that not all services that Yast can provide are easily visible and this is where my ide comes inn.
would it be possible/nice etc. to have an extra tab in the Yast Controll Senter section that reads something like "Uninstalled servers and services". In this sectio would all uninstalled yast options be listed.
I think this would greatly help newcommers to find their way around all the possibilities that are present.
If there is anyone else who thinks this might be usefull, then I'll add it as an improvement suggestion.
cu / birger....
Devoteam Telecom Norway AS --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
I think that yast-devel list (yast-devel@opensuse.org) is ideal for this improvement or add it to bugzilla like enhancement. JReidinger --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
sounds interesting 2008/8/25 Birger Kollstrand <birger.kollstrand@googlemail.com>:
Hi,
I just want to air an idea regarding Yast.
We are using SLES and openSUSE in the company as our main Linux offering.Yast is the keys to why we use those in stead of anything else.
But it's no supprise that most of our newcommers have never used Linux before (We are a 90% SW company and still....)
Yast is then a very good starting point for them. One thing that is an obstacle is that not all services that Yast can provide are easily visible and this is where my ide comes inn.
would it be possible/nice etc. to have an extra tab in the Yast Controll Senter section that reads something like "Uninstalled servers and services". In this sectio would all uninstalled yast options be listed.
I think this would greatly help newcommers to find their way around all the possibilities that are present.
If there is anyone else who thinks this might be usefull, then I'll add it as an improvement suggestion.
cu / birger....
Devoteam Telecom Norway AS --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi,
would it be possible/nice etc. to have an extra tab in the Yast Controll Senter section that reads something like "Uninstalled servers and services". In this sectio would all uninstalled yast options be listed.
this is a great idea! I think it would be really usefull. It even happened to me and I have been using S.U.S.E product for a long time, that I configured a service by hand just to find out there is a YaST module that does it ... great idea Felix Möller --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Felix Möller wrote:
Hi,
would it be possible/nice etc. to have an extra tab in the Yast Controll Senter section that reads something like "Uninstalled servers and services". In this sectio would all uninstalled yast options be listed.
this is a great idea! I think it would be really usefull. It even happened to me and I have been using S.U.S.E product for a long time, that I configured a service by hand just to find out there is a YaST module that does it ...
We wanted to have such a feature in YaST control center in openSUSE 11.0 but still haven't found a good solution. The idea was to have a dimmed icon (desktop file) of a not yet installed YaST module. The problem is that such an icon would be in conflict with already installed modules (and their icons). Bye Lukas
On Tuesday 26 August 2008 03:36:55 am Lukas Ocilka wrote:
Felix Möller wrote:
Hi,
would it be possible/nice etc. to have an extra tab in the Yast Controll Senter section that reads something like "Uninstalled servers and services". In this sectio would all uninstalled yast options be listed.
this is a great idea! I think it would be really usefull. It even happened to me and I have been using S.U.S.E product for a long time, that I configured a service by hand just to find out there is a YaST module that does it ...
We wanted to have such a feature in YaST control center in openSUSE 11.0 but still haven't found a good solution.
The idea was to have a dimmed icon (desktop file) of a not yet installed YaST module. The problem is that such an icon would be in conflict with already installed modules (and their icons).
Bye Lukas
Tab1 "Installed modules" Tab2 "Not installed modules" with bold text that those modules have to be installed first. Tab3 "Bug report modules" ... TabN "Not yet written modules" ;-) Or, instead of Tab1 and 2, just 2 columns, [mark, click and hold, move to other side] will express wish to install or remove module. -- Regards, Rajko --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Lukas Ocilka wrote:
Felix Möller wrote:
Hi,
would it be possible/nice etc. to have an extra tab in the Yast Controll Senter section that reads something like "Uninstalled servers and services". In this sectio would all uninstalled yast options be listed.
this is a great idea! I think it would be really usefull. It even happened to me and I have been using S.U.S.E product for a long time, that I configured a service by hand just to find out there is a YaST module that does it ...
We wanted to have such a feature in YaST control center in openSUSE 11.0 but still haven't found a good solution.
The idea was to have a dimmed icon (desktop file) of a not yet installed YaST module. The problem is that such an icon would be in conflict with already installed modules (and their icons).
Hi, I've just finished a brand-new RPM package that makes YaST Control Center to list not-yet-installed YaST modules too (in a special tab). See: http://kobliha-suse.blogspot.com/2008/08/yast-can-list-not-yet-installed-mod... Honestly, it currently makes YaST Control Center to list /ALL/, not only those /not-yet-installed/ ones, that would need yet another change in Control Center or a better idea how to solve it in general :) ;) Ideas and comments are welcome! ;) Bye && Thx Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.
Hi, Sounds great!!! regards, Luiz Fernando 2008/8/29 Lukas Ocilka <lukas.ocilka@suse.cz>:
Lukas Ocilka wrote:
Felix Mšöller wrote:
Hi,
would it be possible/nice etc. to have an extra tab in the Yast Controll Senter section that reads something like "Uninstalled servers and services". In this sectio would all uninstalled yast options be listed.
this is a great idea! I think it would be really usefull. It even happened to me and I have been using S.U.S.E product for a long time, that I configured a service by hand just to find out there is a YaST module that does it ...
We wanted to have such a feature in YaST control center in openSUSE 11.0 but still haven't found a good solution.
The idea was to have a dimmed icon (desktop file) of a not yet installed YaST module. The problem is that such an icon would be in conflict with already installed modules (and their icons).
Hi,
I've just finished a brand-new RPM package that makes YaST Control Center to list not-yet-installed YaST modules too (in a special tab).
See: http://kobliha-suse.blogspot.com/2008/08/yast-can-list-not-yet-installed-mod...
Honestly, it currently makes YaST Control Center to list /ALL/, not only those /not-yet-installed/ ones, that would need yet another change in Control Center or a better idea how to solve it in general :) ;)
Ideas and comments are welcome! ;)
Bye && Thx Lukas
--
Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi Lukas On Fr 29 Aug 2008 17:04:49 CEST ¡ElCheVive! <elchevive68@gmail.com> wrote:
I've just finished a brand-new RPM package that makes YaST Control Center to list not-yet-installed YaST modules too (in a special tab).
See: http://kobliha-suse.blogspot.com/2008/08/yast-can-list-not-yet-installed-mod...
Honestly, it currently makes YaST Control Center to list /ALL/, not only those /not-yet-installed/ ones, that would need yet another change in Control Center or a better idea how to solve it in general :) ;)
Ideas and comments are welcome! ;)
I'm thinking about an easy solution => What about creating "yast2-<module>-installme" packages? Those "installme" packages: 1) have a "dimmed" icon (and desktop file) for the section where the normal module will be installed 2) have a special desktop file which lists them in your "Not Yet Installed" section The normal "yast2-<module>" packages will provide/obsolete their corresponding "yast2-<module>-installme" packages. The "installme" packages should be very small as they just have a desktop-file and an icon-file and should be recommended by one your new yast2-not-yet-installed module (or another yast2-) package which is recommended in the yast2 pattern. As result, you should get the best of both ideas - dimmed icons and an extra section for non-installed modules and the possibility for "experts" to skip the whole stuff. With kind regards, Lars --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Lars Vogdt wrote:
Hi Lukas
Ideas and comments are welcome! ;)
I'm thinking about an easy solution => What about creating "yast2-<module>-installme" packages?
Those "installme" packages: 1) have a "dimmed" icon (and desktop file) for the section where the normal module will be installed 2) have a special desktop file which lists them in your "Not Yet Installed" section
The normal "yast2-<module>" packages will provide/obsolete their corresponding "yast2-<module>-installme" packages.
The "installme" packages should be very small as they just have a desktop-file and an icon-file and should be recommended by one your new yast2-not-yet-installed module (or another yast2-) package which is recommended in the yast2 pattern.
As result, you should get the best of both ideas - dimmed icons and an extra section for non-installed modules and the possibility for "experts" to skip the whole stuff.
Idea yast2-<module>-installme packages sounds good. 1.) Solves the problem with different icons (dimming could be done automagically while building the package / but it would ignore different YaST themes and we still haven't decided how we could include an icon in YaST package). 2.) The same way I did it I guess (but this would be "per package" instead of "all in one"). Honestly, I'm not sure how the provides/obsoletes works in libzypp by I'd assume new package (e.g., yast2-dns-server) just silently replaces the 'old' one (e.g., yast2-dns-server-installme). Could this work if both packages were on the same media conflicting with each other? Anyway, if it worked, we wouldn't have to change any of the current YaST Control Centers (Qt, GTK, ncurses). This idea sounds like a more generic solution and a package could but needn't provide its "-installme" subpackage but on the other hand creating such a product with all the dependencies would be more complicated. BTW: Do we really want to have 'approximately' (rpm -qa | grep yast2 | wc -l) -> 117 new packages? L.
Lukas Ocilka wrote:
Idea yast2-<module>-installme packages sounds good.
1.) Solves the problem with different icons (dimming could be done automagically while building the package / but it would ignore different YaST themes and we still haven't decided how we could include an icon in YaST package).
2.) The same way I did it I guess (but this would be "per package" instead of "all in one").
...
BTW: Do we really want to have 'approximately' (rpm -qa | grep yast2 | wc -l) -> 117 new packages?
100 new packages is really too much I'd say. We (Stano and I) have found how to solve the *themes issue*: we could just build one all-yast-desktop-files package for each YaST-theme package and change the current control centers to deal with it properly. L.
VGhpcyBsb29rcyBncmVhdCEgUmVhbHksIHJlYWx5IEdSRUFUIQoKTXVjaCBiZXR0ZXIgdGhhbiBJIGhhZCBob3BlZCBmb3IuCgpJIGNoZWRrZWQgeW91ciBibG9nIHBvc3QgYW5kIHdvbmRlciBob3cgeW91IGFxdWlyZSB0aGUgbGlzdCBvZiBhbGwKWWFTVCBwYWNrYWdlcyBhbmQgdGhlaXIgZGVza3RvcCBmaWxlcz8KClJlZ2FyZHMgQmlyZ2VyCgoyMDA4LzgvMjkgTHVrYXMgT2NpbGthIDxsdWthcy5vY2lsa2FAc3VzZS5jej46Cj4gTHVrYXMgT2NpbGthIHdyb3RlOgo+Pgo+PiBGZWxpeCBNxaHDtmxsZXIgd3JvdGU6Cj4+Pgo+Pj4gSGksCj4+Pgo+Pj4KPj4+PiB3b3VsZCBpdCBiZSBwb3NzaWJsZS9uaWNlIGV0Yy4gdG8gaGF2ZSBhbiBleHRyYSB0YWIgaW4gdGhlIFlhc3QKPj4+PiBDb250cm9sbCBTZW50ZXIgc2VjdGlvbiB0aGF0IHJlYWRzIHNvbWV0aGluZyBsaWtlICJVbmluc3RhbGxlZCBzZXJ2ZXJzCj4+Pj4gYW5kIHNlcnZpY2VzIi4gSW4gdGhpcyBzZWN0aW8gd291bGQgYWxsIHVuaW5zdGFsbGVkIHlhc3Qgb3B0aW9ucyBiZQo+Pj4+IGxpc3RlZC4KPj4+Cj4+PiB0aGlzIGlzIGEgZ3JlYXQgaWRlYSEgSSB0aGluayBpdCB3b3VsZCBiZSByZWFsbHkgdXNlZnVsbC4gSXQgZXZlbgo+Pj4gaGFwcGVuZWQgdG8gbWUgYW5kIEkgaGF2ZSBiZWVuIHVzaW5nIFMuVS5TLkUgcHJvZHVjdCBmb3IgYSBsb25nIHRpbWUsIHRoYXQgSQo+Pj4gY29uZmlndXJlZCBhIHNlcnZpY2UgYnkgaGFuZCBqdXN0IHRvIGZpbmQgb3V0IHRoZXJlIGlzIGEgWWFTVCBtb2R1bGUgdGhhdAo+Pj4gZG9lcyBpdCAuLi4KPj4KPj4gV2Ugd2FudGVkIHRvIGhhdmUgc3VjaCBhIGZlYXR1cmUgaW4gWWFTVCBjb250cm9sIGNlbnRlciBpbiBvcGVuU1VTRSAxMS4wCj4+IGJ1dCBzdGlsbCBoYXZlbid0IGZvdW5kIGEgZ29vZCBzb2x1dGlvbi4KPj4KPj4gVGhlIGlkZWEgd2FzIHRvIGhhdmUgYSBkaW1tZWQgaWNvbiAoZGVza3RvcCBmaWxlKSBvZiBhIG5vdCB5ZXQgaW5zdGFsbGVkCj4+IFlhU1QgbW9kdWxlLiBUaGUgcHJvYmxlbSBpcyB0aGF0IHN1Y2ggYW4gaWNvbiB3b3VsZCBiZSBpbiBjb25mbGljdCB3aXRoCj4+IGFscmVhZHkgaW5zdGFsbGVkIG1vZHVsZXMgKGFuZCB0aGVpciBpY29ucykuCj4KPiBIaSwKPgo+IEkndmUganVzdCBmaW5pc2hlZCBhIGJyYW5kLW5ldyBSUE0gcGFja2FnZSB0aGF0IG1ha2VzIFlhU1QgQ29udHJvbCBDZW50ZXIgdG8KPiBsaXN0IG5vdC15ZXQtaW5zdGFsbGVkIFlhU1QgbW9kdWxlcyB0b28gKGluIGEgc3BlY2lhbCB0YWIpLgo+Cj4gU2VlOgo+IGh0dHA6Ly9rb2JsaWhhLXN1c2UuYmxvZ3Nwb3QuY29tLzIwMDgvMDgveWFzdC1jYW4tbGlzdC1ub3QteWV0LWluc3RhbGxlZC1tb2R1bGVzLmh0bWwKPgo+IEhvbmVzdGx5LCBpdCBjdXJyZW50bHkgbWFrZXMgWWFTVCBDb250cm9sIENlbnRlciB0byBsaXN0IC9BTEwvLCBub3Qgb25seQo+IHRob3NlIC9ub3QteWV0LWluc3RhbGxlZC8gb25lcywgdGhhdCB3b3VsZCBuZWVkIHlldCBhbm90aGVyIGNoYW5nZSBpbgo+IENvbnRyb2wgQ2VudGVyIG9yIGEgYmV0dGVyIGlkZWEgaG93IHRvIHNvbHZlIGl0IGluIGdlbmVyYWwgOikgOykKPgo+IElkZWFzIGFuZCBjb21tZW50cyBhcmUgd2VsY29tZSEgOykKPgo+IEJ5ZSAmJiBUaHgKPiBMdWthcwo+Cj4gLS0KPgo+IEx1a2FzIE9jaWxrYSwgWWFTVCBEZXZlbG9wZXIgICAgICAgICAgICAgICAgICAgICAoeG4tLWx1ay1nbGE0NWQpCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KPiBBbm8sIGFuby4gTW91ZHJ5IHJvemthei4gU2FtIGpzZW0gbmVtZWwgdiB0ZWNoIGdyYXR1bGFjaWNoIGphc25vLgo+Cj4K---------------------------------------------------------------------To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.orgFor additional commands, e-mail: opensuse-factory+help@opensuse.org
Birger Kollstrand wrote:
This looks great! Realy, realy GREAT!
Thanks :D
Much better than I had hoped for.
I chedked your blog post and wonder how you aquire the list of all YaST packages and their desktop files?
Well, this must be done somehow manually (or by script [1]) but we have an internal tool (PDB Package DataBase) that allows this query: PACKAGES=`pdb query --release stable-i386 --filter "rpmfile:/usr/share/applications/YaST2/*" --attribs packname | xargs` [2] Frankly, I had to manually edit the list as some obsolete or non-openSUSE packages were listed. -- Bye Lukas [1] https://build.opensuse.org/package/show?package=yast2-desktop-files-openSUSE&project=home%3Alocilka [2] https://build.opensuse.org/package/view_file?file=update_list_of_packages.sh&package=yast2-desktop-files-openSUSE&project=home%3Alocilka
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lukas Ocilka schrieb:
Birger Kollstrand wrote:
This looks great! Realy, realy GREAT!
Thanks :D
Much better than I had hoped for.
I chedked your blog post and wonder how you aquire the list of all YaST packages and their desktop files?
Well, this must be done somehow manually (or by script [1]) but we have an internal tool (PDB Package DataBase) that allows this query: PACKAGES=`pdb query --release stable-i386 --filter "rpmfile:/usr/share/applications/YaST2/*" --attribs packname | xargs` [2]
Frankly, I had to manually edit the list as some obsolete or non-openSUSE packages were listed.
I am sorry to include myself in this discussion so lately, but I believe I have to admit one thing: I totally dislike the idea of filling yast with even more tabs and options... it is full enough already. I would rather set up a simple webpage where yast modules can be installed via ymp. This way those (not-installed) modules would be kept out out of yast as well as they could be easily grouped (like "server", "hardware", etc) on the webpage. The only thing in yast I might include might be a button "install yast modules" in the software menu. HTH Felix -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIvTjbaQ44ga2xxAoRAsCsAJ43QSSKvH3PM+m5gTPVchjhVU5sqgCeLjCD oSobaQPliAzPsxwKTWSlIcw= =D9Zn -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, I dislike the idea of a new web page for install yast modules. Much probably no one will note this and use it, because the users will not know that there are other yast modules than the ones installed by default. Thats the main reason of this new module. regards, Luiz 2008/9/2 Felix-Nicolai Müller <fnmueller@opensuse.org>:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Lukas Ocilka schrieb:
Birger Kollstrand wrote:
This looks great! Realy, realy GREAT!
Thanks :D
Much better than I had hoped for.
I chedked your blog post and wonder how you aquire the list of all YaST packages and their desktop files?
Well, this must be done somehow manually (or by script [1]) but we have an internal tool (PDB Package DataBase) that allows this query: PACKAGES=`pdb query --release stable-i386 --filter "rpmfile:/usr/share/applications/YaST2/*" --attribs packname | xargs` [2]
Frankly, I had to manually edit the list as some obsolete or non-openSUSE packages were listed.
I am sorry to include myself in this discussion so lately, but I believe I have to admit one thing: I totally dislike the idea of filling yast with even more tabs and options... it is full enough already.
I would rather set up a simple webpage where yast modules can be installed via ymp. This way those (not-installed) modules would be kept out out of yast as well as they could be easily grouped (like "server", "hardware", etc) on the webpage. The only thing in yast I might include might be a button "install yast modules" in the software menu.
HTH Felix -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux)
iD8DBQFIvTjbaQ44ga2xxAoRAsCsAJ43QSSKvH3PM+m5gTPVchjhVU5sqgCeLjCD oSobaQPliAzPsxwKTWSlIcw= =D9Zn -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
¡ElCheVive! wrote:
Hi,
I dislike the idea of a new web page for install yast modules. Much probably no one will note this and use it, because the users will not know that there are other yast modules than the ones installed by default. Thats the main reason of this new module.
Let's say "new feature" of YaST Control Center(s) :) And yes, I also wouldn't be happy with introducing yet another YaST page with unexpected content and unknown maintainer. The reason of the current solution (or similar) is to have all-in-one. Having all in extra package(s) also means: you don't need to install it/them - which actually means: you wouldn't see those icons at all. L.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ¡ElCheVive! schrieb:
Hi,
I dislike the idea of a new web page for install yast modules. Much probably no one will note this and use it, because the users will not know that there are other yast modules than the ones installed by default. Thats the main reason of this new module.
Yast needs to become slicker and not even more crowded with more symbols. It does not even matter if those modules are dimmed or not. A regular desktop user (the main audience I believe) will rather breake seomthing using ssh-manager or apache-manager, etc and will get confused. An icon pointing to a website would not be less obvious than a community module on yast. Another possibility would be to have a new section in yast-sw-installer which only deals with yast modules. Or to create a new module that only lists not yet installed modules. In any case, I would keep yast as simple and clean as possible. Introducing (dimmed) icons to the regular sections contradicts the effort that has already been made to make yast slicker. Sadly, this task was only begun for 11.0. greetings Felix -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIvU1kaQ44ga2xxAoRAlaqAKCTVX2RqPHbtetmyqF7F3+vJMj1RQCgt5Tg P+gPgxMOPS/zIrcQ/3ZRw6c= =m/2+ -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2008/9/2 Felix-Nicolai Müller <fnmueller@opensuse.org>:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Another possibility would be to have a new section in yast-sw-installer which only deals with yast modules. Or to create a new module that only lists not yet installed modules.
Thats the idea, a module that shows only the non installed modules. In the first draft Lucas did, it show all modules, but its a draft... (http://kobliha-suse.blogspot.com/2008/08/yast-can-list-not-yet-installed-mod...) regards, Luiz --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Felix-Nicolai Müller wrote:
¡ElCheVive! schrieb:
Hi,
I dislike the idea of a new web page for install yast modules. Much probably no one will note this and use it, because the users will not know that there are other yast modules than the ones installed by default. Thats the main reason of this new module. ...
Another possibility would be to have a new section in yast-sw-installer which only deals with yast modules. Or to create a new module that only lists not yet installed modules.
In any case, I would keep yast as simple and clean as possible. Introducing (dimmed) icons to the regular sections contradicts the effort that has already been made to make yast slicker. Sadly, this task was only begun for 11.0.
And that's actually the case, I've created *new* YaST Control Center group that lists them, they're not listed in the same groups with the already installed YaST modules. Stano has (personally) pointed out that we could even change YaST Control Center to use tabs: one for installed modules (the same way it does now) another for not yet installed ones (using the current groups but with dimmed icons). L.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lukas Ocilka schrieb:
Felix-Nicolai Müller wrote:
¡ElCheVive! schrieb:
Hi,
I dislike the idea of a new web page for install yast modules. Much probably no one will note this and use it, because the users will not know that there are other yast modules than the ones installed by default. Thats the main reason of this new module. ...
Another possibility would be to have a new section in yast-sw-installer which only deals with yast modules. Or to create a new module that only lists not yet installed modules.
In any case, I would keep yast as simple and clean as possible. Introducing (dimmed) icons to the regular sections contradicts the effort that has already been made to make yast slicker. Sadly, this task was only begun for 11.0.
And that's actually the case, I've created *new* YaST Control Center group that lists them, they're not listed in the same groups with the already installed YaST modules.
Stano has (personally) pointed out that we could even change YaST Control Center to use tabs: one for installed modules (the same way it does now) another for not yet installed ones (using the current groups but with dimmed icons).
L.
In this case it's perfect :-) Keep it as it is, no tabs. Greetz Felix -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIvVMBaQ44ga2xxAoRAj5DAJsH+5HBDOWDt8nTzJYSrh6LBj+HQACfZgvm stBiiwC2BYfYTsHBx+H3QpQ= =f+Ax -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Lukas Ocilka:
And that's actually the case, I've created *new* YaST Control Center group that lists them, they're not listed in the same groups with the already installed YaST modules.
The presence or lack of a yast module should reflect what the system install process figured out plus what people wanted on their systems. Zero people should care about a complete list of yast modules. yast modules are media, ok? They "communicate" the system. To explore what opensuse can offer (Birger's need) people need to look at software schemata, package groups, whatever. Wolfgang ps: Why is the httpd module not pulled in when I install apache? --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, on Samstag, 6. September 2008, Wolfgang Woehl wrote:
ps: Why is the httpd module not pulled in when I install apache?
Because the apache package does not have Recommends: yast2-http-server in its specfile. The other way round is also possible: add Supplements: apache2 to the yast2-http-server package. (Open a bugreport and it might be added ;-) This would be useful for every YaST module, so maybe it {c,sh}ould be made a general policy: - "If there is a YaST module for a package, the package should recommend it" - or - - "each YaST module should have a Suplements: for the package it configures" This might even be the better solution because it is easier to check ("each YaST package must have at least one Supplements: statement") I'm cross-posting this mail to the opensuse-packaging mailinglist because packaging policies are better fitted there. Please answer only to the -packaging mailinglist if possible. (Packagers, do you like the above proposal?) Regards, Christian Boltz -- "GNU is not Linux - Linux has a kernel that boots" [Chris Thompson] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Christian Boltz:
on Samstag, 6. September 2008, Wolfgang Woehl wrote:
ps: Why is the httpd module not pulled in when I install apache?
Because the apache package does not have Recommends: yast2-http-server in its specfile.
The other way round is also possible: add Supplements: apache2 to the yast2-http-server package.
Aha, thank you. Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
2008/9/6 Wolfgang Woehl <tito@rumford.de>:
Lukas Ocilka:
And that's actually the case, I've created *new* YaST Control Center group that lists them, they're not listed in the same groups with the already installed YaST modules.
The presence or lack of a yast module should reflect what the system install process figured out plus what people wanted on their systems. Zero people should care about a complete list of yast modules.
yast modules are media, ok? They "communicate" the system.
To explore what opensuse can offer (Birger's need) people need to look at software schemata, package groups, whatever.
Wolfgang
I do not agree with your view. What Lukas has made a prototype of is just what I see newcommers to SuSE administration need. An easy overview of Yast capabilities. Birger --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi, How is the status of this module? regards, Luiz 2008/9/8 Birger Kollstrand <birger.kollstrand@googlemail.com>:
2008/9/6 Wolfgang Woehl <tito@rumford.de>:
Lukas Ocilka:
And that's actually the case, I've created *new* YaST Control Center group that lists them, they're not listed in the same groups with the already installed YaST modules.
The presence or lack of a yast module should reflect what the system install process figured out plus what people wanted on their systems. Zero people should care about a complete list of yast modules.
yast modules are media, ok? They "communicate" the system.
To explore what opensuse can offer (Birger's need) people need to look at software schemata, package groups, whatever.
Wolfgang
I do not agree with your view. What Lukas has made a prototype of is just what I see newcommers to SuSE administration need. An easy overview of Yast capabilities.
Birger --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
¡ElCheVive! wrote:
Hi,
How is the status of this module?
2008/9/8 Birger Kollstrand <birger.kollstrand@googlemail.com>:
2008/9/6 Wolfgang Woehl <tito@rumford.de>: I do not agree with your view. What Lukas has made a prototype of is just what I see newcommers to SuSE administration need. An easy overview of Yast capabilities.
Hi, It's currently living in the build service, waiting for better ideas and/or contributions. It needs some changes in YaST Control Center if we want to use the package how it exists now. Bye Lukas
Birger Kollstrand:
would it be possible/nice etc. to have an extra tab in the Yast Controll Senter section that reads something like "Uninstalled servers and services". In this sectio would all uninstalled yast options be listed.
Wrong idea. You need to tell people to look at "Software", schemata and package groups, in order to explore. Plus upon installing a package yast should pull in the module. Which it doesn't do. (For instance install apache2 and see whether the yast module pops up). Which kind of sucks. Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (10)
-
Birger Kollstrand -
Christian Boltz -
Felix Möller -
Felix-Nicolai Müller -
josef reidinger -
Lars Vogdt -
Lukas Ocilka -
Rajko M. -
Wolfgang Woehl -
¡ElCheVive!