> 2. In which places of the codebase this installation directory is > needed and can't be worked around? > > We have writing the pid, use lib, some files for VDD generator for > example and so on. The pid could be written to %TEMP%\SCMBug\PID in my > oppinion, the lib-path of SCMBug could be added to Windows-PATH due to
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.
> an installation. Wouldn't use lib even work with relative paths?
> Something like use lib "../share/scmbug/lib/"; instead of use lib
> "C:/Programme/Scmbug/share/scmbug/lib/"; in
With relative paths it could break if a user calls the glue installer
outside %ProgramFiles%/Scmbug e.g from C:\
> SCMBug/bin/scmbug_install_glue.pl. At my company we use a perl package
> setting library paths for perl modules which will be included in every
> .pl-files BEGIN-statement and reads a configuration file in the same
> directory where include-directories are specified. This could be
see previous comment.
> generated by the installer, I think, by using "echo" at the command
> line maybe.
>
> $arguments->{ stylesheet_file } = "C:/Program
> Files/Scmbug/share/scmbug/glue/templates/stylesheets/vdd.xsl";
>
> Could code like this be changed to use a configuration setting or some
> kind of environment variable?
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.
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%.
> 3. Identifying any other places needing this installation directory
> for proper working.
>
> I did never use the SCMBug-installation mechanism for glues, what
> information is needed for this to work? It needs the perl-installation
> directory in the hooks templates which could be read from registry
> with the installer, I think. Should the hooks be generated along with
> the installation directory in some kind of way, maybe just be echo'ing
> the content to a file using pipes?
>
> > I have so far refused to expect from the user to execute a .bat file
> > that will take care of this.
>
> Bugzilla comes with checksetup.pl and it seems to work... Though, I
> like just decompressing a zip or checking out from version control and
> let TextPad do the rest.
Sometimes users don't run it. Then, they ask for help in the mailing
lists.
> > I'd rather we had a proper installer that
> > can be built under Linux.
>
> 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.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ scmbug-users mailing list [email protected] http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
