Ticket #399 (assigned defect)

Opened 5 years ago

Last modified 3 years ago

Stand-alone executabel of Padre for Linux

Reported by: szabgab Owned by: Alias
Priority: major Milestone:
Component: downstream Version: 0.36
Keywords: Cc:

Description

ORLite::Migrate::Patch was missing from the PAR generated executable but now it is added.
Still when ORLite::Migrate is running the migration scripts it does so via IPC::Run3 which uses the system perl and not the perl that comes with padre. That might not work as they might not be binary compatible.

One thing I tried was to add the lib directory that comes with padre.exe with the following naive code in Padre::DB

BEGIN {
	if ($ENV{PAR_TEMP}) {
	 	$ENV{PERL5LIB} .= ":$ENV{PAR_TEMP}/inc/lib";
	}
}

That gave me

install_driver(SQLite) failed: DBD::SQLite object version 1.14 does not match bootstrap parameter 1.23 at DynaLoader.pm line 219, <STDIN> line 1.

probably if I add it as the first thing to PERL5LIB that would work on my computer but not on other computers with other version of perl.

Change History

comment:1 Changed 5 years ago by szabgab

The problem is that PAR does not expose a perl executable and ORLite::Migrate wants to run its migration scripts as external scripts. The system Perl cannot be used to execute the migration scripts as it might be different version and it does not have some of the modules. (and in the longer run there might not be a system perl)

So until either PAR can expose a perl executable or ORLite::Migrate can run the migrations scripts in the same process or until someone comes up with some clever idea we cannot use PAR to generate
stand-alone executables for Padre.

comment:2 Changed 5 years ago by szabgab

  • Component changed from editor to downstream

comment:3 Changed 3 years ago by bowtie

  • Owner set to Alias
  • Status changed from new to assigned

Can this now be closed

Note: See TracTickets for help on using tickets.