Dealing with GNU Stow conflicts
What is the recommended way of dealing with GNU Stow conflicts?
I tried to stow readline-6.2 and got the following warning:
> stow readline-6.2
Loading defaults from /home/josh/.stowrc
WARNING! stowing readline-6.2 would cause conflicts:
* existing target is stowed to a different package: share/info/dir =>
../../../stow_dir/stow_2.2.0_canonical_paths/share/info/dir
All operations aborted.
The clash is with the package stow_2.2.0_canonical_paths which is the package dir for stow (this is because I bootstrapped stow).
Here is is what that conflicting target contains:
> cat ~/local/share/info/dir
This is the file .../info/dir, which contains the
topmost node of the Info hierarchy, called (dir)Top.
The first time you invoke Info you start off looking at this node.
File: dir, Node: Top This is the top of the INFO tree
This (the Directory node) gives a menu of major topics.
Typing "q" exits, "?" lists all Info commands, "d" returns here,
"h" gives a primer for first-timers,
"mEmacs<Return>" visits the Emacs manual, etc.
In Emacs, you can click mouse button 2 on a menu item or cross reference
to select it.
* Menu:
System administration
* Stow: (stow). GNU Stow.
What would be the recommended way of resolving this conflict?
readline stow
asked Apr 23 '13 at 13:48
Amelio Vazquez-Reina
12.3k53130230
add a comment |
What is the recommended way of dealing with GNU Stow conflicts?
I tried to stow readline-6.2 and got the following warning:
> stow readline-6.2
Loading defaults from /home/josh/.stowrc
WARNING! stowing readline-6.2 would cause conflicts:
* existing target is stowed to a different package: share/info/dir =>
../../../stow_dir/stow_2.2.0_canonical_paths/share/info/dir
All operations aborted.
The clash is with the package stow_2.2.0_canonical_paths which is the package dir for stow (this is because I bootstrapped stow).
Here is is what that conflicting target contains:
> cat ~/local/share/info/dir
This is the file .../info/dir, which contains the
topmost node of the Info hierarchy, called (dir)Top.
The first time you invoke Info you start off looking at this node.
File: dir, Node: Top This is the top of the INFO tree
This (the Directory node) gives a menu of major topics.
Typing "q" exits, "?" lists all Info commands, "d" returns here,
"h" gives a primer for first-timers,
"mEmacs<Return>" visits the Emacs manual, etc.
In Emacs, you can click mouse button 2 on a menu item or cross reference
to select it.
* Menu:
System administration
* Stow: (stow). GNU Stow.
What would be the recommended way of resolving this conflict?
readline stow
asked Apr 23 '13 at 13:48
Amelio Vazquez-Reina
12.3k53130230
add a comment |
What is the recommended way of dealing with GNU Stow conflicts?
I tried to stow readline-6.2 and got the following warning:
> stow readline-6.2
Loading defaults from /home/josh/.stowrc
WARNING! stowing readline-6.2 would cause conflicts:
* existing target is stowed to a different package: share/info/dir =>
../../../stow_dir/stow_2.2.0_canonical_paths/share/info/dir
All operations aborted.
The clash is with the package stow_2.2.0_canonical_paths which is the package dir for stow (this is because I bootstrapped stow).
Here is is what that conflicting target contains:
> cat ~/local/share/info/dir
This is the file .../info/dir, which contains the
topmost node of the Info hierarchy, called (dir)Top.
The first time you invoke Info you start off looking at this node.
File: dir, Node: Top This is the top of the INFO tree
This (the Directory node) gives a menu of major topics.
Typing "q" exits, "?" lists all Info commands, "d" returns here,
"h" gives a primer for first-timers,
"mEmacs<Return>" visits the Emacs manual, etc.
In Emacs, you can click mouse button 2 on a menu item or cross reference
to select it.
* Menu:
System administration
* Stow: (stow). GNU Stow.
What would be the recommended way of resolving this conflict?
readline stow
asked Apr 23 '13 at 13:48
Amelio Vazquez-Reina
12.3k53130230
What is the recommended way of dealing with GNU Stow conflicts?
I tried to stow readline-6.2 and got the following warning:
> stow readline-6.2
Loading defaults from /home/josh/.stowrc
WARNING! stowing readline-6.2 would cause conflicts:
* existing target is stowed to a different package: share/info/dir =>
../../../stow_dir/stow_2.2.0_canonical_paths/share/info/dir
All operations aborted.
The clash is with the package stow_2.2.0_canonical_paths which is the package dir for stow (this is because I bootstrapped stow).
Here is is what that conflicting target contains:
> cat ~/local/share/info/dir
This is the file .../info/dir, which contains the
topmost node of the Info hierarchy, called (dir)Top.
The first time you invoke Info you start off looking at this node.
File: dir, Node: Top This is the top of the INFO tree
This (the Directory node) gives a menu of major topics.
Typing "q" exits, "?" lists all Info commands, "d" returns here,
"h" gives a primer for first-timers,
"mEmacs<Return>" visits the Emacs manual, etc.
In Emacs, you can click mouse button 2 on a menu item or cross reference
to select it.
* Menu:
System administration
* Stow: (stow). GNU Stow.
What would be the recommended way of resolving this conflict?
readline stow
readline stow
asked Apr 23 '13 at 13:48
Amelio Vazquez-Reina
12.3k53130230
asked Apr 23 '13 at 13:48
Amelio Vazquez-Reina
12.3k53130230
asked Apr 23 '13 at 13:48
Amelio Vazquez-Reina
12.3k53130230
asked Apr 23 '13 at 13:48
Amelio Vazquez-Reina
12.3k53130230
asked Apr 23 '13 at 13:48
Amelio Vazquez-Reina
12.3k53130230
12.3k53130230
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
The dir file is automatically generated/expanded by install-info and contain information about the available documentation of the texinfo documentation system.
You can simply delete this file. If you want to use info system, you can try to merge the dir into the other before. Or you can run a install-info command (e.g. install-info --info-dir=$PWD time.info.gz) in the share/info directory after you have linked all files there with stow.
Another option is to switch to xstow which can merge this file automatically if you add the following to your xstow.ini.
[exec]
match = dir # GNU info index file
exec = merge-info %t %s -o %t
exec-unstow = merge-info -u %t %s -o %t
answered Apr 23 '13 at 14:12
jofel
20.1k34780
Thank you jofel. I recently started with stow since I thought xstow was dead (the last update to xstow was in 2010). In contrast, stow seems to have an active repository and seems to be part of the official GNU tools). I have also noticed that stow has recently added some new features, perhaps closing the gap with xstow, but I may be wrong. Would you still recommend xstow? What other features have you noticed that xstow has that modern versions of stow doesn't?
– Amelio Vazquez-Reina
Apr 23 '13 at 16:31
2
Yeah, I thinkxstowis probably a dead project. I like the idea of post-(un)install hooks though - whilst Stow doesn't aim to be a full-blown package manager likerpmordpkg, hooks make sense, so I've added them to theTODOfile.
– Adam Spiers
Apr 24 '13 at 7:49
add a comment |
With GNU autotools software, you may specify --infodir separately from --prefix when you run ./configure.
I used to have a separate stow directory for all info-documents, until I realized I never read them...
answered Aug 2 '16 at 21:57
Kusalananda
122k16230375
add a comment |
You can remove the dir file after make installing but before stowing. Then, after stowing simply call install-info to merge the info files into the original dir. I think that the cleanest solution.
answered 2 days ago
memeplex
101
New contributor
memeplex is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
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%2f73426%2fdealing-with-gnu-stow-conflicts%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
The dir file is automatically generated/expanded by install-info and contain information about the available documentation of the texinfo documentation system.
You can simply delete this file. If you want to use info system, you can try to merge the dir into the other before. Or you can run a install-info command (e.g. install-info --info-dir=$PWD time.info.gz) in the share/info directory after you have linked all files there with stow.
Another option is to switch to xstow which can merge this file automatically if you add the following to your xstow.ini.
[exec]
match = dir # GNU info index file
exec = merge-info %t %s -o %t
exec-unstow = merge-info -u %t %s -o %t
answered Apr 23 '13 at 14:12
jofel
20.1k34780
Thank you jofel. I recently started with stow since I thought xstow was dead (the last update to xstow was in 2010). In contrast, stow seems to have an active repository and seems to be part of the official GNU tools). I have also noticed that stow has recently added some new features, perhaps closing the gap with xstow, but I may be wrong. Would you still recommend xstow? What other features have you noticed that xstow has that modern versions of stow doesn't?
– Amelio Vazquez-Reina
Apr 23 '13 at 16:31
2
Yeah, I thinkxstowis probably a dead project. I like the idea of post-(un)install hooks though - whilst Stow doesn't aim to be a full-blown package manager likerpmordpkg, hooks make sense, so I've added them to theTODOfile.
– Adam Spiers
Apr 24 '13 at 7:49
add a comment |
The dir file is automatically generated/expanded by install-info and contain information about the available documentation of the texinfo documentation system.
You can simply delete this file. If you want to use info system, you can try to merge the dir into the other before. Or you can run a install-info command (e.g. install-info --info-dir=$PWD time.info.gz) in the share/info directory after you have linked all files there with stow.
Another option is to switch to xstow which can merge this file automatically if you add the following to your xstow.ini.
[exec]
match = dir # GNU info index file
exec = merge-info %t %s -o %t
exec-unstow = merge-info -u %t %s -o %t
answered Apr 23 '13 at 14:12
jofel
20.1k34780
Thank you jofel. I recently started with stow since I thought xstow was dead (the last update to xstow was in 2010). In contrast, stow seems to have an active repository and seems to be part of the official GNU tools). I have also noticed that stow has recently added some new features, perhaps closing the gap with xstow, but I may be wrong. Would you still recommend xstow? What other features have you noticed that xstow has that modern versions of stow doesn't?
– Amelio Vazquez-Reina
Apr 23 '13 at 16:31
2
Yeah, I thinkxstowis probably a dead project. I like the idea of post-(un)install hooks though - whilst Stow doesn't aim to be a full-blown package manager likerpmordpkg, hooks make sense, so I've added them to theTODOfile.
– Adam Spiers
Apr 24 '13 at 7:49
add a comment |
The dir file is automatically generated/expanded by install-info and contain information about the available documentation of the texinfo documentation system.
You can simply delete this file. If you want to use info system, you can try to merge the dir into the other before. Or you can run a install-info command (e.g. install-info --info-dir=$PWD time.info.gz) in the share/info directory after you have linked all files there with stow.
Another option is to switch to xstow which can merge this file automatically if you add the following to your xstow.ini.
[exec]
match = dir # GNU info index file
exec = merge-info %t %s -o %t
exec-unstow = merge-info -u %t %s -o %t
answered Apr 23 '13 at 14:12
jofel
20.1k34780
The dir file is automatically generated/expanded by install-info and contain information about the available documentation of the texinfo documentation system.
You can simply delete this file. If you want to use info system, you can try to merge the dir into the other before. Or you can run a install-info command (e.g. install-info --info-dir=$PWD time.info.gz) in the share/info directory after you have linked all files there with stow.
Another option is to switch to xstow which can merge this file automatically if you add the following to your xstow.ini.
[exec]
match = dir # GNU info index file
exec = merge-info %t %s -o %t
exec-unstow = merge-info -u %t %s -o %t
answered Apr 23 '13 at 14:12
jofel
20.1k34780
edited Apr 24 '13 at 10:29
answered Apr 23 '13 at 14:12
jofel
20.1k34780
answered Apr 23 '13 at 14:12
jofel
20.1k34780
answered Apr 23 '13 at 14:12
jofel
20.1k34780
20.1k34780
Thank you jofel. I recently started with stow since I thought xstow was dead (the last update to xstow was in 2010). In contrast, stow seems to have an active repository and seems to be part of the official GNU tools). I have also noticed that stow has recently added some new features, perhaps closing the gap with xstow, but I may be wrong. Would you still recommend xstow? What other features have you noticed that xstow has that modern versions of stow doesn't?
– Amelio Vazquez-Reina
Apr 23 '13 at 16:31
2
Yeah, I thinkxstowis probably a dead project. I like the idea of post-(un)install hooks though - whilst Stow doesn't aim to be a full-blown package manager likerpmordpkg, hooks make sense, so I've added them to theTODOfile.
– Adam Spiers
Apr 24 '13 at 7:49
add a comment |
Thank you jofel. I recently started with stow since I thought xstow was dead (the last update to xstow was in 2010). In contrast, stow seems to have an active repository and seems to be part of the official GNU tools). I have also noticed that stow has recently added some new features, perhaps closing the gap with xstow, but I may be wrong. Would you still recommend xstow? What other features have you noticed that xstow has that modern versions of stow doesn't?
– Amelio Vazquez-Reina
Apr 23 '13 at 16:31
2
Yeah, I thinkxstowis probably a dead project. I like the idea of post-(un)install hooks though - whilst Stow doesn't aim to be a full-blown package manager likerpmordpkg, hooks make sense, so I've added them to theTODOfile.
– Adam Spiers
Apr 24 '13 at 7:49
Thank you jofel. I recently started with stow since I thought xstow was dead (the last update to xstow was in 2010). In contrast, stow seems to have an active repository and seems to be part of the official GNU tools). I have also noticed that stow has recently added some new features, perhaps closing the gap with xstow, but I may be wrong. Would you still recommend xstow? What other features have you noticed that xstow has that modern versions of stow doesn't?
– Amelio Vazquez-Reina
Apr 23 '13 at 16:31
Thank you jofel. I recently started with stow since I thought xstow was dead (the last update to xstow was in 2010). In contrast, stow seems to have an active repository and seems to be part of the official GNU tools). I have also noticed that stow has recently added some new features, perhaps closing the gap with xstow, but I may be wrong. Would you still recommend xstow? What other features have you noticed that xstow has that modern versions of stow doesn't?
– Amelio Vazquez-Reina
Apr 23 '13 at 16:31
2
2
Yeah, I think
xstow is probably a dead project. I like the idea of post-(un)install hooks though - whilst Stow doesn't aim to be a full-blown package manager like rpm or dpkg, hooks make sense, so I've added them to the TODO file.– Adam Spiers
Apr 24 '13 at 7:49
Yeah, I think
xstow is probably a dead project. I like the idea of post-(un)install hooks though - whilst Stow doesn't aim to be a full-blown package manager like rpm or dpkg, hooks make sense, so I've added them to the TODO file.– Adam Spiers
Apr 24 '13 at 7:49
add a comment |
With GNU autotools software, you may specify --infodir separately from --prefix when you run ./configure.
I used to have a separate stow directory for all info-documents, until I realized I never read them...
answered Aug 2 '16 at 21:57
Kusalananda
122k16230375
add a comment |
With GNU autotools software, you may specify --infodir separately from --prefix when you run ./configure.
I used to have a separate stow directory for all info-documents, until I realized I never read them...
answered Aug 2 '16 at 21:57
Kusalananda
122k16230375
add a comment |
With GNU autotools software, you may specify --infodir separately from --prefix when you run ./configure.
I used to have a separate stow directory for all info-documents, until I realized I never read them...
answered Aug 2 '16 at 21:57
Kusalananda
122k16230375
With GNU autotools software, you may specify --infodir separately from --prefix when you run ./configure.
I used to have a separate stow directory for all info-documents, until I realized I never read them...
answered Aug 2 '16 at 21:57
Kusalananda
122k16230375
answered Aug 2 '16 at 21:57
Kusalananda
122k16230375
answered Aug 2 '16 at 21:57
Kusalananda
122k16230375
answered Aug 2 '16 at 21:57
Kusalananda
122k16230375
122k16230375
add a comment |
add a comment |
You can remove the dir file after make installing but before stowing. Then, after stowing simply call install-info to merge the info files into the original dir. I think that the cleanest solution.
answered 2 days ago
memeplex
101
New contributor
memeplex is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
You can remove the dir file after make installing but before stowing. Then, after stowing simply call install-info to merge the info files into the original dir. I think that the cleanest solution.
answered 2 days ago
memeplex
101
New contributor
memeplex is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
You can remove the dir file after make installing but before stowing. Then, after stowing simply call install-info to merge the info files into the original dir. I think that the cleanest solution.
answered 2 days ago
memeplex
101
New contributor
memeplex is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
You can remove the dir file after make installing but before stowing. Then, after stowing simply call install-info to merge the info files into the original dir. I think that the cleanest solution.
answered 2 days ago
memeplex
101
New contributor
memeplex is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
memeplex
101
New contributor
memeplex is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 2 days ago
memeplex
101
answered 2 days ago
memeplex
101
101
New contributor
memeplex is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
memeplex is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
memeplex is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2f73426%2fdealing-with-gnu-stow-conflicts%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
