How to prevent automake from overwrting _DATA file
Clash Royale CLAN TAG#URR8PPP
In Makefile.am we have:
bin_PROGRAMS = sample
sample_SOURCES = main.cpp
sampleconfdir = $(sysconfdir)/sample
sampleconf_DATA = sample.cfg
whenever I install the application using make install, the file sample.cfg gets overwritten. How to tell automake to skip copy if file is already present?
automake autotools software-distribution
edited Feb 3 at 8:46
Kusalananda
132k17252414
asked Feb 3 at 5:10
AliAli
31
add a comment |
In Makefile.am we have:
bin_PROGRAMS = sample
sample_SOURCES = main.cpp
sampleconfdir = $(sysconfdir)/sample
sampleconf_DATA = sample.cfg
whenever I install the application using make install, the file sample.cfg gets overwritten. How to tell automake to skip copy if file is already present?
automake autotools software-distribution
edited Feb 3 at 8:46
Kusalananda
132k17252414
asked Feb 3 at 5:10
AliAli
31
add a comment |
In Makefile.am we have:
bin_PROGRAMS = sample
sample_SOURCES = main.cpp
sampleconfdir = $(sysconfdir)/sample
sampleconf_DATA = sample.cfg
whenever I install the application using make install, the file sample.cfg gets overwritten. How to tell automake to skip copy if file is already present?
automake autotools software-distribution
edited Feb 3 at 8:46
Kusalananda
132k17252414
asked Feb 3 at 5:10
AliAli
31
In Makefile.am we have:
bin_PROGRAMS = sample
sample_SOURCES = main.cpp
sampleconfdir = $(sysconfdir)/sample
sampleconf_DATA = sample.cfg
whenever I install the application using make install, the file sample.cfg gets overwritten. How to tell automake to skip copy if file is already present?
automake autotools software-distribution
automake autotools software-distribution
edited Feb 3 at 8:46
Kusalananda
132k17252414
asked Feb 3 at 5:10
AliAli
31
edited Feb 3 at 8:46
Kusalananda
132k17252414
asked Feb 3 at 5:10
AliAli
31
edited Feb 3 at 8:46
Kusalananda
132k17252414
edited Feb 3 at 8:46
Kusalananda
132k17252414
edited Feb 3 at 8:46
Kusalananda
132k17252414
132k17252414
asked Feb 3 at 5:10
AliAli
31
asked Feb 3 at 5:10
AliAli
31
asked Feb 3 at 5:10
AliAli
31
31
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
It is fairly common for software to install example configurations and let the user copy and modify this configuration for use with their actual installation. By "user" I mean anyone installing the software, be it a local administrator (root) installing the software system-wide or an unprivileged user installing the software under their $HOME somewhere.
Example configuration files may, for example, be installed
- in or under
sysconfdir, but with a modified filename (for example with a.examplesuffix). - is a separate
examplesdirectory somewhere underdocdir.
The INSTALL document would then direct the user to copy and modify these examples to suit their needs.
The benefit of this is that the user installing a new version of the software would get an up to date example of the configuration file or files. They can then update their actual configuration based on the new files if they need to do so.
Avoiding installing a new configuration file, and not installing examples, would possibly leave the user in a bewildered state when the syntax of the configuration, or any of its settings, has changed as they don't know what the file should look like (unless this is clearly mentioned in the utility's manual and upgrade instructions).
answered Feb 3 at 8:44
KusalanandaKusalananda
132k17252414
In my case, sample.cfg is a configuration file that should only be changed by super users. So, letting user take a copy and do whatever, is not applicable. Am I correct?
– Ali
Feb 3 at 8:54
@Ali The "user" may well be a local administrator (someone with root authority), so what I wrote still applies.
– Kusalananda
Feb 3 at 9:00
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498386%2fhow-to-prevent-automake-from-overwrting-data-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
It is fairly common for software to install example configurations and let the user copy and modify this configuration for use with their actual installation. By "user" I mean anyone installing the software, be it a local administrator (root) installing the software system-wide or an unprivileged user installing the software under their $HOME somewhere.
Example configuration files may, for example, be installed
- in or under
sysconfdir, but with a modified filename (for example with a.examplesuffix). - is a separate
examplesdirectory somewhere underdocdir.
The INSTALL document would then direct the user to copy and modify these examples to suit their needs.
The benefit of this is that the user installing a new version of the software would get an up to date example of the configuration file or files. They can then update their actual configuration based on the new files if they need to do so.
Avoiding installing a new configuration file, and not installing examples, would possibly leave the user in a bewildered state when the syntax of the configuration, or any of its settings, has changed as they don't know what the file should look like (unless this is clearly mentioned in the utility's manual and upgrade instructions).
answered Feb 3 at 8:44
KusalanandaKusalananda
132k17252414
In my case, sample.cfg is a configuration file that should only be changed by super users. So, letting user take a copy and do whatever, is not applicable. Am I correct?
– Ali
Feb 3 at 8:54
@Ali The "user" may well be a local administrator (someone with root authority), so what I wrote still applies.
– Kusalananda
Feb 3 at 9:00
add a comment |
It is fairly common for software to install example configurations and let the user copy and modify this configuration for use with their actual installation. By "user" I mean anyone installing the software, be it a local administrator (root) installing the software system-wide or an unprivileged user installing the software under their $HOME somewhere.
Example configuration files may, for example, be installed
- in or under
sysconfdir, but with a modified filename (for example with a.examplesuffix). - is a separate
examplesdirectory somewhere underdocdir.
The INSTALL document would then direct the user to copy and modify these examples to suit their needs.
The benefit of this is that the user installing a new version of the software would get an up to date example of the configuration file or files. They can then update their actual configuration based on the new files if they need to do so.
Avoiding installing a new configuration file, and not installing examples, would possibly leave the user in a bewildered state when the syntax of the configuration, or any of its settings, has changed as they don't know what the file should look like (unless this is clearly mentioned in the utility's manual and upgrade instructions).
answered Feb 3 at 8:44
KusalanandaKusalananda
132k17252414
In my case, sample.cfg is a configuration file that should only be changed by super users. So, letting user take a copy and do whatever, is not applicable. Am I correct?
– Ali
Feb 3 at 8:54
@Ali The "user" may well be a local administrator (someone with root authority), so what I wrote still applies.
– Kusalananda
Feb 3 at 9:00
add a comment |
It is fairly common for software to install example configurations and let the user copy and modify this configuration for use with their actual installation. By "user" I mean anyone installing the software, be it a local administrator (root) installing the software system-wide or an unprivileged user installing the software under their $HOME somewhere.
Example configuration files may, for example, be installed
- in or under
sysconfdir, but with a modified filename (for example with a.examplesuffix). - is a separate
examplesdirectory somewhere underdocdir.
The INSTALL document would then direct the user to copy and modify these examples to suit their needs.
The benefit of this is that the user installing a new version of the software would get an up to date example of the configuration file or files. They can then update their actual configuration based on the new files if they need to do so.
Avoiding installing a new configuration file, and not installing examples, would possibly leave the user in a bewildered state when the syntax of the configuration, or any of its settings, has changed as they don't know what the file should look like (unless this is clearly mentioned in the utility's manual and upgrade instructions).
answered Feb 3 at 8:44
KusalanandaKusalananda
132k17252414
It is fairly common for software to install example configurations and let the user copy and modify this configuration for use with their actual installation. By "user" I mean anyone installing the software, be it a local administrator (root) installing the software system-wide or an unprivileged user installing the software under their $HOME somewhere.
Example configuration files may, for example, be installed
- in or under
sysconfdir, but with a modified filename (for example with a.examplesuffix). - is a separate
examplesdirectory somewhere underdocdir.
The INSTALL document would then direct the user to copy and modify these examples to suit their needs.
The benefit of this is that the user installing a new version of the software would get an up to date example of the configuration file or files. They can then update their actual configuration based on the new files if they need to do so.
Avoiding installing a new configuration file, and not installing examples, would possibly leave the user in a bewildered state when the syntax of the configuration, or any of its settings, has changed as they don't know what the file should look like (unless this is clearly mentioned in the utility's manual and upgrade instructions).
answered Feb 3 at 8:44
KusalanandaKusalananda
132k17252414
edited Feb 3 at 9:02
answered Feb 3 at 8:44
KusalanandaKusalananda
132k17252414
answered Feb 3 at 8:44
KusalanandaKusalananda
132k17252414
answered Feb 3 at 8:44
KusalanandaKusalananda
132k17252414
132k17252414
In my case, sample.cfg is a configuration file that should only be changed by super users. So, letting user take a copy and do whatever, is not applicable. Am I correct?
– Ali
Feb 3 at 8:54
@Ali The "user" may well be a local administrator (someone with root authority), so what I wrote still applies.
– Kusalananda
Feb 3 at 9:00
add a comment |
In my case, sample.cfg is a configuration file that should only be changed by super users. So, letting user take a copy and do whatever, is not applicable. Am I correct?
– Ali
Feb 3 at 8:54
@Ali The "user" may well be a local administrator (someone with root authority), so what I wrote still applies.
– Kusalananda
Feb 3 at 9:00
In my case, sample.cfg is a configuration file that should only be changed by super users. So, letting user take a copy and do whatever, is not applicable. Am I correct?
– Ali
Feb 3 at 8:54
In my case, sample.cfg is a configuration file that should only be changed by super users. So, letting user take a copy and do whatever, is not applicable. Am I correct?
– Ali
Feb 3 at 8:54
@Ali The "user" may well be a local administrator (someone with root authority), so what I wrote still applies.
– Kusalananda
Feb 3 at 9:00
@Ali The "user" may well be a local administrator (someone with root authority), so what I wrote still applies.
– Kusalananda
Feb 3 at 9:00
add a comment |
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f498386%2fhow-to-prevent-automake-from-overwrting-data-file%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown