Dealing with GNU Stow conflicts

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP












4















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?










share|improve this question


























    4















    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?










    share|improve this question
























      4












      4








      4


      2






      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?










      share|improve this question














      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Apr 23 '13 at 13:48









      Amelio Vazquez-ReinaAmelio Vazquez-Reina

      12.4k53132233




      12.4k53132233




















          3 Answers
          3






          active

          oldest

          votes


















          3














          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





          share|improve this answer

























          • 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 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


















          1














          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...






          share|improve this answer






























            0














            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.






            share|improve this answer






















              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
              );



              );













              draft saved

              draft discarded


















              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









              3














              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





              share|improve this answer

























              • 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 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















              3














              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





              share|improve this answer

























              • 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 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













              3












              3








              3







              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





              share|improve this answer















              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






              share|improve this answer














              share|improve this answer



              share|improve this answer








              edited Apr 24 '13 at 10:29

























              answered Apr 23 '13 at 14:12









              jofeljofel

              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 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

















              • 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 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
















              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













              1














              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...






              share|improve this answer



























                1














                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...






                share|improve this answer

























                  1












                  1








                  1







                  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...






                  share|improve this answer













                  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...







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Aug 2 '16 at 21:57









                  KusalanandaKusalananda

                  124k16236387




                  124k16236387





















                      0














                      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.






                      share|improve this answer



























                        0














                        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.






                        share|improve this answer

























                          0












                          0








                          0







                          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.






                          share|improve this answer













                          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.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jan 4 at 20:03









                          memeplexmemeplex

                          101




                          101



























                              draft saved

                              draft discarded
















































                              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.




                              draft saved


                              draft discarded














                              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





















































                              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






                              Popular posts from this blog

                              How to check contact read email or not when send email to Individual?

                              Displaying single band from multi-band raster using QGIS

                              How many registers does an x86_64 CPU actually have?