How to make MSYS (MSYS2) portable












4















On Windows, I have a C:msys32 folder (containing what I believe to be a MSYS2 install) created for/by an ESP32 development environment (located in ~/esp). The MSYS home folder includes my Windows username.



Now when I copy that install to another computer, suddenly that folder changes names which I find disturbing by itself, as this isn't "my folder", it is just a name to get around a Linux requirement, it could be some fixed (canonical) name such as 'user'.



More significantly this behaviour means my install isn't portable. Whe I copy the msys32 folder to another computer everything either breaks, or doesn't make any sense. For me it would be best if that username was simply removed from the path, but I'll take second best, which is to give it a fixed name. How can I do that?



PS I understand the goal of msys is to recreate a Linux environment, but please consider that "multi-user" is a dinosaur in todays world where most people are "multi-computer".










share|improve this question























  • It should be portable, but if your username on the new machine is different then it will create a new /home/<username> directory of course. It's also possible that some /etc/fstab or /etc/passwd editing took place. Newer cygwin/msys versions don't need /etc/passwd and in your case a custom /etc/fstab is also not necessary, I think.

    – T Nierath
    May 9 '18 at 12:34











  • @TNierath Note I explicitly do NOT want to know these things: portable is portable. The username is redundant, this is not a real install, just a dev environment. So the "of course" you mention is really not "of course" to me. That <username> you mention, better be something fixed. I believe that will better attend most users, as nobody cares about usernames, as long as they are distinct. But thank you, you obviously know what you're talking about.

    – user287749
    May 9 '18 at 13:02













  • Note that this really breaks otherwise portable installs: apps like Eclipse use the home folder, and it will be wrong. A global search and replace of the username does not resolve.

    – user287749
    May 9 '18 at 13:07











  • Well, it isn't portable in that sense. Cygwin simulates a POSIX environment, that means when you start a shell it expects a username, which is derived from your windows account. The programs in /usr /bin and settings in /etc are always the same since they are global settings. For your needs, it shouldn't matter if a new user directory with default config files is created on the fly. However, since the install was created by "ESP32" it could have modified the /etc config files.

    – T Nierath
    May 9 '18 at 14:21











  • @TNierath "that means when you start a shell it expects a username, which is derived from your windows account". That may seem perfectly logical to you, but it really isn't. Why should that username be the same as my windows account? Why doesn't it allow me to choose? That simple option would make portability possible. Portability means the end of lots of frustrations, for which normal people do not have the time or the means to resolve. But anyhow, there's no way to force a user-selected username (or home folder)? Thanks.

    – user287749
    May 9 '18 at 18:45
















4















On Windows, I have a C:msys32 folder (containing what I believe to be a MSYS2 install) created for/by an ESP32 development environment (located in ~/esp). The MSYS home folder includes my Windows username.



Now when I copy that install to another computer, suddenly that folder changes names which I find disturbing by itself, as this isn't "my folder", it is just a name to get around a Linux requirement, it could be some fixed (canonical) name such as 'user'.



More significantly this behaviour means my install isn't portable. Whe I copy the msys32 folder to another computer everything either breaks, or doesn't make any sense. For me it would be best if that username was simply removed from the path, but I'll take second best, which is to give it a fixed name. How can I do that?



PS I understand the goal of msys is to recreate a Linux environment, but please consider that "multi-user" is a dinosaur in todays world where most people are "multi-computer".










share|improve this question























  • It should be portable, but if your username on the new machine is different then it will create a new /home/<username> directory of course. It's also possible that some /etc/fstab or /etc/passwd editing took place. Newer cygwin/msys versions don't need /etc/passwd and in your case a custom /etc/fstab is also not necessary, I think.

    – T Nierath
    May 9 '18 at 12:34











  • @TNierath Note I explicitly do NOT want to know these things: portable is portable. The username is redundant, this is not a real install, just a dev environment. So the "of course" you mention is really not "of course" to me. That <username> you mention, better be something fixed. I believe that will better attend most users, as nobody cares about usernames, as long as they are distinct. But thank you, you obviously know what you're talking about.

    – user287749
    May 9 '18 at 13:02













  • Note that this really breaks otherwise portable installs: apps like Eclipse use the home folder, and it will be wrong. A global search and replace of the username does not resolve.

    – user287749
    May 9 '18 at 13:07











  • Well, it isn't portable in that sense. Cygwin simulates a POSIX environment, that means when you start a shell it expects a username, which is derived from your windows account. The programs in /usr /bin and settings in /etc are always the same since they are global settings. For your needs, it shouldn't matter if a new user directory with default config files is created on the fly. However, since the install was created by "ESP32" it could have modified the /etc config files.

    – T Nierath
    May 9 '18 at 14:21











  • @TNierath "that means when you start a shell it expects a username, which is derived from your windows account". That may seem perfectly logical to you, but it really isn't. Why should that username be the same as my windows account? Why doesn't it allow me to choose? That simple option would make portability possible. Portability means the end of lots of frustrations, for which normal people do not have the time or the means to resolve. But anyhow, there's no way to force a user-selected username (or home folder)? Thanks.

    – user287749
    May 9 '18 at 18:45














4












4








4


1






On Windows, I have a C:msys32 folder (containing what I believe to be a MSYS2 install) created for/by an ESP32 development environment (located in ~/esp). The MSYS home folder includes my Windows username.



Now when I copy that install to another computer, suddenly that folder changes names which I find disturbing by itself, as this isn't "my folder", it is just a name to get around a Linux requirement, it could be some fixed (canonical) name such as 'user'.



More significantly this behaviour means my install isn't portable. Whe I copy the msys32 folder to another computer everything either breaks, or doesn't make any sense. For me it would be best if that username was simply removed from the path, but I'll take second best, which is to give it a fixed name. How can I do that?



PS I understand the goal of msys is to recreate a Linux environment, but please consider that "multi-user" is a dinosaur in todays world where most people are "multi-computer".










share|improve this question














On Windows, I have a C:msys32 folder (containing what I believe to be a MSYS2 install) created for/by an ESP32 development environment (located in ~/esp). The MSYS home folder includes my Windows username.



Now when I copy that install to another computer, suddenly that folder changes names which I find disturbing by itself, as this isn't "my folder", it is just a name to get around a Linux requirement, it could be some fixed (canonical) name such as 'user'.



More significantly this behaviour means my install isn't portable. Whe I copy the msys32 folder to another computer everything either breaks, or doesn't make any sense. For me it would be best if that username was simply removed from the path, but I'll take second best, which is to give it a fixed name. How can I do that?



PS I understand the goal of msys is to recreate a Linux environment, but please consider that "multi-user" is a dinosaur in todays world where most people are "multi-computer".







msys






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked May 9 '18 at 12:24









user287749user287749

233




233













  • It should be portable, but if your username on the new machine is different then it will create a new /home/<username> directory of course. It's also possible that some /etc/fstab or /etc/passwd editing took place. Newer cygwin/msys versions don't need /etc/passwd and in your case a custom /etc/fstab is also not necessary, I think.

    – T Nierath
    May 9 '18 at 12:34











  • @TNierath Note I explicitly do NOT want to know these things: portable is portable. The username is redundant, this is not a real install, just a dev environment. So the "of course" you mention is really not "of course" to me. That <username> you mention, better be something fixed. I believe that will better attend most users, as nobody cares about usernames, as long as they are distinct. But thank you, you obviously know what you're talking about.

    – user287749
    May 9 '18 at 13:02













  • Note that this really breaks otherwise portable installs: apps like Eclipse use the home folder, and it will be wrong. A global search and replace of the username does not resolve.

    – user287749
    May 9 '18 at 13:07











  • Well, it isn't portable in that sense. Cygwin simulates a POSIX environment, that means when you start a shell it expects a username, which is derived from your windows account. The programs in /usr /bin and settings in /etc are always the same since they are global settings. For your needs, it shouldn't matter if a new user directory with default config files is created on the fly. However, since the install was created by "ESP32" it could have modified the /etc config files.

    – T Nierath
    May 9 '18 at 14:21











  • @TNierath "that means when you start a shell it expects a username, which is derived from your windows account". That may seem perfectly logical to you, but it really isn't. Why should that username be the same as my windows account? Why doesn't it allow me to choose? That simple option would make portability possible. Portability means the end of lots of frustrations, for which normal people do not have the time or the means to resolve. But anyhow, there's no way to force a user-selected username (or home folder)? Thanks.

    – user287749
    May 9 '18 at 18:45



















  • It should be portable, but if your username on the new machine is different then it will create a new /home/<username> directory of course. It's also possible that some /etc/fstab or /etc/passwd editing took place. Newer cygwin/msys versions don't need /etc/passwd and in your case a custom /etc/fstab is also not necessary, I think.

    – T Nierath
    May 9 '18 at 12:34











  • @TNierath Note I explicitly do NOT want to know these things: portable is portable. The username is redundant, this is not a real install, just a dev environment. So the "of course" you mention is really not "of course" to me. That <username> you mention, better be something fixed. I believe that will better attend most users, as nobody cares about usernames, as long as they are distinct. But thank you, you obviously know what you're talking about.

    – user287749
    May 9 '18 at 13:02













  • Note that this really breaks otherwise portable installs: apps like Eclipse use the home folder, and it will be wrong. A global search and replace of the username does not resolve.

    – user287749
    May 9 '18 at 13:07











  • Well, it isn't portable in that sense. Cygwin simulates a POSIX environment, that means when you start a shell it expects a username, which is derived from your windows account. The programs in /usr /bin and settings in /etc are always the same since they are global settings. For your needs, it shouldn't matter if a new user directory with default config files is created on the fly. However, since the install was created by "ESP32" it could have modified the /etc config files.

    – T Nierath
    May 9 '18 at 14:21











  • @TNierath "that means when you start a shell it expects a username, which is derived from your windows account". That may seem perfectly logical to you, but it really isn't. Why should that username be the same as my windows account? Why doesn't it allow me to choose? That simple option would make portability possible. Portability means the end of lots of frustrations, for which normal people do not have the time or the means to resolve. But anyhow, there's no way to force a user-selected username (or home folder)? Thanks.

    – user287749
    May 9 '18 at 18:45

















It should be portable, but if your username on the new machine is different then it will create a new /home/<username> directory of course. It's also possible that some /etc/fstab or /etc/passwd editing took place. Newer cygwin/msys versions don't need /etc/passwd and in your case a custom /etc/fstab is also not necessary, I think.

– T Nierath
May 9 '18 at 12:34





It should be portable, but if your username on the new machine is different then it will create a new /home/<username> directory of course. It's also possible that some /etc/fstab or /etc/passwd editing took place. Newer cygwin/msys versions don't need /etc/passwd and in your case a custom /etc/fstab is also not necessary, I think.

– T Nierath
May 9 '18 at 12:34













@TNierath Note I explicitly do NOT want to know these things: portable is portable. The username is redundant, this is not a real install, just a dev environment. So the "of course" you mention is really not "of course" to me. That <username> you mention, better be something fixed. I believe that will better attend most users, as nobody cares about usernames, as long as they are distinct. But thank you, you obviously know what you're talking about.

– user287749
May 9 '18 at 13:02







@TNierath Note I explicitly do NOT want to know these things: portable is portable. The username is redundant, this is not a real install, just a dev environment. So the "of course" you mention is really not "of course" to me. That <username> you mention, better be something fixed. I believe that will better attend most users, as nobody cares about usernames, as long as they are distinct. But thank you, you obviously know what you're talking about.

– user287749
May 9 '18 at 13:02















Note that this really breaks otherwise portable installs: apps like Eclipse use the home folder, and it will be wrong. A global search and replace of the username does not resolve.

– user287749
May 9 '18 at 13:07





Note that this really breaks otherwise portable installs: apps like Eclipse use the home folder, and it will be wrong. A global search and replace of the username does not resolve.

– user287749
May 9 '18 at 13:07













Well, it isn't portable in that sense. Cygwin simulates a POSIX environment, that means when you start a shell it expects a username, which is derived from your windows account. The programs in /usr /bin and settings in /etc are always the same since they are global settings. For your needs, it shouldn't matter if a new user directory with default config files is created on the fly. However, since the install was created by "ESP32" it could have modified the /etc config files.

– T Nierath
May 9 '18 at 14:21





Well, it isn't portable in that sense. Cygwin simulates a POSIX environment, that means when you start a shell it expects a username, which is derived from your windows account. The programs in /usr /bin and settings in /etc are always the same since they are global settings. For your needs, it shouldn't matter if a new user directory with default config files is created on the fly. However, since the install was created by "ESP32" it could have modified the /etc config files.

– T Nierath
May 9 '18 at 14:21













@TNierath "that means when you start a shell it expects a username, which is derived from your windows account". That may seem perfectly logical to you, but it really isn't. Why should that username be the same as my windows account? Why doesn't it allow me to choose? That simple option would make portability possible. Portability means the end of lots of frustrations, for which normal people do not have the time or the means to resolve. But anyhow, there's no way to force a user-selected username (or home folder)? Thanks.

– user287749
May 9 '18 at 18:45





@TNierath "that means when you start a shell it expects a username, which is derived from your windows account". That may seem perfectly logical to you, but it really isn't. Why should that username be the same as my windows account? Why doesn't it allow me to choose? That simple option would make portability possible. Portability means the end of lots of frustrations, for which normal people do not have the time or the means to resolve. But anyhow, there's no way to force a user-selected username (or home folder)? Thanks.

– user287749
May 9 '18 at 18:45










3 Answers
3






active

oldest

votes


















0














I'm not quite sure what to make of "everything either breaks, or doesn't make any sense" and if I can help your with that.



Regarding the different userprofiles, home paths, usernames, and how they relate to each other. Keep in mind that every local user account on Windows is always unique anyway, you may log into two Windows machines with the same account name and same password but their SIDs are always different. This usually does not matter for you, only because the default file permmissions are set up for "Authenticated Users" and similar abstract groups.



Similarly on unix, you usually care about the contents of your home folder and file access rights, aside from that the username or underlying UID are of no great concern, it's just the name you have to provide upon login.



Unless "ESP32" did something freaky with the /etc configuration files, things should just work no matter what username is shown on the prompt, setting %HOME% via the Windows system properties is my preferred approach to specify my custom home directory, since programs like the windows build of emacs also respect this setting. If you want a fully self-contained portable solution for exactly one user, then /etc/nsswitch.conf should do the job.



Detailed Information:




  • https://cygwin.com/cygwin-ug-net/ntsec.html

  • https://cygwin.com/cygwin-ug-net/setup-env.html


PS: Msys is a cygwin derived build environment to help the Windows port of gcc and friends (collectively called mingw) build software on Windows that is in theory cross platform but mostly built on Unix and came to rely on the unix tools for building. That's it. Cygwin aims much higher than that and if you want to, for example, run a ssh server with privilege separation then cygwin de-facto stops being portable due to stuff like file permission problems and missing accounts.






share|improve this answer
























  • I was blocked from giving you marks, given my low score on this section, so I did so in some other questions

    – user287749
    May 10 '18 at 13:57



















1














Today, I found a nice MSYS2 portable package here: MSYS2 Portable 2018.05.31 Dev Test 1 | PortableApps.com - Portable software for USB, portable and cloud drives






