On Thu, Jul 28, 2011 at 4:29 PM, Torsten Bergmann
<astares@gmx.de> wrote:
OK, thanks for the pointer to
https://pharo-ic.lille.inria.fr/hudson/view/Cog/job/Cog-Win32/
Still this one is not yet customized to use the "lighthouse and gear"
icon. It also does not include a resource section - so one can find
out the vendor and version easily using explorer directly on the EXE's
properties.
Any admin would be suspicious if he would find an EXE on a hard disk
that does not include the vendor and product name. This info is
also used when the firewall pops up as soon as you have a Seaside
app running that requests network access. With this (not yet branded)
VM the info would be empty...
I can provide the necessary info/files for that, so we can include them
into the auto build. This is easy to change.
But still I dont know what the codebase of this auto build Cog VM
for windows is. Is it the Subversion repo from Eliot or the
Git clone from Igor?
If it is the git one how does it relate to Eliots work, for instance
is the IAB32 and MT stuff already part of it as in #r2474?
Is it auto-merged or who is in charge of merging things into it?
I know this could end up in a discussion about Pharo forking and
personal working styles - but nonetheless I'm eager to know more
about all these (now distributed?) work being done.
Esteban wrote:
> let me guess... why can that be happening... oh, I know: you are using
> windows!
Anything I can answer here is that Windows is one of the relevant
parts of the IT market - if we want Pharo to be successfull in
commercial environments we should help developers/pharo users to
easily feel comfortable in these environments and help their
customers on ANY platform - including Windows. So your comment
didnt help to make the situation better, did it?
Nothing more to add.
Thx
T.
--
Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir
belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de