[yast-devel] Amaranth: Why Ruby
Amaranth: Why Ruby ================== Robert suggested a survey to choose the language, but that would omit the reasoning, the criteria. The implied criterion is: - popularity among current and potential contributors where Ruby wins the SUSE WebYaST people and other SUSE web/Rails developers Let me add other ones I could think of: - existing code base We have YaPI and User in Perl We want to interface with WebYaST in Ruby - the above two combined: libraries and contributors of other distros' yast-like tools Fedora, Ubuntu, Pardus use Python - runtime efficiency it matters for installation RAM requirements I don't have the data. Anyone? So far I found http://eigenclass.org/R2/writings/object-size-ruby-ocaml which basically says that rb 1.8 has bloated @members so use 1.9 or structs. In the end I think that barring a veto by another criterion, the most important one is the availability of developers to make the transition. That results in Ruby, but I may be wrong and maybe there are five of you who will say "Yes! As long as it's Intercal!" Please reply with insights into the criteria already mentioned, your preferences, or other criteria. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
On Wednesday 09 February 2011 15:07:07 Martin Vidner wrote:
Amaranth: Why Ruby ==================
Robert suggested a survey to choose the language, but that would omit the reasoning, the criteria. The implied criterion is:
- popularity among current and potential contributors where Ruby wins the SUSE WebYaST people and other SUSE web/Rails developers
Let me add other ones I could think of:
- existing code base We have YaPI and User in Perl We want to interface with WebYaST in Ruby
- the above two combined: libraries and contributors of other distros' yast-like tools Fedora, Ubuntu, Pardus use Python
- runtime efficiency it matters for installation RAM requirements I don't have the data. Anyone? So far I found http://eigenclass.org/R2/writings/object-size-ruby-ocaml which basically says that rb 1.8 has bloated @members so use 1.9 or structs.
In the end I think that barring a veto by another criterion, the most important one is the availability of developers to make the transition. That results in Ruby, but I may be wrong and maybe there are five of you who will say "Yes! As long as it's Intercal!"
Please reply with insights into the criteria already mentioned, your preferences, or other criteria.
Actually, we should use upstream stuff where appropriate, and here I see Python more common. As long as we want to use e.g. PackageKit as back-end, we need to have Python installed (and occupying memory) anyway. I think that we should look into libraries which will most likely be used and consider whether it is worth it aligning on a single language. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 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
On 02/10/2011 08:51 AM, Jiri Srain wrote:
Python more common. As long as we want to use e.g. PackageKit as back-end, we need to have Python installed (and occupying memory) anyway.
Uh, why? PackageKit does not require python. Our package does because it includes the python client API (dbus wrapper). Duncan -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Thursday 10 February 2011 09:57:15 Duncan Mac-Vicar P. wrote:
On 02/10/2011 08:51 AM, Jiri Srain wrote:
Python more common. As long as we want to use e.g. PackageKit as back-end, we need to have Python installed (and occupying memory) anyway.
Uh, why? PackageKit does not require python. Our package does because it includes the python client API (dbus wrapper).
I just recalled that PackageKit is the reason why Python is dragged in by WebYaST. The main purpose of that comment was that we should be aware whether we drag in Python code (which we have to co-maintain with the community then). For installation, we are also limited by memory. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 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
* Jiri Srain <jsrain@suse.cz> [Feb 10. 2011 10:33]:
On Thursday 10 February 2011 09:57:15 Duncan Mac-Vicar P. wrote:
On 02/10/2011 08:51 AM, Jiri Srain wrote:
Python more common. As long as we want to use e.g. PackageKit as back-end, we need to have Python installed (and occupying memory) anyway.
Uh, why? PackageKit does not require python. Our package does because it includes the python client API (dbus wrapper).
I just recalled that PackageKit is the reason why Python is dragged in by WebYaST.
The main purpose of that comment was that we should be aware whether we drag in Python code (which we have to co-maintain with the community then). For installation, we are also limited by memory.
Regarding memory usage, I found this: http://hentenaar.com/serendipity/index.php?/archives/27-Benchmark-PHP-vs.-Py... In these tests, Ruby consumed 30% less memory than Python. Regarding disk space / package size, its ~20MB for Python and ~6MB for Ruby. Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Thursday 10 February 2011 13:23:24 Klaus Kaempf wrote:
* Jiri Srain <jsrain@suse.cz> [Feb 10. 2011 10:33]:
On Thursday 10 February 2011 09:57:15 Duncan Mac-Vicar P. wrote:
On 02/10/2011 08:51 AM, Jiri Srain wrote:
Python more common. As long as we want to use e.g. PackageKit as back-end, we need to have Python installed (and occupying memory) anyway.
Uh, why? PackageKit does not require python. Our package does because it includes the python client API (dbus wrapper).
I just recalled that PackageKit is the reason why Python is dragged in by WebYaST.
The main purpose of that comment was that we should be aware whether we drag in Python code (which we have to co-maintain with the community then). For installation, we are also limited by memory.
Regarding memory usage, I found this:
http://hentenaar.com/serendipity/index.php?/archives/27-Benchmark-PHP-vs.-P ython-vs.-Perl-vs.-Ruby.html
In these tests, Ruby consumed 30% less memory than Python.
Regarding disk space / package size, its ~20MB for Python and ~6MB for Ruby.
That's nothing I disagree with. What I say is that Python + Ruby > Python Python + Ruby > Ruby I'm advocating against resulting in a mixed environment. Jiri -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain@suse.cz Lihovarska 1060/12 tel: +420 284 084 659 190 00 Praha 9 fax: +420 284 084 001 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
On Thu, Feb 10, 2011 at 01:23:24PM +0100, Klaus Kaempf wrote:
* Jiri Srain <jsrain@suse.cz> [Feb 10. 2011 10:33]:
The main purpose of that comment was that we should be aware whether we drag in Python code (which we have to co-maintain with the community then). For installation, we are also limited by memory.
Regarding memory usage, I found this:
http://hentenaar.com/serendipity/index.php?/archives/27-Benchmark-PHP-vs.-Py...
In these tests, Ruby consumed 30% less memory than Python.
Yes... on this "benchmark": Two test programs were measured: Hello - Prints "Hello World" to stdout. Inc - Increments a variable, starting at 0. Each program does one-million iterations, and is run ten consecutive times. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
* Martin Vidner <mvidner@suse.cz> [Feb 10. 2011 14:03]:
On Thu, Feb 10, 2011 at 01:23:24PM +0100, Klaus Kaempf wrote:
* Jiri Srain <jsrain@suse.cz> [Feb 10. 2011 10:33]:
The main purpose of that comment was that we should be aware whether we drag in Python code (which we have to co-maintain with the community then). For installation, we are also limited by memory.
Regarding memory usage, I found this:
http://hentenaar.com/serendipity/index.php?/archives/27-Benchmark-PHP-vs.-Py...
In these tests, Ruby consumed 30% less memory than Python.
Yes... on this "benchmark":
Two test programs were measured: Hello - Prints "Hello World" to stdout. Inc - Increments a variable, starting at 0. Each program does one-million iterations, and is run ten consecutive times.
Well, that was the only 'benchmark' Google gave me ;-) Klaus --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 02/10/2011 10:33 AM, Jiri Srain wrote:
On Thursday 10 February 2011 09:57:15 Duncan Mac-Vicar P. wrote:
On 02/10/2011 08:51 AM, Jiri Srain wrote:
Python more common. As long as we want to use e.g. PackageKit as back-end, we need to have Python installed (and occupying memory) anyway.
Uh, why? PackageKit does not require python. Our package does because it includes the python client API (dbus wrapper).
I just recalled that PackageKit is the reason why Python is dragged in by WebYaST.
Packaging bug. python-packagekit should be splitted out. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hello, On Feb 9 15:07 Martin Vidner wrote (excerpt):
Amaranth: Why Ruby ... - popularity among current and potential contributors where Ruby wins the SUSE WebYaST people and other SUSE web/Rails developers
What about popularity among other Linux distributors? What do they use for their setup tools? If they use already a common language, they might already have an ecosystem of re-usable code and contributors. If their code is free software, we could use it as well. In particular basic software modules (without UI) which actually do something in the system (e.g. read and write system settings). I assume the UI would have to be separated because this is where Linux distributors like to be different. I do not know if the other Linux distributors have already their UI software separated from their basic software which changes the system. Perhaps it is possible to have the UI stuff well separated from the basic software modules which change the system? Then it would be possible to have at least the basic software which actually changes the system (at least almost) the same for all Linux distributors so that all potential contributors could help here easily regardless which Linux distribution each individual contributor uses. On the other hand the UI stuff which probably every Linux distributor likes to do on his own way could be implemented in whatever way (in particular in whatever language) each Linux distributor likes most. In short: What about something like Python (or whatever the other Linux distributors use) for the basic software which changes the system and Ruby (or whatever we like most) for our own YaST UI? Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Am 09.02.2011 15:07, schrieb Martin Vidner:
Amaranth: Why Ruby ==================
- popularity among current and potential contributors where Ruby wins the SUSE WebYaST people and other SUSE web/Rails developers
This is a strong argument for me - I vote for Ruby. It's also much easier to switch between teams if the same language is used. -- Gabriele Mohr SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Maxfeldstr. 5 Tel: +49 911 740 53 362 90409 Nürnberg Email: gs@suse.de ----------------------------------------------------------------- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 02/10/2011 06:42 AM, Gabriele Mohr wrote:
Am 09.02.2011 15:07, schrieb Martin Vidner:
Amaranth: Why Ruby ==================
- popularity among current and potential contributors where Ruby wins the SUSE WebYaST people and other SUSE web/Rails developers
This is a strong argument for me - I vote for Ruby. It's also much easier to switch between teams if the same language is used.
But it also constrains the implementation to the 4 walls of SUSE. As was pointed out on this thread other distributions predominantly use Python for system configuration tasks. Yes there are unanswered questions about separation of UI code from code that actually fiddles the settings in the config files, i.e. MVC paradigm adherence. But it might be easier to get involved in the existing projects and drive UI separation, if necessary, than to start from scratch with Yet another Setup Tool language (pun intended ;) ). Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU Novell-IBM Software Integration Center LINUX Tech Lead rschweikert@novell.com rschweikert@ca.ibm.com 781-464-8147 Novell Making IT Work As One -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dne 10.2.2011 16:02, Robert Schweikert napsal(a):
On 02/10/2011 06:42 AM, Gabriele Mohr wrote:
Am 09.02.2011 15:07, schrieb Martin Vidner:
Amaranth: Why Ruby ==================
- popularity among current and potential contributors where Ruby wins the SUSE WebYaST people and other SUSE web/Rails developers
This is a strong argument for me - I vote for Ruby. It's also much easier to switch between teams if the same language is used.
But it also constrains the implementation to the 4 walls of SUSE. As was pointed out on this thread other distributions predominantly use Python for system configuration tasks.
Yes there are unanswered questions about separation of UI code from code that actually fiddles the settings in the config files, i.e. MVC paradigm adherence. But it might be easier to get involved in the existing projects and drive UI separation, if necessary, than to start from scratch with Yet another Setup Tool language (pun intended ;) ).
One "yes" for Ruby and "no" for Python is the level of expertise we have here in SUSE. It took us several months maybe even years to learn Ruby, how long does it take to learn Python or any other language? I mean "learn" in a level that developers do not only need to consult every line of code with documentation but even can think in the level of abstraction that the language provides. I don't say: Let's use Ruby. What I say is that learning something new takes time. Sometimes a lot of time. Do we have enough time? Bye Lukas - -- Lukas Ocilka, Appliances Department, Novell Inc. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFNVAM2VSqMdRCqTiwRAoLDAJ9AHW8S0qlulZNMlWGnqILCOwPzjQCdF92q az1kR+OtuvXgDwvJBXIdfQ8= =Hsbj -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Feb 10, 2011, at 8:24 AM, Lukas Ocilka wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dne 10.2.2011 16:02, Robert Schweikert napsal(a):
On 02/10/2011 06:42 AM, Gabriele Mohr wrote:
Am 09.02.2011 15:07, schrieb Martin Vidner:
Amaranth: Why Ruby ==================
- popularity among current and potential contributors where Ruby wins the SUSE WebYaST people and other SUSE web/Rails developers
This is a strong argument for me - I vote for Ruby. It's also much easier to switch between teams if the same language is used.
But it also constrains the implementation to the 4 walls of SUSE. As was pointed out on this thread other distributions predominantly use Python for system configuration tasks.
Yes there are unanswered questions about separation of UI code from code that actually fiddles the settings in the config files, i.e. MVC paradigm adherence. But it might be easier to get involved in the existing projects and drive UI separation, if necessary, than to start from scratch with Yet another Setup Tool language (pun intended ;) ).
One "yes" for Ruby and "no" for Python is the level of expertise we have here in SUSE.
It took us several months maybe even years to learn Ruby, how long does it take to learn Python or any other language? I mean "learn" in a level that developers do not only need to consult every line of code with documentation but even can think in the level of abstraction that the language provides.
I don't say: Let's use Ruby. What I say is that learning something new takes time. Sometimes a lot of time. Do we have enough time?
Do you have enough time to start from scratch, go it on your own, and ignore the efforts of other distros? I would give such things as "What do other distros use for such things?" and "Which language lets us re-use more existing code/projects?" more weight than "What do we know in-house?" in the decision process. I'm sure a bunch of Ruby coders can pick up Python easy enough, but starting from scratch vs. leveraging as much as possible from existing external efforts isn't the way to ensure the long-term success of the project. -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 02/10/2011 04:40 PM, Bart Whiteley wrote:
Do you have enough time to start from scratch, go it on your own, and ignore the efforts of other distros?
Again, distro"S" here is Fedora and Pardus. And from Fedora, stuff you can reuse in python is Anaconda, System Tools and yum. For all the rest you have libsomething in C which you can reuse anyways. -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dne 10.2.2011 16:40, Bart Whiteley napsal(a):
On Feb 10, 2011, at 8:24 AM, Lukas Ocilka wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Dne 10.2.2011 16:02, Robert Schweikert napsal(a):
On 02/10/2011 06:42 AM, Gabriele Mohr wrote:
Am 09.02.2011 15:07, schrieb Martin Vidner:
Amaranth: Why Ruby ==================
... shortened ...
I don't say: Let's use Ruby. What I say is that learning something new takes time. Sometimes a lot of time. Do we have enough time?
Do you have enough time to start from scratch, go it on your own, and ignore the efforts of other distros?
I didn't say that we need to start everything from scratch. We even can't.
I would give such things as "What do other distros use for such things?" and "Which language lets us re-use more existing code/projects?" more weight than "What do we know in-house?" in the decision process.
Yes, you're right, these are *also* absolutely valid questions and pieces of information to be taken into consideration. Maybe we should try to explore how the "other" distributions do it and whether we like that or not.
I'm sure a bunch of Ruby coders can pick up Python easy enough, but starting from scratch vs. leveraging as much as possible from existing external efforts isn't the way to ensure the long-term success of the project.
IMO another approach would be to try both languages and, let's say, after 2 or 4 weeks..., reevaluate what we've done and how it worked. Bye Lukas - -- Lukas Ocilka, Appliances Department, Novell Inc. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFNVPtLVSqMdRCqTiwRAk03AJ0Q7wlKKsgitQXfRMwhWkjFlnKdbQCeJ27W 30qzD2OkSxonCK4F0FohGi4= =GDrM -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Thursday, February 10, 2011 04:24:39 pm Lukas Ocilka wrote:
Dne 10.2.2011 16:02, Robert Schweikert napsal(a):
On 02/10/2011 06:42 AM, Gabriele Mohr wrote:
Am 09.02.2011 15:07, schrieb Martin Vidner:
Amaranth: Why Ruby ==================
- popularity among current and potential contributors where Ruby wins the SUSE WebYaST people and other SUSE web/Rails developers
This is a strong argument for me - I vote for Ruby. It's also much easier to switch between teams if the same language is used.
But it also constrains the implementation to the 4 walls of SUSE. As was pointed out on this thread other distributions predominantly use Python for system configuration tasks.
Yes there are unanswered questions about separation of UI code from code that actually fiddles the settings in the config files, i.e. MVC paradigm adherence. But it might be easier to get involved in the existing projects and drive UI separation, if necessary, than to start from scratch with Yet another Setup Tool language (pun intended ;) ).
One "yes" for Ruby and "no" for Python is the level of expertise we have here in SUSE.
It took us several months maybe even years to learn Ruby, how long does it take to learn Python or any other language? I mean "learn" in a level that developers do not only need to consult every line of code with documentation but even can think in the level of abstraction that the language provides.
I don't say: Let's use Ruby. What I say is that learning something new takes time. Sometimes a lot of time. Do we have enough time?
A couple of months ago we had enough time to learn ruby instead of sticking to YCP. :-)
Bye Lukas
-- Thomas Goettlicher SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hello, On Feb 10 16:24 Lukas Ocilka wrote (excerpt):
... we ... ... here in SUSE ... ... us ... ... Do we ...
I think this is the wrong point of view. I think it should be more "they" and "them". Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 02/10/2011 05:43 PM, Johannes Meixner wrote:
Hello,
On Feb 10 16:24 Lukas Ocilka wrote (excerpt):
... we ... ... here in SUSE ... ... us ... ... Do we ...
I think this is the wrong point of view.
I think it should be more "they" and "them".
Sure, but instead of vague statements like "the distros use python", we need to know which distro and what is written there exactly in python, because from what I have seen, this is only true for Fedora: installer, yum, system tools Pardus: same For all the rest, is a mix of Bash, perl, C, etc... -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Feb 10, 2011, at 9:49 AM, Duncan Mac-Vicar P. wrote:
On 02/10/2011 05:43 PM, Johannes Meixner wrote:
Hello,
On Feb 10 16:24 Lukas Ocilka wrote (excerpt):
... we ... ... here in SUSE ... ... us ... ... Do we ...
I think this is the wrong point of view.
I think it should be more "they" and "them".
Sure, but instead of vague statements like "the distros use python", we need to know which distro and what is written there exactly in python, because from what I have seen, this is only true for
Fedora: installer, yum, system tools Pardus: same
For all the rest, is a mix of Bash, perl, C, etc...
Which distros use ruby? -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 02/10/2011 11:49 AM, Duncan Mac-Vicar P. wrote:
On 02/10/2011 05:43 PM, Johannes Meixner wrote:
Hello,
On Feb 10 16:24 Lukas Ocilka wrote (excerpt):
... we ... ... here in SUSE ... ... us ... ... Do we ...
I think this is the wrong point of view.
I think it should be more "they" and "them".
Sure, but instead of vague statements like "the distros use python", we need to know which distro and what is written there exactly in python,
Agreed about the being more specific part, and the distros and their specific implementation was stated specifically in this thread earlier, although I cannot put my finger on it right this second.
because from what I have seen, this is only true for
Fedora: installer, yum, system tools Pardus: same
For all the rest, is a mix of Bash, perl, C, etc...
-- Robert Schweikert MAY THE SOURCE BE WITH YOU Novell-IBM Software Integration Center LINUX Tech Lead rschweikert@novell.com rschweikert@ca.ibm.com 781-464-8147 Novell Making IT Work As One -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Hello, On Feb 10 17:49 Duncan Mac-Vicar P. wrote (excerpt):
On 02/10/2011 05:43 PM, Johannes Meixner wrote:
I think it should be more "they" and "them".
Sure, but instead of vague statements like "the distros use python", we need to know which distro and what is written there exactly in python
I did not mean the programming language. I mean that the target audience for a "new YaST" should be more the people "out there". Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 02/10/2011 04:02 PM, Robert Schweikert wrote:
But it also constrains the implementation to the 4 walls of SUSE. As was pointed out on this thread other distributions predominantly use Python for system configuration tasks.
Others being Fedora and Pardus? Debian uses mix of C/Perl Gentoo uses python for portage, but there are alternative implementations in C++ Archlinux uses C/Bash .... -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On Wed, Feb 09, 2011 at 03:07:07PM +0100, Martin Vidner wrote:
- the above two combined: libraries and contributors of other distros' yast-like tools Fedora, Ubuntu, Pardus use Python
Correction: Ubuntu uses Perl based system-tools-backends: http://system-tools-backends.freedesktop.org/ http://cgit.freedesktop.org/system-tools-backends/tree/ -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
participants (10)
-
Bart Whiteley -
Duncan Mac-Vicar P. -
Gabriele Mohr -
Jiri Srain -
Johannes Meixner -
Klaus Kaempf -
Lukas Ocilka -
Martin Vidner -
Robert Schweikert -
Thomas Goettlicher