how to update an app you cloned and installed from GitHub?How to make svn look for if there is an update once...

How to prevent cutting edges on my TV, HDMI-connected?

Start from ones

I have a player who yells

Can you feel passing through the sound barrier in an F-16?

Why did this happen to Thanos's ships at the end of "Avengers: Endgame"?

for loop not working in bash

Prove your innocence

How would one country purchase another?

Defense against attacks using dictionaries

Are illustrations in novels frowned upon?

Attaching a piece of wood to a necklace without drilling

Is “I am getting married with my sister” ambiguous?

What is the hex versus octal timeline?

Why in most German places is the church the tallest building?

Most practical knots for hitching a line to an object while keeping the bitter end as tight as possible, without sag?

Can't stopover at Sapporo when going from Asahikawa to Chitose airport?

LeetCode: Pascal's Triangle C#

Why is my Earth simulation slower than the reality?

Irish Snap: Variant Rules

Was there ever a treaty between 2 entities with significantly different translations to the detriment of one party?

If all stars rotate, why was there a theory developed, that requires non-rotating stars?

Numbers Decrease while Letters Increase

What is the history of the university asylum law?

What is this symbol: semicircles facing eachother



how to update an app you cloned and installed from GitHub?


How to make svn look for if there is an update once a minute and if there is call some script?Why don't you need to update drivers? (Or do you?)Does Fedora 16 do automatic system updates?Fedora preupgrade-cli failsunstable apt-pinning set to -1 on stable DebianHow can I selectively update Debian Jessie programs, that is without moving to Testing?Install partly downloaded updates in DebianIgnore most updatesHow to deal with undocumented Arch Linux update failures?I've installed Manjaro linux, a derivative of Arch linux, and run into software updates circular dependency problem, suggested workaround?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















so when I google all kinds of variations on this, all I see are results on how to update the GitHub app itself or to update the version of the OS, and I can't find instructions on how to update individual apps that I have installed using git clone.



so if I downloaded an app like bettercap or hcxtools and I get a response that I should update from the master to fix an error how is that done?



if I just go and overwrite the original folder like for example my oh my zsh or my powerlevel9k won't it wipe out all my settings and customizations that I like???










share|improve this question







New contributor



