Le 18/07/2012 08:38, Tomás Abad a écrit :
Hello Guillaume,
On Wed, Jul 18, 2012 at 8:06 AM, Guillaume Rousse
<[email protected]> wrote:
Le 18/07/2012 01:25, Tomás Abad a écrit :
d) Is there any problem if I make use of Strawberry Perl May 2012
v5.16.0.1 32bits to build an installer for Microsoft Windows
32bits platforms and Strawberry Perl May 2012 v5.16.0.1 64bits to
build another installer for Microsoft Windows 64bits platforms?
The 64bits version of the agent is unlikely to works out-of-the box,
mainly because of registry issues, but that's the way to go IMHO.
I'll try to do only a FusionInventory Agent installer for both
platforms. The installer will install Perl 32 bits or 64 bits based on the
target Windows platform.
Distinct 32 and 64 bits installers would avoid having to download a bloated
binary, where only half of the payload would be used in any scenario...
You are right Guillaume but, in this case, the increase in size of
the installer can be, as much, of 80 MBytes (without take into account
any compression). These increase is not so much and allows a better
and easy management and use, I think.
A +100% size increase is not something I'd call 'not so much',
especially for automated deployment scenario.
And beyond technical issues, the choice of which architecture to use
should be left to end user, instead of being hardcoded in a piece of
code. We're targeting sysadmins, not your (or my) grandmother, meaning
people supposed knowledgful enough to make the decision that fit their
need. Including installing the 32bits version on 64bits platform, for
whatever reason, if needed.
--
BOFH excuse #35:
working as designed
_______________________________________________
Fusioninventory-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/fusioninventory-devel
