search for: chocolatey

As some before me on the group, I have a problem getting the Chocolatey provider to work on Windows. I downloaded it from Github and placed it in /etc/puppetlabs/puppet/modules/chocolatey. (I am running Puppet Enterprise 2.7.19). On a Windows 8 client, I have a very simple manifest: class install_notepadplusplus { if $::osfamily == ''windows { $pkg...

Hello, Has anyone here had experience using Puppet (2.7 for now) to install Microsoft Visual Studio 2010 (or even 2012, for that matter) on Windows Server 2008? So far I didn''t find anything on the web, the forge or Github. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop

Hi guys, Currently the windows package provider does not support versions (like ensure => 1.2.3). Even though most packages set a DisplayVersion key in the registry - so the version is often available. Now I need to upgrade my puppet clients from v3.1.1 to v3.2.3-rc1 (to get facts.d support on windows) - and I was wondering if any of you had a suggestion as to how to handle it, until

Hi, I configured puppet open source with the chocolatey module and one windows client. When the puppet agent run as a service (not the interactive version) I can see in the windows event log some errors like Fault bucket 1734820220, type 5 Event name: PowerShell Fault bucket , type 0 Event name: PowerShell I tried to google it but I did not find a...

...ork as expected. As for alternatives, 'rportable' and 'innoextract' have already been mentioned if you really just want to dump the files from the installer, if that works for you. Another popular option to install (any) Windows software without manually running installers is using chocolatey, for example: choco install miktex choco install r.project This will still indirectly use official installers, but the installers have been verified as "safe" by external folks and the installation is completely automated. Perhaps that's another compromise you could live with.

Andrew, This might be offtopic for llvmdev. I suggest the mailing list, cfe-users. > * clang.exe version 3.4 (trunk), from LLVM 3.4.svn How did you build it? clang.exe depends on crt libraries, either mingw32 or msvcrt. Please try (and watch their output); > clang --version > clang -v -O2 -o hello.exe hello.c Please confirm; - Which library did you install? Visual studio or

On Tue, Oct 29, 2019 at 8:40 PM David Blaikie <dblaikie at gmail.com> wrote: > > > > On Tue, Oct 29, 2019 at 10:28 AM Roman Lebedev via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> +1 to bumping cmake version and cleaning build system somewhat. >> >> On Tue, Oct 29, 2019 at 8:23 PM Tom Stellard via llvm-dev >> <llvm-dev at

...for alternatives, 'rportable' and 'innoextract' have already been > mentioned if you really just want to dump the files from the > installer, if that works for you. Another popular option to install > (any) Windows software without manually running installers is using > chocolatey, for example: > > choco install miktex > choco install r.project > > This will still indirectly use official installers, but the installers > have been verified as "safe" by external folks and the installation is > completely automated. Perhaps that's another...

I'm trying to compile hello.c with clang.exe, but I'm getting an error about missing cstdlib headers. Source: https://github.com/mcandre/mcandre/tree/master/c/hello/ Trace: C:\Users\andrew\Desktop\src\mcandre\c\hello>gmake clang -O2 -Wall -Wextra -Wmost -Weverything -o hello hello.c hello.c:1:10: fatal error: 'stdio.h' file not found #include <stdio.h> ^ 1

> On Jun 3, 2019, at 4:40 PM, Abby Spurdle <spurdle.a at gmail.com> wrote: > >> If you go here: >> https://cran.cnr.berkeley.edu/bin/windows/base >> you see EXE installers for Windows. This contrasts with other programming >> languages that offer both an executable installer and ZIP files that can > be >> extracted and run > > Are you suggesting