Re: [Mingw-users] Using mingw-get in a scripted setup

[Geert J. <ge...@ko...>]

Keith, Renato,

Thanks for the feedback. I had looked at mingw-get list/show before, but I missed the fact that 
you have to specify the subcomponent to get installation information.

To answer Renato's question on whether I don't just simply use mingw-get install and ignore the 
errors:
The scripted setup is run on an unattended build server. When we decide to use newer versions 
of certain components, these should get updated automatically the next time the script runs 
(which version to use is specified in a configuration script).

As far as I know, mingw-get install will never update a package. So I have to check if a package 
is installed or not. If not install, I need to invoke mingw-get install, otherwise I intended to call 
mingw-get upgrade. But with the information I can extract from mingw-get list, I can even 
refine this a bit and only invoke mingw-get upgrade if there is a version mismatch.

I think I can work with this. Thanks again.

Geert

On Wednesday 09 October 2013 18:17:40 Renato Silva wrote:
> 2013/10/9 Geert Janssens <ge...@ko...>
> 
> > **
> > 
> > Hi,
> > 
> > 
> > 
> > I really like mingw-get as a tool to ease the installation of an
> > mingw/msys environment.
> > 
> > 
> > 
> > I'm unfortunately having some trouble using it for an scripted build
> > environment set up.
> > 
> > 
> > 
> > The script is supposed to install a number of packages via mingw-get
> > the first time it's called. It selects package versions bas
> > ed on a configuration file. If a package version is updated in that
> > configuration file, the next call of the script should update the
> > relevant package(s).
> > 
> > 
> > 
> > This turns out to be very difficult to do. The command line version
> > of mingw-get doesn't have an interface to query for installed
> > packages. So another way has to be found to detect this.
> > 
> > 
> > 
> > In a previous question on this same list, it was suggested to parse
> > the manifest files for this. I have tried this, but that also turns
> > out to be pretty hard to do in a scripted environment, mostly
> > because package names are not consistent.
> > 
> > 
> > 
> > A few examples:
> > 
> > - packages are names <subsystem>-name-<subcomponent>, but tarballs
> > are names package-<some other
> > stuff>-<subsystem>-<subcomponent>.<packagingmethod>
> > 
> > 
> > 
> > => This means each package to install must be mangled before the
> > tarball can be checked in the manifest file. This is still possible
> > to work around though, if at least all packages followed the same
> > rules.
> > 
> > 
> > 
> > - package gcc-g++ uses tarballs named gcc-c++
> > 
> > 
> > 
> > => So to query if package gcc-g++ is installed I have to write an
> > exception in my query code to search for gcc-c++ instead.
> > 
> > 
> > 
> > At this point I have given up for now.
> > 
> > 
> > 
> > Is there another way I can figure out which packages are installed
> > in a scripted environment ?
> > 
> > 
> > 
> > The mingw-get gui obviously can do it, so the logic is somewhere in
> > mingw-get. How hard would it be to expose similar information on the
> > command line ? For example as extra info in the mingw-get list
> > command ?
> > 
> > Or a separate query command ?
> 
> Hi Geert. I have a script for setting up the building environment for
> Pidgin under Windows. I simply don't care to check if the packages are
> already installed or not, I just install them [1]. If some or all of
> them are already installed, no harm was done. Can't you use this
> approach?
> 
> Otherwise, do you really need a list of installed packages? Since you
> know what specific packages you are interested in, you could use the
> list command including the subcomponent for knowing if the package is
> installed (you need to know which subcomponents you want too).
> Example:
> 
> $ mingw-get show msys-make-bin | grep -E "^(Installed|Repository)
> Version" Installed Version:  make-3.81-3-msys-1.0.13-bin.tar.lzma
> Repository Version: make-3.81-3-msys-1.0.13-bin.tar.lzma
> 
> When the subcomponent is not installed, installed version is none. If
> you still want to list all installed packages, I have another script
> which you may use as inspiration [2]. It searches for packages with a
> provided name, returning an indexed list of matches. You can then
> pass that index for having mingw-get showing information about the
> package. Example:
> 
> $ packages ssl
>   1 msys-libopenssl
>   2 msys-openssl
> 
> $ packages ssl 1 | head -5
> Package: msys-libopenssl                                 Subsystem:
> msys Components: dev, dll
>     dev  is installed: libopenssl-1.0.0-1-msys-1.0.13-dev.tar.lzma
>     dll  is installed: libopenssl-1.0.0-1-msys-1.0.13-dll-100.tar.lzma
> 
> The scripts injects the installed or not information above into the