Guten Tag Kristis Makris,
am Sonntag, 16. Dezember 2007 um 05:47 schrieben Sie:
> We could use %ProgramFiles%\Scmbug\... for all this, assuming it will
> work within Perl. Else we'll need to extract %ProgramFiles% from the
> environment within Perl.
"%ProgramFiles%\Scmbug\..." won't work, but using
"$ENV{'someVariable'}" will do fine.
> We will need to "wrap" the binaries, e.g. glue_installer.pl with .bat
> files that will call perl -L%ProgramFiles%/Scmbug/lib <toolname> and
> change glue_installer.pl to not 'use lib "absolute_path";' but instead
> 'use packagename::only;'. We will have two "binaries" to maintain. The
> real one, and the wrapper. And will need to follow this scheme for
> future binaries.
Maybe I did understand you wrong but I don't think this would be
necessary according to what I tested now.
> Also we'll need to call the absolute path for perl for svn on Windows,
> since there's no %PERL% variable, or might not be, or Perl might not be
> in the %PATH%.
I didn't understand that, what's "perl for svn"? Do you mean the path
to Perl's Binary in the hook-templates?
>> Is this necessary? Windows software should use MSI, in my oppinion,
> Yes this is necessary. Otherwise releases won't be automated. Linux is
> the release platform.
Is anyone aware of a comfortable cross-platform installer? I just know
InstallAnywhere using Java, but even this comes with an exe for
Windows and I think the whole thing is crap. I always got problems
with those installers and different versions of Java, no Java at all
and all that stuff.
I don't think we want to write our own tool installing SCMBug.
Here's what I did for my old SCMBug installation version 0.19.9:
I created the environment variable SCMBUG_HOME pointing to the
installation directory. This variable could be created during a
MSI-installation with the path the user entered. Every file using an
absolute Windows path was changed using $ENV{'SCMBUG_HOME'} now, I had
to change some expressions from something like '...' to "..." to get
this to work.
One down, one to go: Perl and the hooks. At least with my versions of
ActiveState Perl there is a key in the Windows registry under
HKLM\Software\Perl where one could get the home- and bin-dir. Using
MSI we could read the (default)-key with Perls installation directory,
create a environment variable and use that instead of an absolute path
in the hook-templates.
With those changes we could freely let the user decide where to
install SCMBug, the installer would create the necessary environment
variables. If one doesn't want to use the installer, he could
uncompress/checkout the SCMBug-directory where ever he wants and
should only create the needed anvironment variables himself. That's
nothing horrible for those interested in SCMBug, I think.
What do you think?
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning
AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig
Telefon: Potsdam: 0331-743881-0
E-Mail: [EMAIL PROTECTED]
Web: http://www.am-soft.de
AM-SoFT Potsdam GmbH, Konsumhof 1-5, 14482 Potsdam
Amtsgericht Potsdam HRB 12480, Geschäftsführer Andreas Muchow
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
