On Thu, Nov 20, 2014 at 10:13 AM, Ingo Maindorfer <[email protected]> wrote:
> Hello list,
>
> we plan to make a snapshot from a msys2 folder and distribute this one
> to our developers. The reaseon for this is that we need defined versions
> of the libs and that is difficult with a rolling release...
Hello Ingo,
A multi-user setup? Sounds great! Why not setup your own curated
msys2/mingw{32,64} repositories on a local file server, then point
your users' MSYS2 installs at them instead of ours (in
/etc/pacman.conf) so that they can use MSYS2's pacman as normal? That
way you can also add your own site-specific packages to them if you
need to. I fear that anything else would be very hacky. We could do
with having some documentation regarding how to do this, but I think
you could find some from Arch Linux, otherwise a few guys on #msys2 on
oftc IRC (alexey, tabris and Elieux) may be able to help. Sounds like
something we'd like on the Wiki though.
>
> After moving the folder to new computer on a different drive letter we
> get some slightly erros like QtCreator dosen't find Qt like befor. And
> yes, I'm rerunning qtbinpatcher.
>
> My question is how can I rerun msys2_shell.bat like the very first run
> when it creates the links and setting some stuff?
Despite my strong recommendation, to pretend to MSYS2 that it's a
first-run again, you should search in /etc for MAYBE_FIRST_START,
you'll see that not having a /etc/pacman.d/gnupg or /etc/xml/catalog
folder will trigger it. This won't fix your Qt Creator issue though.
For that you'd need to re-install the
mingw-w64-{i686,x86_64}-qt-creator package(s) via pacman -U so that
the post install [1] scripts get re-run as they write configuration
files in %AppData%/QtProject/ with absolute paths.
Alternatively you could mandate that everyone uses a fixed known drive
for their MSYS2 installations so that there's no difference
machine-to-machine. This would make comparing strace output or other
logs for differences easy.
Finally, you could go with installing MSYS2 as usual from a known
installer, then use pacman -U on a directory of packages to setup the
specific versions you want of all the packages you care about. This
wouldn't be great for what you want to do as users could still run
"pacman -Syu" and get newer versions ..
[1]
https://github.com/Alexpux/MINGW-packages/blob/master/mingw-w64-qtcreator/qt-creator-x86_64.install
>
> Best Regards,
>
> Ingo
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> Msys2-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/msys2-users
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
_______________________________________________
Msys2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/msys2-users
