-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consolidate configuration files #12
Labels
Comments
@Fxhnd We are going with the .macleod folder, yes? |
Yes, it think that is what we agreed on.
…On Feb 10, 2018 7:15 PM, "Evan M. R. Sampson" ***@***.***> wrote:
@Fxhnd <https://github.com/fxhnd> We are going with the .macleod folder,
yes?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADm56ulXyYGrfY5yBehRvcQ2WePnSe_3ks5tTjETgaJpZM4P50_c>
.
|
We could just go with a regular macleod/ folder and drop the leading "." so
it doesn't look weird for Windows users. The leading period was to make the
folder hidden on *Nix systems, but in hindsight that's not the most user
friendly approach.
Best,
Rob
…On Sat, Feb 10, 2018 at 7:37 PM thahmann ***@***.***> wrote:
Yes, it think that is what we agreed on.
On Feb 10, 2018 7:15 PM, "Evan M. R. Sampson" ***@***.***>
wrote:
> @Fxhnd <https://github.com/fxhnd> We are going with the .macleod folder,
> yes?
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#12 (comment)>,
> or mute the thread
> <
https://github.com/notifications/unsubscribe-auth/ADm56ulXyYGrfY5yBehRvcQ2WePnSe_3ks5tTjETgaJpZM4P50_c
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHyBkttNMy1o1Fv59w0490lnTorKNvfEks5tTjZjgaJpZM4P50_c>
.
|
I agree, lets drop the leading period.
Torsten
…On 2/10/2018 8:05 PM, Robert Powell wrote:
We could just go with a regular macleod/ folder and drop the leading "." so
it doesn't look weird for Windows users. The leading period was to make the
folder hidden on *Nix systems, but in hindsight that's not the most user
friendly approach.
Best,
Rob
On Sat, Feb 10, 2018 at 7:37 PM thahmann ***@***.***> wrote:
> Yes, it think that is what we agreed on.
>
> On Feb 10, 2018 7:15 PM, "Evan M. R. Sampson" ***@***.***>
> wrote:
>
> > @Fxhnd <https://github.com/fxhnd> We are going with the .macleod
folder,
> > yes?
> >
> > —
> > You are receiving this because you are subscribed to this thread.
> > Reply to this email directly, view it on GitHub
> > <#12 (comment)>,
> > or mute the thread
> > <
>
https://github.com/notifications/unsubscribe-auth/ADm56ulXyYGrfY5yBehRvcQ2WePnSe_3ks5tTjETgaJpZM4P50_c
> >
> > .
> >
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#12 (comment)>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/AHyBkttNMy1o1Fv59w0490lnTorKNvfEks5tTjZjgaJpZM4P50_c>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADm56k-KACz62Rll--gQZYAXkOuusNJOks5tTjzggaJpZM4P50_c>.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
At the moment we have three separate configuration files in the conf/ directory. The only difference between them are paths to base directories and command names/return values. It might be better to take the existing configuration files and place them under doc/sample_config for reference.
We would then update the software to look in the $USER/.macleod (*Nix) or $USER/macleod directory for a single configuration file. Setting the correct config values is then an installation step where a user copies the closest configuration and updates it accordingly.
This would also keep us from getting our config files stuck in the baseline every so often.
The text was updated successfully, but these errors were encountered: