>
> Hi Marc,
>
> On 22.04.2010 13:46, heiko.hel...@horiba.com wrote:
> > If you don't mind, I'll try to keep the patch in the bugzilla bug
> > updated with new wpkg revisions.
>
---snip
>
> For sure I fully agree that you can continue to maintain the
> patch and I am even
> thinking about includi
Hi Marc,
On 22.04.2010 13:46, heiko.hel...@horiba.com wrote:
> If you don't mind, I'll try to keep the patch in the bugzilla bug
> updated with new wpkg revisions.
First of all, thank you for your comments. In some aspects you're fully right.
Maybe I am not using MSI packages which take very long
Hello Marc,
Sorry , the patch is "experimental" at best. Use only if you're the
adventurous type (and mail problems with it directly to me). Or better use
one of Rainer's suggestions.
But thanks for getting the discussion started :)
Hello Rainer
Thank you very much for your explanation.
> So
Hi both,
On 22.04.2010 09:55, heiko.hel...@horiba.com wrote:
> This is correct and documented (but i admit a little unexpected) behaviour.
>
> I wrote a patch some time ago that makes this configurable - but since
> there was no reaction, I assumed everybody was okay with the original
> behaviour
Am 22.04.2010 00:21, Brent A Nelson wrote:
I was able to build a 64-bit MSI and send it to the wpkg-gp author,
along with all the quick hacks to the build environment necessary for
the compile. It seems to be working great!
Let me know if you need the 64-bit MSI before it's available at the
auth
Hi all,
at first: I'm very happy with wpkg, it makes my daily work much muc
easier. Thanks a lot for the great work!
One of the packages I deploy via wpkg is the Java Runtime Environment
using the package definition from
http://wpkg.org/Java#JRE_without_Java_Quick_Starter_on_32-bit_hosts
because
Hello Marc,
> Hi guys,
>
> Then I
> ran WPKG again expecting that the checks will be met and the upgrade
> commands wouldn't be run. But the debug output states that the checks
> were not executed and the upgrade commands were run immediately leading
> to the same error again.
>
> Is this the in
Hi guys,
I upgraded one of my packages and saw a behaviour I didn't expect. One
of my users updated "Apple Application Support" himself to a version
newer than I am trying to install. Running the MSI delivered by Safari
installer then exits with error code 1603. Running the MSI in foreground
state
