#43: nettestctl: creation of config files at first launch ------------------------+----------------------- Reporter: olichtne | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Component: component1 | Version: Keywords: | Blocked By: Blocking: | ------------------------+----------------------- After installation lnst doesn't have any configuration files created yet. At this point the application runs using the default values.
The first launch of the application should create the user configuration file containing the currently setup values (these will probably be the defaults).
The file will be ~/.lnst/lnst.conf
The following runs should be using the configuration contained within this file.
#43: nettestctl: creation of config files at first launch -------------------------+------------------------------------------------ Reporter: olichtne | Owner: somebody Type: defect | Status: new Priority: major | Milestone: Push LNST as a package into Fedora Component: component1 | Version: Resolution: | Keywords: Blocked By: | Blocking: -------------------------+------------------------------------------------ Changes (by olichtne):
* milestone: => Push LNST as a package into Fedora
#43: nettestctl: creation of config files at first launch -------------------------+------------------------------------------------ Reporter: olichtne | Owner: olichtne Type: defect | Status: assigned Priority: major | Milestone: Push LNST as a package into Fedora Component: component1 | Version: Resolution: | Keywords: Blocked By: | Blocking: -------------------------+------------------------------------------------ Changes (by olichtne):
* owner: somebody => olichtne * status: new => assigned
Comment:
This should be a fairly small patch, I have it mostly finished. But I have question that needs answering first. The patchset [1] I posted on Tuesday, makes it so that we can handle the operator '+=' on some of the options. The config however is not able to distinguish which values were loaded from where therefore it is only able to blindly dump its contents to string/file.
How should I act in case of options that can use '+='? Should the dumped file contain the operator '=' and all the values loaded up until now? or should it contain '+=' and no values because they will be loaded from the config files with a lower priority?
I know this is a minor issue but asking never hurts...
[1] https://lists.fedorahosted.org/pipermail/lnst- developers/2012-October/000697.html
#43: nettestctl: creation of config files at first launch -------------------------+------------------------------------------------ Reporter: olichtne | Owner: olichtne Type: defect | Status: assigned Priority: major | Milestone: Push LNST as a package into Fedora Component: component1 | Version: Resolution: | Keywords: Blocked By: | Blocking: -------------------------+------------------------------------------------
Comment (by jirka):
I do not have strong opinion. Do whatever you like best.
#43: nettestctl: creation of config files at first launch -------------------------+------------------------------------------------ Reporter: olichtne | Owner: olichtne Type: defect | Status: assigned Priority: major | Milestone: Push LNST as a package into Fedora Component: component1 | Version: Resolution: | Keywords: Blocked By: | Blocking: -------------------------+------------------------------------------------
Comment (by olichtne):
Patch set posted:
https://lists.fedorahosted.org/pipermail/lnst- developers/2012-November/000760.html
#43: nettestctl: creation of config files at first launch -------------------------+------------------------------------------------ Reporter: olichtne | Owner: olichtne Type: defect | Status: closed Priority: major | Milestone: Push LNST as a package into Fedora Component: component1 | Version: Resolution: fixed | Keywords: Blocked By: | Blocking: -------------------------+------------------------------------------------ Changes (by olichtne):
* status: assigned => closed * resolution: => fixed
Comment:
Patch set applied, closing this ticket as resolved. Now what remains is to input the correct default values. That will be done when creating the package.
lnst-developers@lists.fedorahosted.org