share|improve this answer

































    0














    For my needs it was sufficient to edit "db_home: /home/user" in "C:msys32etcnsswitch.conf" before running mingw32.exe.



    After running ming32.exe, c:msys32homeuser will be created, with the usual files in it. It is the new home folder. Now all paths in userspace are constants, and installs can be zipped up and copied to another PC, and all install problems vanish.






    share|improve this answer























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "3"
      };
      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: true,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: 10,
      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%2fsuperuser.com%2fquestions%2f1321097%2fhow-to-make-msys-msys2-portable%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









      0














      I'm not quite sure what to make of "everything either breaks, or doesn't make any sense" and if I can help your with that.



      Regarding the different userprofiles, home paths, usernames, and how they relate to each other. Keep in mind that every local user account on Windows is always unique anyway, you may log into two Windows machines with the same account name and same password but their SIDs are always different. This usually does not matter for you, only because the default file permmissions are set up for "Authenticated Users" and similar abstract groups.



      Similarly on unix, you usually care about the contents of your home folder and file access rights, aside from that the username or underlying UID are of no great concern, it's just the name you have to provide upon login.



      Unless "ESP32" did something freaky with the /etc configuration files, things should just work no matter what username is shown on the prompt, setting %HOME% via the Windows system properties is my preferred approach to specify my custom home directory, since programs like the windows build of emacs also respect this setting. If you want a fully self-contained portable solution for exactly one user, then /etc/nsswitch.conf should do the job.



      Detailed Information:




      • https://cygwin.com/cygwin-ug-net/ntsec.html

      • https://cygwin.com/cygwin-ug-net/setup-env.html


      PS: Msys is a cygwin derived build environment to help the Windows port of gcc and friends (collectively called mingw) build software on Windows that is in theory cross platform but mostly built on Unix and came to rely on the unix tools for building. That's it. Cygwin aims much higher than that and if you want to, for example, run a ssh server with privilege separation then cygwin de-facto stops being portable due to stuff like file permission problems and missing accounts.






      share|improve this answer
























      • I was blocked from giving you marks, given my low score on this section, so I did so in some other questions

        – user287749
        May 10 '18 at 13:57
















      0














      I'm not quite sure what to make of "everything either breaks, or doesn't make any sense" and if I can help your with that.



      Regarding the different userprofiles, home paths, usernames, and how they relate to each other. Keep in mind that every local user account on Windows is always unique anyway, you may log into two Windows machines with the same account name and same password but their SIDs are always different. This usually does not matter for you, only because the default file permmissions are set up for "Authenticated Users" and similar abstract groups.



      Similarly on unix, you usually care about the contents of your home folder and file access rights, aside from that the username or underlying UID are of no great concern, it's just the name you have to provide upon login.



      Unless "ESP32" did something freaky with the /etc configuration files, things should just work no matter what username is shown on the prompt, setting %HOME% via the Windows system properties is my preferred approach to specify my custom home directory, since programs like the windows build of emacs also respect this setting. If you want a fully self-contained portable solution for exactly one user, then /etc/nsswitch.conf should do the job.



      Detailed Information:




      • https://cygwin.com/cygwin-ug-net/ntsec.html

      • https://cygwin.com/cygwin-ug-net/setup-env.html


      PS: Msys is a cygwin derived build environment to help the Windows port of gcc and friends (collectively called mingw) build software on Windows that is in theory cross platform but mostly built on Unix and came to rely on the unix tools for building. That's it. Cygwin aims much higher than that and if you want to, for example, run a ssh server with privilege separation then cygwin de-facto stops being portable due to stuff like file permission problems and missing accounts.






      share|improve this answer
























      • I was blocked from giving you marks, given my low score on this section, so I did so in some other questions

        – user287749
        May 10 '18 at 13:57














      0












      0








      0







      I'm not quite sure what to make of "everything either breaks, or doesn't make any sense" and if I can help your with that.



      Regarding the different userprofiles, home paths, usernames, and how they relate to each other. Keep in mind that every local user account on Windows is always unique anyway, you may log into two Windows machines with the same account name and same password but their SIDs are always different. This usually does not matter for you, only because the default file permmissions are set up for "Authenticated Users" and similar abstract groups.



      Similarly on unix, you usually care about the contents of your home folder and file access rights, aside from that the username or underlying UID are of no great concern, it's just the name you have to provide upon login.



      Unless "ESP32" did something freaky with the /etc configuration files, things should just work no matter what username is shown on the prompt, setting %HOME% via the Windows system properties is my preferred approach to specify my custom home directory, since programs like the windows build of emacs also respect this setting. If you want a fully self-contained portable solution for exactly one user, then /etc/nsswitch.conf should do the job.



      Detailed Information:




      • https://cygwin.com/cygwin-ug-net/ntsec.html

      • https://cygwin.com/cygwin-ug-net/setup-env.html


      PS: Msys is a cygwin derived build environment to help the Windows port of gcc and friends (collectively called mingw) build software on Windows that is in theory cross platform but mostly built on Unix and came to rely on the unix tools for building. That's it. Cygwin aims much higher than that and if you want to, for example, run a ssh server with privilege separation then cygwin de-facto stops being portable due to stuff like file permission problems and missing accounts.






      share|improve this answer













      I'm not quite sure what to make of "everything either breaks, or doesn't make any sense" and if I can help your with that.



      Regarding the different userprofiles, home paths, usernames, and how they relate to each other. Keep in mind that every local user account on Windows is always unique anyway, you may log into two Windows machines with the same account name and same password but their SIDs are always different. This usually does not matter for you, only because the default file permmissions are set up for "Authenticated Users" and similar abstract groups.



      Similarly on unix, you usually care about the contents of your home folder and file access rights, aside from that the username or underlying UID are of no great concern, it's just the name you have to provide upon login.



      Unless "ESP32" did something freaky with the /etc configuration files, things should just work no matter what username is shown on the prompt, setting %HOME% via the Windows system properties is my preferred approach to specify my custom home directory, since programs like the windows build of emacs also respect this setting. If you want a fully self-contained portable solution for exactly one user, then /etc/nsswitch.conf should do the job.



      Detailed Information:




      • https://cygwin.com/cygwin-ug-net/ntsec.html

      • https://cygwin.com/cygwin-ug-net/setup-env.html


      PS: Msys is a cygwin derived build environment to help the Windows port of gcc and friends (collectively called mingw) build software on Windows that is in theory cross platform but mostly built on Unix and came to rely on the unix tools for building. That's it. Cygwin aims much higher than that and if you want to, for example, run a ssh server with privilege separation then cygwin de-facto stops being portable due to stuff like file permission problems and missing accounts.







      share|improve this answer












      share|improve this answer



      share|improve this answer










      answered May 10 '18 at 6:31









      T NierathT Nierath

      35419




      35419













      • I was blocked from giving you marks, given my low score on this section, so I did so in some other questions

        – user287749
        May 10 '18 at 13:57



















      • I was blocked from giving you marks, given my low score on this section, so I did so in some other questions

        – user287749
        May 10 '18 at 13:57

















      I was blocked from giving you marks, given my low score on this section, so I did so in some other questions

      – user287749
      May 10 '18 at 13:57





      I was blocked from giving you marks, given my low score on this section, so I did so in some other questions

      – user287749
      May 10 '18 at 13:57













      1














      Today, I found a nice MSYS2 portable package here: MSYS2 Portable 2018.05.31 Dev Test 1 | PortableApps.com - Portable software for USB, portable and cloud drives






      share|improve this answer






























        1














        Today, I found a nice MSYS2 portable package here: MSYS2 Portable 2018.05.31 Dev Test 1 | PortableApps.com - Portable software for USB, portable and cloud drives






        share|improve this answer




























          1












          1








          1







          Today, I found a nice MSYS2 portable package here: MSYS2 Portable 2018.05.31 Dev Test 1 | PortableApps.com - Portable software for USB, portable and cloud drives






          share|improve this answer















          Today, I found a nice MSYS2 portable package here: MSYS2 Portable 2018.05.31 Dev Test 1 | PortableApps.com - Portable software for USB, portable and cloud drives







          share|improve this answer














          share|improve this answer



          share|improve this answer








          edited Jan 22 at 15:50









          Gerold Broser

          281218




          281218










          answered Jun 23 '18 at 12:23









          ollydbg23ollydbg23

          21136




          21136























              0














              For my needs it was sufficient to edit "db_home: /home/user" in "C:msys32etcnsswitch.conf" before running mingw32.exe.



              After running ming32.exe, c:msys32homeuser will be created, with the usual files in it. It is the new home folder. Now all paths in userspace are constants, and installs can be zipped up and copied to another PC, and all install problems vanish.






              share|improve this answer




























                0














                For my needs it was sufficient to edit "db_home: /home/user" in "C:msys32etcnsswitch.conf" before running mingw32.exe.



                After running ming32.exe, c:msys32homeuser will be created, with the usual files in it. It is the new home folder. Now all paths in userspace are constants, and installs can be zipped up and copied to another PC, and all install problems vanish.






                share|improve this answer


























                  0












                  0








                  0







                  For my needs it was sufficient to edit "db_home: /home/user" in "C:msys32etcnsswitch.conf" before running mingw32.exe.



                  After running ming32.exe, c:msys32homeuser will be created, with the usual files in it. It is the new home folder. Now all paths in userspace are constants, and installs can be zipped up and copied to another PC, and all install problems vanish.






                  share|improve this answer













                  For my needs it was sufficient to edit "db_home: /home/user" in "C:msys32etcnsswitch.conf" before running mingw32.exe.



                  After running ming32.exe, c:msys32homeuser will be created, with the usual files in it. It is the new home folder. Now all paths in userspace are constants, and installs can be zipped up and copied to another PC, and all install problems vanish.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered May 11 '18 at 12:01









                  user287749user287749

                  233




                  233






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Super User!


                      • 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%2fsuperuser.com%2fquestions%2f1321097%2fhow-to-make-msys-msys2-portable%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

                      Aardman Animations

                      Are they similar matrix

                      “minimization” problem in Euclidean space related to orthonormal basis