ioncube loader

[pepedog]

Sorry, I corrected it in my post
makepkg -g --asroot
That generated mdsums to goes into PKGBUILD, but it's on screen
>> this redirects output
So putting it together, this generated the mdsum part and appends it to PKGBUILD
makepkg -g --asroot >> PKGBUILD

[capchap]

OK, great, I'll try it.

[capchap]

WOW!!!!!!!
I am impressed.

I ran it as trial run, gave me a screen full of data statistics that updated until completed, then appended the checksum stuff to the trialrun file.
AND it downloded:
-> Downloading php-5.3.28.tar.gz.asc...
and reported:
-> Found php.ini.patch
-> Found apache.conf
-> Found php-fpm.conf.in.patch
-> Found logrotate.d.php-fpm
-> Found php-fpm.service
-> Found php-fpm.tmpfiles
==> Generating checksums for source files...
not sure what it did with them

before the command
$this->bbcode_second_pass_code('', '[root@Jalepeno php]# ls
PKGBUILD logrotate.d.php-fpm php-fpm.install php-fpm.tmpfiles
apache.conf php-fpm.conf.in.patch php-fpm.service php.ini.patch')
after the command:
$this->bbcode_second_pass_code('', '[root@Jalepeno php]# ls
PKGBUILD php-5.3.28.tar.gz php-fpm.install php.ini.patch
apache.conf php-5.3.28.tar.gz.asc php-fpm.service src
logrotate.d.php-fpm php-fpm.conf.in.patch php-fpm.tmpfiles trialrun
')
So, even though I ran it with trialrun instead of PKGBUILD
I think it still worked and all I have to do is append contents of trialrun to PKGBUILD
$this->bbcode_second_pass_code('', 'cat trialrun >> PKGBUILD')
then I could just proceed with your next command
$this->bbcode_second_pass_code('', 'makepkg -Acs --asroot')
correct?

man makepkg says:
The advantage to a script-based build is that the work is only done once. Once you
have the build script for a package, makepkg will do the rest: download and validate
source files, check dependencies, configure the build-time settings, build the
package, install the package into a temporary root, make customizations, generate
meta-info, and package the whole thing up for pacman to use.
but when I ran the command I received the following request:
:: Proceed with installation? [Y/n]

I told it no.
is this just a generic question because thats what it does even though it is not 'installing' anything...
after it said:
synchronizing filesystem...
==> ERROR: 'pacman' failed to install missing dependencies.
so was it going to install or not?

[capchap]

ran the command
nunch of processing, but one concerns me:
Verifying source file signatures with gpg...
php-5.3.28.tar.gz ... FAILED (unknown public key 2F7956BC5DA04B5D)
==> WARNING: Warnings have occurred while verifying the signatures.
Please make sure you really trust them.

how do I find out where it came from?
I think I remember seeing something in the PKGBUILD that got it from php
if so, I guess I should trust it????

[capchap]

here is something a bit more serious...

patching file php.ini-production
Hunk #1 succeeded at 376 (offset 80 lines).
Hunk #2 succeeded at 793 (offset 100 lines).
Hunk #3 succeeded at 816 (offset 100 lines).
Hunk #4 FAILED at 854.
1 out of 4 hunks FAILED -- saving rejects to file php.ini-production.rej
==> ERROR: A failure occurred in prepare().
Aborting...

what is the recovery/fix for a failed hunk?

[pepedog]

1/ it wanted to install stuff to build, makedepends
2/ you have 2 lots of md5sums, you -g generated them an appended at the bottom, the bottom one takes president
3/ in the upper one there is a SKIP, edit bottom one so it has skip in same place.
4/ don't trial run
5/ delete src directory before trying again

[capchap]

found a brief description at
http://elinux.org/Handling_Patch_Rejects

$this->bbcode_second_pass_quote('', '
')You'll need to check the .rej files it creates. Those chuncks of code
were not merged into the target files, so you'll need to edit the
targets and edit them accordingly, i.e. make the sense of the changes
and add the lines preceding with + and remove the ones starting with -.
Those who do not have one of those preceding characters are meant for
context guidance and are not to be changed.
More info here

[capchap]

ok, I edited php.ini-production to address the +- mods required by makepkg, but this into'd a small concern.
the are commented out, but the .rej file left 3 lines out that probably should have been deleted:
;extension=php_pdo_mssql.dll
;extension=php_sqlite.dll
;extension=php_zip.dll
they are commented so no harm...unless I forget later and try to enable them inadvertently.
So, I'm going to remove them anyway.
these are the only .dll lines left in the file and instructions clearly say .dll extension is for windows.

so now that I have edited the production file, what do I do next?
Do I have to downgrade other packages as well or will pacman fix them when I install this package?
is there anything I need to be aware of?

[moonman]

Don't bother. I tried compiling it, it won't. I fixed first problem with freetype, but then there was another one with ssl and then I am sure there will be tons more. It's too old.

[capchap]

thats dissappointing.
how do I put my ABS back so it matches my current environ?
just put 5.5.15 back in the PKGBUILD and run makepkg again?
or is there a simpler way?

lastly, so I am still in situation with ioncube loader not being able to run under 5.5.15. is there any way the dev-team could compile a version of ioncube loader that will work, or am I on my own with that?