Mailinglist Archive: yast-devel (79 mails)

< Previous Next >
Re: [yast-devel] Rspec as specification
On Wed, 2 Mar 2016 11:06:57 +0100
Arvin Schnell <aschnell@xxxxxxxx> wrote:

On Tue, Mar 01, 2016 at 05:16:49PM +0100, Martin Vidner wrote:
On Tue, Mar 01, 2016 at 04:53:41PM +0100, Josef Reidinger wrote:
Hi,
as there is in last days some discussion how rspec can be used as
specification or not and I would like to document how bootloader
do its proposal, so I take it as oppurinity to write it in RSpec.

Output for better formatting is placed to pastebin
http://pastebin.com/raw/8YhuWwVi

Please ignore for now typos. I am more interested if it is
readable for you as specification how bootloader is proposed.

Yes, it is a good summary of the requirements!

No, these do not look like requirements but as *one*
solution. Requirements should include the motivation.

Yes, it is not requirements, it is specification how it works.
Requirements and explanation why something is done in given way is
captured in comments in code. Specification only say what it do, not
why.


Besides of that, the text does not even mention that it has to do
with the "bootloader"; wide context is just missing. And what is
"os_prober"?

It is snippet for propose method. Of course it also have at beginning
something like Bootloader::Grub2Base ( as it is generic grub2 proposal,
not stage1 or EFI specific one which have more specification ).

What wide context you expect?

os_prober is one of grub2 configuration options which it propose. it is
easily googable term like "grub2 os_prober" or even single "os_prober"
term. I worry if I have to explain all configuration option for grub2
it will easily be too crowded and easy to lost point.


Regards,
Arvin


Thanks for feedback,
Josef
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >