Ehm, it already can?
/etc/revisor/revisor.conf is the file.

There is also documentation available, both on trac and in the rpm package.

It usually helps to run the command in a terminal (whether you use the --cli or not), because then you would probably have tried revisor.py --help :)

Also not a defect :)

Ehm, it already can?
/etc/revisor/revisor.conf is the file.

There is also documentation available, both on trac and in the rpm package.

It usually helps to run the command in a terminal (whether you use the --cli or not), because then you would probably have tried revisor.py --help :)

Also not a defect :)

Baard,

I did not see any option that allowed me to save the options I had selected in the GUI. Did I miss it ?

Baard,

I did not see any option that allowed me to save the options I had selected in the GUI. Did I miss it ?

'''--kickstart-save''' ''/path/to/ks'' will do a decent amount of saving the options that are kickstart related, e.g. root password, timezone, etc.

Other then that, all configuration is based on models which preserves reproducibility; create a model to your liking in /etc/revisor/revisor.conf, supply a (modified?) "main" configuration file (actually a YUM configuration file such as the others in /etc/revisor/conf.d/), and off you go.

Creating a kickstart is also very easy, with help of the existing kickstarts (/usr/share/livecd-tools/), the kickstarts that are going to be in F-10 (http://git.fedorahosted.org/?p=spin-kickstarts.git) and some of the lousy samples in /etc/revisor/conf.d (which mostly apply to installation media), not to mention system-config-kickstart [--generate]

'''--kickstart-save''' ''/path/to/ks'' will do a decent amount of saving the options that are kickstart related, e.g. root password, timezone, etc.

Other then that, all configuration is based on models which preserves reproducibility; create a model to your liking in /etc/revisor/revisor.conf, supply a (modified?) "main" configuration file (actually a YUM configuration file such as the others in /etc/revisor/conf.d/), and off you go.

Creating a kickstart is also very easy, with help of the existing kickstarts (/usr/share/livecd-tools/), the kickstarts that are going to be in F-10 (http://git.fedorahosted.org/?p=spin-kickstarts.git) and some of the lousy samples in /etc/revisor/conf.d (which mostly apply to installation media), not to mention system-config-kickstart [--generate]

I'll reopen one last time, if you still think my feature request does not make sense feel free to close it and I'll find some other tool to make livecd's :)

Consider this:
- I can already use kickstart-configurator and livecd-tools - why use revisor ? Because it presents a GUI way of doing the same thing, hopefully being more user-friendly. So, are you achieving that goal if a very logical question like "I want to save the config I just made from the GUI" has an answer that says "we're not doing this in the GUI because you can do it from the command line" ? If I'd be ok with the command line I wouldn't be using the GUI to begin with.
- With the high number of bugs I'm running into (I filed 17 or so), causing me to have to restart, the need for this feature should be even more obvious. Seriously - I entered the same set of options 17 times (!!!!) over and over and over again - including being forced to choose a root password, and revisor making sure there was no way I would be able to get the password the same twice, because it eats my first character - so if revisor makes it that common a task to have to go through all the settings, don't you think a save button is the least it should offer ?

Don't take this the wrong way, I'm not angry about this ticket - I am just truly surprised that you make revisor to be a GUI and avoid the command line, and then you go tell me to use the command line to get my config saved. It's as if you're telling me "Don't use revisor", so who do you want to be using revisor then ?

I'll reopen one last time, if you still think my feature request does not make sense feel free to close it and I'll find some other tool to make livecd's :)

Consider this:
- I can already use kickstart-configurator and livecd-tools - why use revisor ? Because it presents a GUI way of doing the same thing, hopefully being more user-friendly. So, are you achieving that goal if a very logical question like "I want to save the config I just made from the GUI" has an answer that says "we're not doing this in the GUI because you can do it from the command line" ? If I'd be ok with the command line I wouldn't be using the GUI to begin with.
- With the high number of bugs I'm running into (I filed 17 or so), causing me to have to restart, the need for this feature should be even more obvious. Seriously - I entered the same set of options 17 times (!!!!) over and over and over again - including being forced to choose a root password, and revisor making sure there was no way I would be able to get the password the same twice, because it eats my first character - so if revisor makes it that common a task to have to go through all the settings, don't you think a save button is the least it should offer ?

Don't take this the wrong way, I'm not angry about this ticket - I am just truly surprised that you make revisor to be a GUI and avoid the command line, and then you go tell me to use the command line to get my config saved. It's as if you're telling me "Don't use revisor", so who do you want to be using revisor then ?

Replying to [comment:4 thomasvs]:

• I can already use kickstart-configurator and livecd-tools - why use revisor ? Because it presents a GUI way of doing the same thing, hopefully being more user-friendly. So, are you achieving that goal if a very logical question like "I want to save the config I just made from the GUI" has an answer that says "we're not doing this in the GUI because you can do it from the command line" ? If I'd be ok with the command line I wouldn't be using the GUI to begin with.

I hear you, and I'm not objecting to anything you request. I just don't see how I can get it done, as there's multiple configuration files used (kickstart, revisor.conf, model specific yum configuration), as well as arbitrary trees you can supply (check copy_dir). I'll leave the ticket open for your suggestions on this.

• With the high number of bugs I'm running into (I filed 17 or so), causing me to have to restart, the need for this feature should be even more obvious. Seriously - I entered the same set of options 17 times (!!!!) over and over and over again - including being forced to choose a root password, and revisor making sure there was no way I would be able to get the password the same twice, because it eats my first character - so if revisor makes it that common a task to have to go through all the settings, don't you think a save button is the least it should offer ?

Say if we save automagically to the directory in which the product ends up; what would we do about the absolute paths (such as "main" in the model configuration)? Should we dump all settings or just the ones you've changed? How do we make sure this configuration is still available if supplied for a second run -remember revisor cleans out the destination directory before it goes to work (e.g. reads the kickstart file)? How do you suggest we load this configuration?

Don't take this the wrong way, I'm not angry about this ticket - I am just truly surprised that you make revisor to be a GUI and avoid the command line, and then you go tell me to use the command line to get my config saved. It's as if you're telling me "Don't use revisor", so who do you want to be using revisor then ?

Seriously, the power of Revisor is in the command-line. It enables use-cases a 1001 administrators have (had) a 1001 separate scripts for. The GUI though still is one of Revisor's main features. For anything more advanced then what is in the GUI already, I'm gonna need help in both designing the GUI program/dialog flow as well as enabling the disabled advanced button just to not obfuscate the dialogs.

Replying to [comment:4 thomasvs]:

• I can already use kickstart-configurator and livecd-tools - why use revisor ? Because it presents a GUI way of doing the same thing, hopefully being more user-friendly. So, are you achieving that goal if a very logical question like "I want to save the config I just made from the GUI" has an answer that says "we're not doing this in the GUI because you can do it from the command line" ? If I'd be ok with the command line I wouldn't be using the GUI to begin with.

I hear you, and I'm not objecting to anything you request. I just don't see how I can get it done, as there's multiple configuration files used (kickstart, revisor.conf, model specific yum configuration), as well as arbitrary trees you can supply (check copy_dir). I'll leave the ticket open for your suggestions on this.

• With the high number of bugs I'm running into (I filed 17 or so), causing me to have to restart, the need for this feature should be even more obvious. Seriously - I entered the same set of options 17 times (!!!!) over and over and over again - including being forced to choose a root password, and revisor making sure there was no way I would be able to get the password the same twice, because it eats my first character - so if revisor makes it that common a task to have to go through all the settings, don't you think a save button is the least it should offer ?

Say if we save automagically to the directory in which the product ends up; what would we do about the absolute paths (such as "main" in the model configuration)? Should we dump all settings or just the ones you've changed? How do we make sure this configuration is still available if supplied for a second run -remember revisor cleans out the destination directory before it goes to work (e.g. reads the kickstart file)? How do you suggest we load this configuration?

Don't take this the wrong way, I'm not angry about this ticket - I am just truly surprised that you make revisor to be a GUI and avoid the command line, and then you go tell me to use the command line to get my config saved. It's as if you're telling me "Don't use revisor", so who do you want to be using revisor then ?

Seriously, the power of Revisor is in the command-line. It enables use-cases a 1001 administrators have (had) a 1001 separate scripts for. The GUI though still is one of Revisor's main features. For anything more advanced then what is in the GUI already, I'm gonna need help in both designing the GUI program/dialog flow as well as enabling the disabled advanced button just to not obfuscate the dialogs.