Carey James is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.




























    0















    so when I google all kinds of variations on this, all I see are results on how to update the GitHub app itself or to update the version of the OS, and I can't find instructions on how to update individual apps that I have installed using git clone.



    so if I downloaded an app like bettercap or hcxtools and I get a response that I should update from the master to fix an error how is that done?



    if I just go and overwrite the original folder like for example my oh my zsh or my powerlevel9k won't it wipe out all my settings and customizations that I like???










    share|improve this question







    New contributor



    Carey James is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
    Check out our Code of Conduct.
























      0












      0








      0








      so when I google all kinds of variations on this, all I see are results on how to update the GitHub app itself or to update the version of the OS, and I can't find instructions on how to update individual apps that I have installed using git clone.



      so if I downloaded an app like bettercap or hcxtools and I get a response that I should update from the master to fix an error how is that done?



      if I just go and overwrite the original folder like for example my oh my zsh or my powerlevel9k won't it wipe out all my settings and customizations that I like???










      share|improve this question







      New contributor



      Carey James is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.











      so when I google all kinds of variations on this, all I see are results on how to update the GitHub app itself or to update the version of the OS, and I can't find instructions on how to update individual apps that I have installed using git clone.



      so if I downloaded an app like bettercap or hcxtools and I get a response that I should update from the master to fix an error how is that done?



      if I just go and overwrite the original folder like for example my oh my zsh or my powerlevel9k won't it wipe out all my settings and customizations that I like???







      upgrade






      share|improve this question







      New contributor



      Carey James is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.










      share|improve this question







      New contributor



      Carey James is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      share|improve this question




      share|improve this question






      New contributor



      Carey James is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.








      asked 2 days ago









      Carey JamesCarey James

      1




      1




      New contributor



      Carey James is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.




      New contributor




      Carey James is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
      Check out our Code of Conduct.



























          2 Answers
          2






          active

          oldest

          votes


















          1















          You shouldn't have to wipe out/overwrite the folder, as that would indeed wipe out any customizations you've made.



          The command you're looking for is git pull, which will pull any changes from the repository and merge them into your current directory. If you have committed changes to the repository, using git pull --rebase will keep your history cleaner, since it avoids a merge commit with the update. Depending on how you checked out the code, you may need to specify a remote (default is origin) and branch (master, based on your question), so your full command may be git pull origin master --rebase



          There is a possibility that you could have made changes that will conflict with updates, in which case you'll have to resolve conflicts - the Git manual provides more details on that should you need it.



          If you want to be careful, first make a copy of the folder that you want to update, then update the original folder. If something goes wrong, delete the original folder and move your copy back into place and start over.






          share|improve this answer








          New contributor



          Steven is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.





























            0















            Now you know why packaging systems like dpkg and rpm were invented - managing the install, upgrade, downgrade or removal of software is harder than it seems.



            If at all possible, you should install packaged versions of software for your distribution of choice. This might limit you to an older version of particular packages, depending on how "bleeding edge" your distro is. This is not generally a problem - in most cases, you don't actually need the latest version, and in most of the remaining cases having the latest version isn't worth the price of breaking out of your distro's packaging system.



            However, if there's no packaged version or if you really do need the latest version:




            1. your best bet is to package the program yourself. This takes some effort and some time to learn how to do it, but has the best result - software that can be easily installed, upgraded, removed, etc using your distro's package tools.



            2. Use GNU Stow or CheckInstall when you build and install the software.



              Either of these will give you many of the features of a real package (like being able to easily uninstall or upgrade your installed software), and keep your self-installed software nicely separated (e.g. in subdirs of /usr/local or /opt) from packaged software.



              Note: both of these (and similar programs like xstow) are probably available as packages for your distro. That's certainly true for Debian.



            3. For software meant to run directly out of a cloned git repository (e.g. scripts, or omzsh), just use git pull to update it as described in @Steven's answer. Note, however, that if there's a packaged version available for your distro then you should probably use that.







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


              }
              });






              Carey James is a new contributor. Be nice, and check out our Code of Conduct.










              draft saved

              draft discarded


















              StackExchange.ready(
              function () {
              StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f536529%2fhow-to-update-an-app-you-cloned-and-installed-from-github%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              1















              You shouldn't have to wipe out/overwrite the folder, as that would indeed wipe out any customizations you've made.



              The command you're looking for is git pull, which will pull any changes from the repository and merge them into your current directory. If you have committed changes to the repository, using git pull --rebase will keep your history cleaner, since it avoids a merge commit with the update. Depending on how you checked out the code, you may need to specify a remote (default is origin) and branch (master, based on your question), so your full command may be git pull origin master --rebase



              There is a possibility that you could have made changes that will conflict with updates, in which case you'll have to resolve conflicts - the Git manual provides more details on that should you need it.



              If you want to be careful, first make a copy of the folder that you want to update, then update the original folder. If something goes wrong, delete the original folder and move your copy back into place and start over.






              share|improve this answer








              New contributor



              Steven is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.


























                1















                You shouldn't have to wipe out/overwrite the folder, as that would indeed wipe out any customizations you've made.



                The command you're looking for is git pull, which will pull any changes from the repository and merge them into your current directory. If you have committed changes to the repository, using git pull --rebase will keep your history cleaner, since it avoids a merge commit with the update. Depending on how you checked out the code, you may need to specify a remote (default is origin) and branch (master, based on your question), so your full command may be git pull origin master --rebase



                There is a possibility that you could have made changes that will conflict with updates, in which case you'll have to resolve conflicts - the Git manual provides more details on that should you need it.



                If you want to be careful, first make a copy of the folder that you want to update, then update the original folder. If something goes wrong, delete the original folder and move your copy back into place and start over.






                share|improve this answer








                New contributor



                Steven is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.
























                  1














                  1










                  1









                  You shouldn't have to wipe out/overwrite the folder, as that would indeed wipe out any customizations you've made.



                  The command you're looking for is git pull, which will pull any changes from the repository and merge them into your current directory. If you have committed changes to the repository, using git pull --rebase will keep your history cleaner, since it avoids a merge commit with the update. Depending on how you checked out the code, you may need to specify a remote (default is origin) and branch (master, based on your question), so your full command may be git pull origin master --rebase



                  There is a possibility that you could have made changes that will conflict with updates, in which case you'll have to resolve conflicts - the Git manual provides more details on that should you need it.



                  If you want to be careful, first make a copy of the folder that you want to update, then update the original folder. If something goes wrong, delete the original folder and move your copy back into place and start over.






                  share|improve this answer








                  New contributor



                  Steven is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.









                  You shouldn't have to wipe out/overwrite the folder, as that would indeed wipe out any customizations you've made.



                  The command you're looking for is git pull, which will pull any changes from the repository and merge them into your current directory. If you have committed changes to the repository, using git pull --rebase will keep your history cleaner, since it avoids a merge commit with the update. Depending on how you checked out the code, you may need to specify a remote (default is origin) and branch (master, based on your question), so your full command may be git pull origin master --rebase



                  There is a possibility that you could have made changes that will conflict with updates, in which case you'll have to resolve conflicts - the Git manual provides more details on that should you need it.



                  If you want to be careful, first make a copy of the folder that you want to update, then update the original folder. If something goes wrong, delete the original folder and move your copy back into place and start over.







                  share|improve this answer








                  New contributor



                  Steven is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.








                  share|improve this answer



                  share|improve this answer






                  New contributor



                  Steven 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









                  StevenSteven

                  1111 bronze badge




                  1111 bronze badge




                  New contributor



                  Steven is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.




                  New contributor




                  Steven is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                  Check out our Code of Conduct.






























                      0















                      Now you know why packaging systems like dpkg and rpm were invented - managing the install, upgrade, downgrade or removal of software is harder than it seems.



                      If at all possible, you should install packaged versions of software for your distribution of choice. This might limit you to an older version of particular packages, depending on how "bleeding edge" your distro is. This is not generally a problem - in most cases, you don't actually need the latest version, and in most of the remaining cases having the latest version isn't worth the price of breaking out of your distro's packaging system.



                      However, if there's no packaged version or if you really do need the latest version:




                      1. your best bet is to package the program yourself. This takes some effort and some time to learn how to do it, but has the best result - software that can be easily installed, upgraded, removed, etc using your distro's package tools.



                      2. Use GNU Stow or CheckInstall when you build and install the software.



                        Either of these will give you many of the features of a real package (like being able to easily uninstall or upgrade your installed software), and keep your self-installed software nicely separated (e.g. in subdirs of /usr/local or /opt) from packaged software.



                        Note: both of these (and similar programs like xstow) are probably available as packages for your distro. That's certainly true for Debian.



                      3. For software meant to run directly out of a cloned git repository (e.g. scripts, or omzsh), just use git pull to update it as described in @Steven's answer. Note, however, that if there's a packaged version available for your distro then you should probably use that.







                      share|improve this answer






























                        0















                        Now you know why packaging systems like dpkg and rpm were invented - managing the install, upgrade, downgrade or removal of software is harder than it seems.



                        If at all possible, you should install packaged versions of software for your distribution of choice. This might limit you to an older version of particular packages, depending on how "bleeding edge" your distro is. This is not generally a problem - in most cases, you don't actually need the latest version, and in most of the remaining cases having the latest version isn't worth the price of breaking out of your distro's packaging system.



                        However, if there's no packaged version or if you really do need the latest version:




                        1. your best bet is to package the program yourself. This takes some effort and some time to learn how to do it, but has the best result - software that can be easily installed, upgraded, removed, etc using your distro's package tools.



                        2. Use GNU Stow or CheckInstall when you build and install the software.



                          Either of these will give you many of the features of a real package (like being able to easily uninstall or upgrade your installed software), and keep your self-installed software nicely separated (e.g. in subdirs of /usr/local or /opt) from packaged software.



                          Note: both of these (and similar programs like xstow) are probably available as packages for your distro. That's certainly true for Debian.



                        3. For software meant to run directly out of a cloned git repository (e.g. scripts, or omzsh), just use git pull to update it as described in @Steven's answer. Note, however, that if there's a packaged version available for your distro then you should probably use that.







                        share|improve this answer




























                          0














                          0










                          0









                          Now you know why packaging systems like dpkg and rpm were invented - managing the install, upgrade, downgrade or removal of software is harder than it seems.



                          If at all possible, you should install packaged versions of software for your distribution of choice. This might limit you to an older version of particular packages, depending on how "bleeding edge" your distro is. This is not generally a problem - in most cases, you don't actually need the latest version, and in most of the remaining cases having the latest version isn't worth the price of breaking out of your distro's packaging system.



                          However, if there's no packaged version or if you really do need the latest version:




                          1. your best bet is to package the program yourself. This takes some effort and some time to learn how to do it, but has the best result - software that can be easily installed, upgraded, removed, etc using your distro's package tools.



                          2. Use GNU Stow or CheckInstall when you build and install the software.



                            Either of these will give you many of the features of a real package (like being able to easily uninstall or upgrade your installed software), and keep your self-installed software nicely separated (e.g. in subdirs of /usr/local or /opt) from packaged software.



                            Note: both of these (and similar programs like xstow) are probably available as packages for your distro. That's certainly true for Debian.



                          3. For software meant to run directly out of a cloned git repository (e.g. scripts, or omzsh), just use git pull to update it as described in @Steven's answer. Note, however, that if there's a packaged version available for your distro then you should probably use that.







                          share|improve this answer













                          Now you know why packaging systems like dpkg and rpm were invented - managing the install, upgrade, downgrade or removal of software is harder than it seems.



                          If at all possible, you should install packaged versions of software for your distribution of choice. This might limit you to an older version of particular packages, depending on how "bleeding edge" your distro is. This is not generally a problem - in most cases, you don't actually need the latest version, and in most of the remaining cases having the latest version isn't worth the price of breaking out of your distro's packaging system.



                          However, if there's no packaged version or if you really do need the latest version:




                          1. your best bet is to package the program yourself. This takes some effort and some time to learn how to do it, but has the best result - software that can be easily installed, upgraded, removed, etc using your distro's package tools.



                          2. Use GNU Stow or CheckInstall when you build and install the software.



                            Either of these will give you many of the features of a real package (like being able to easily uninstall or upgrade your installed software), and keep your self-installed software nicely separated (e.g. in subdirs of /usr/local or /opt) from packaged software.



                            Note: both of these (and similar programs like xstow) are probably available as packages for your distro. That's certainly true for Debian.



                          3. For software meant to run directly out of a cloned git repository (e.g. scripts, or omzsh), just use git pull to update it as described in @Steven's answer. Note, however, that if there's a packaged version available for your distro then you should probably use that.








                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered 2 days ago









                          cascas

                          41.6k4 gold badges59 silver badges111 bronze badges




                          41.6k4 gold badges59 silver badges111 bronze badges

























                              Carey James is a new contributor. Be nice, and check out our Code of Conduct.










                              draft saved

                              draft discarded


















                              Carey James is a new contributor. Be nice, and check out our Code of Conduct.













                              Carey James is a new contributor. Be nice, and check out our Code of Conduct.












                              Carey James is a new contributor. Be nice, and check out our Code of Conduct.
















                              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%2f536529%2fhow-to-update-an-app-you-cloned-and-installed-from-github%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

                              Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                              Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                              Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...