Description of problem:
It' quite easy to launch grub2 from another grub2:
menuentry "F20 Grub" {
    ### just e.g., the /boot on partition case is even simpler
    insmod lvm
    set root=(vg_name-lv_with_fedora)
    ### grub2 may be also built as linux binary
    ### in that case replace "multiboot" with "linux"
    multiboot /boot/grub2/i386-pc/core.img
}
such setup has advantage of more OSs not messing up with each other bootloader but in order to be actually useful, anaconda would have to:
1) install grub physically in /boot
2) not to touch actual boot sector and stage 1.5 space

This bug purpose is to get effectively the same what was achieved in the past by grub installation to partition and chainloading the partition from master grub - but unlike that method, executing grub2 from another grub2 in the way outlined above is clean so anaconda shouldn't have troubles implementing it

The only problem I see is communicating this option in UI so that users who want it can see it. Maybe the options could form somehow a logical tree:
* install bootloader to boot sector of the disk (default)
* do not setup the bootloader
    * install the bootloader to /boot but do not set the computer up to use it
    * do not install bootloader at all
 

Version-Release number of selected component (if applicable):
Fedora 20 beta

How reproducible:
always

Steps to Reproduce:
1. try to install bootloader without stage 1 and 1.5
2.
3.

Actual results:


Expected results:


Additional info: