[yast-devel] DnsServerAPI.pm
Hi! Because of dependencies I moved $SUBJ from yast2-dns-server into yast2 package. This was because of bnc#392606 (yast-http-server dependency), but if any other packages are affected, please fix them. All changes are in svn trunk, packages are not in autobuild yet. Bye, Michal -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Michal Zugec wrote:
Hi! Because of dependencies I moved $SUBJ from yast2-dns-server into yast2 package. This was because of bnc#392606 (yast-http-server dependency), but if any other packages are affected, please fix them. All changes are in svn trunk, packages are not in autobuild yet.
I've removed your changes in VERSION files in trunk (openSUSE 11.1). Version line 2.16.X must be kept for openSUSE 11.0 maintenance as we can't have two different packages with the same version. The next version of package yast2 in trunk will be 2.17.0. That version should also contain: --- cut --- Provides: yast2-dns-server:/usr/share/YaST2/modules/DnsServerAPI.pm --- cut --- (not done yet) The next version of yast2-dns-server will be 2.17.0 too (not done yet). Other packages requiring DnsServerAPI should require yast2 >= 2.17.0 (not done yet). Package yast2 should conflict with yast2-dns-server <= 2.17.0 (not done yet). Please, make sure that your changes are consistent and that all the dependencies are correct. Thanks && Bye Lukas
Hi! Dne Tuesday 10 of June 2008 09:44:17 Michal Zugec napsal(a):
Hi! Because of dependencies I moved $SUBJ from yast2-dns-server into yast2 package. This was because of bnc#392606 (yast-http-server dependency), but if any other packages are affected, please fix them. All changes are in svn trunk, packages are not in autobuild yet.
Is this really the best way to go? This way we polute the yast2.rpm package with code which does not work without another package (yast2-dns-server) at all. With this code in, yast2.rpm should IMHO recommend the yast2-dns-server package, which does not conform with it being understoon as "base libraries". I personally find the dependency of yast2-apache on yast2-dns-server acceptable, as the price for integration of YaST modules. -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz
Jiri Srain wrote:
Hi!
Dne Tuesday 10 of June 2008 09:44:17 Michal Zugec napsal(a):
Hi! Because of dependencies I moved $SUBJ from yast2-dns-server into yast2 package. This was because of bnc#392606 (yast-http-server dependency), but if any other packages are affected, please fix them. All changes are in svn trunk, packages are not in autobuild yet.
Is this really the best way to go? This way we polute the yast2.rpm package with code which does not work without another package (yast2-dns-server) at all. With this code in, yast2.rpm should IMHO recommend the yast2-dns-server package, which does not conform with it being understoon as "base libraries".
I personally find the dependency of yast2-apache on yast2-dns-server acceptable, as the price for integration of YaST modules.
yast2-apache does not use the yast2-dns-server client, it uses the APIs. See my other mail. Our current way of packaging is insane. When someone try to generate an appliance for a simple server out of it, you will pull lot of unrelated packages. We need to define a way to package the "platform", reusable stuff. Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Michal Zugec wrote:
Hi! Because of dependencies I moved $SUBJ from yast2-dns-server into yast2 package. This was because of bnc#392606 (yast-http-server dependency), but if any other packages are affected, please fix them. All changes are in svn trunk, packages are not in autobuild yet.
Bye, Micha This open against the topic of, why having yast2 as a wildcard for everything needed in two places?
YaST already has the difference between modules and clients, why no package modules supposed to be used by other clients to in a separate package? With the current solution, and the current workaround you just made yast2-dns to depend on libzypp. yast2-modules-network yast2-modules-dns yast2-modules-packagemgmt yast2-modules-desktop .... Otherwise the stuff is just not reusable. Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Duncan Mac-Vicar Prett wrote:
Michal Zugec wrote:
Hi! Because of dependencies I moved $SUBJ from yast2-dns-server into yast2 package. This was because of bnc#392606 (yast-http-server dependency), but if any other packages are affected, please fix them. All changes are in svn trunk, packages are not in autobuild yet.
Bye, Micha This open against the topic of, why having yast2 as a wildcard for everything needed in two places?
YaST already has the difference between modules and clients, why no package modules supposed to be used by other clients to in a separate package?
With the current solution, and the current workaround you just made yast2-dns to depend on libzypp.
yast2-modules-network yast2-modules-dns yast2-modules-packagemgmt yast2-modules-desktop ....
Otherwise the stuff is just not reusable.
The current DneServerAPI module works without yast2-dns-server being installed. First time it is used, it reports (into log) that the package is not installed and that the dns-related functions will not work. It's the similar to the module SLPAPI.pm It also only provides the API layer, nothing more. L.
Lukas Ocilka wrote:
The current DneServerAPI module works without yast2-dns-server being installed. First time it is used, it reports (into log) that the package is not installed and that the dns-related functions will not work.
It's the similar to the module SLPAPI.pm
It also only provides the API layer, nothing more.
L.
I know. My question, is, why a package wanting to use that module, should end depending in libzypp and a ton of other packages. Those reusable modules should be in their own package with their related APIs. Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Duncan Mac-Vicar Prett wrote:
Lukas Ocilka wrote:
The current DneServerAPI module works without yast2-dns-server being installed. First time it is used, it reports (into log) that the package is not installed and that the dns-related functions will not work.
It's the similar to the module SLPAPI.pm
It also only provides the API layer, nothing more.
L.
I know.
My question, is, why a package wanting to use that module, should end depending in libzypp and a ton of other packages.
Those reusable modules should be in their own package with their related APIs.
The problem is that some users keep complaining that yast2-http-server requires yast2-dns-server even if they don't want to use the DNS Server on their machine. Another users are pretty satisfied with the yast2-http-server <-> yast2-dns-server connection. The problem is actually in the fact that the functionality is optional. Some will use it, some will not. Why Miso moved DnsServerAPI to yast2 :)? Well, because he basically didn't want to write another Perl wrapper around another Perl wrapper (DnsServerAPI is mainly a Perl wrapper around DnsServer YCP Module) ;) ... and this was just cheaper ;) Another solution would be to move that library to yast2-dns-server-API package. Would it help? Do we want a package with one relatively small library (plus docu?). L.
Lukas Ocilka wrote:
Another solution would be to move that library to yast2-dns-server-API package. Would it help? Do we want a package with one relatively small library (plus docu?).
L.
ugh, yes, that is what I proposed above. Instead of yast2-http -> yast2-dns-server or yast2-http -> yast2-dns-server -> yast2 -> libzypp and more yast2-http -> yast2-dns-server -> yast2-modules-dns (or yast2-components-dns or whatever...) The tricky part is not the size and the amount of libraries, but grouping these APIs correctly. For that, looking the dependency graph and the functional areas would be useful. Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Dňa Tuesday 10 June 2008 14:55:14 Duncan Mac-Vicar Prett ste napísal:
Lukas Ocilka wrote:
Another solution would be to move that library to yast2-dns-server-API package. Would it help? Do we want a package with one relatively small library (plus docu?).
L.
ugh, yes, that is what I proposed above.
Instead of
yast2-http -> yast2-dns-server
or yast2-http -> yast2-dns-server -> yast2 -> libzypp and more
yast2-http -> yast2-dns-server -> yast2-modules-dns
yast2-api-dns? Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Stanislav Visnovsky wrote:
Dňa Tuesday 10 June 2008 14:55:14 Duncan Mac-Vicar Prett ste napísal:
Lukas Ocilka wrote:
Another solution would be to move that library to yast2-dns-server-API package. Would it help? Do we want a package with one relatively small library (plus docu?).
L. ugh, yes, that is what I proposed above.
Instead of
yast2-http -> yast2-dns-server
or yast2-http -> yast2-dns-server -> yast2 -> libzypp and more
yast2-http -> yast2-dns-server -> yast2-modules-dns
yast2-api-dns?
I'd rather use $package-api for building and .spec file purpose. ~~~> Recommends ---> Requires yast2-dns-server-api ~~~> yast2-dns-server yast2-http-server ---> yast2-dns-server-api yast2-dhcp-server ---> yast2-dns-server-api yast2-slp-api ~~~> yast2-slp yast2-ntp-client ---> yast2-slp-api Finally, the system will end up with yast2-dns-server (plus deps.) installed but one can remove it as it is only recommended :) Any comments? Thx && Bye L.
On st 11. června 2008, Lukas Ocilka wrote:
Stanislav Visnovsky wrote:
yast2-api-dns?
I'd rather use $package-api for building and .spec file purpose.
I agree, it goes the same line as $package-devel-doc (e.g. yast2-nis-server-devel-doc) j -- Jiri Suchomel SUSE LINUX, s.r.o. e-mail: jsuchome@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Praha 9, Czech Republic http://www.suse.cz -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Jiří Suchomel wrote:
On st 11. června 2008, Lukas Ocilka wrote:
Stanislav Visnovsky wrote:
yast2-api-dns?
I'd rather use $package-api for building and .spec file purpose.
I agree, it goes the same line as $package-devel-doc (e.g. yast2-nis-server-devel-doc)
j
That is because -doc is part of the package. My proposal was to make the modules with functionality a separate package grouped by areas of management, and not just a split of the package, which will just create a 1:1 between APIs (modules) and UIs (clients). This is not about splitting packages, but about giving some logic to our platform. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Tue, Jun 10, 2008 at 01:21:22PM +0200, Lukas Ocilka wrote:
The current DnsServerAPI module works without yast2-dns-server being installed. First time it is used, it reports (into log) that the package is not installed and that the dns-related functions will not work.
I like that approach: Reduce the functionallity if something is not installed. Of course this must be a understandable omission, e.g. you cannot open a firewall port in nfs-server configuration if the firewall module is not installed. I must admit I looked at the code and didn't understand how the wrapper works. But wouldn't it be useful if the language supports this? E.g. in Python the import statement is just a normal function and can be put in a try block: try: import "firewall" except ImportError: popup "reduced functionallity..." log "firewall module missing" show_open_port_button = False ciao Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Tue, Jun 10, 2008 at 01:12:28PM +0200, Duncan Mac-Vicar Prett wrote:
This open against the topic of, why having yast2 as a wildcard for everything needed in two places?
YaST already has the difference between modules and clients, why no package modules supposed to be used by other clients to in a separate package?
With the current solution, and the current workaround you just made yast2-dns to depend on libzypp.
yast2-modules-network yast2-modules-dns yast2-modules-packagemgmt yast2-modules-desktop ....
We had that years ago and ended up with 200+ packages. Now we would likely end up with 400+. And users did complain about that: For them it was not visible what all the packages were good for. You can still see remains of that era in the spec files, e.g.: Provides: yast2-lib-sequencer Provides: yast2-agent-fdisk yast2-agent-fdisk-devel Provides: yast2-config-environment Provides: yast2-ui-qt ciao Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Arvin Schnell wrote:
We had that years ago and ended up with 200+ packages. Now we would likely end up with 400+. And users did complain about that: For them it was not visible what all the packages were good for.
And we were told that the autobuild was overloaded with too many packages. So we merged agent + data + clients into one package. -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (8)
-
Arvin Schnell -
Duncan Mac-Vicar Prett -
Jiri Srain -
Jiří Suchomel -
Ladislav Slezak -
Lukas Ocilka -
Michal Zugec -
Stanislav Visnovsky