Re: Bootstrapping PEAR for distros

Justin Patrin wrote:

go-pear *can* work offline, IIRC. I think that you can pre-download the packages and have it use those instead of going online. This way you can specify what versions you want to use and not go online. I believe that go-pear supports a non-interactive mode, but I could be mistaken.

OK thanks. Well, Greg's solution an up-to-date PHAR seems good, but I'll bear that in mind for the future.

I have many things I would say here, but if PEAR_Command_Packaging is doing the RPM creation then, as long as that code is written well, things should be ok.

I don't make any great claims; the majority of it was written by Greg, has been in pear core for years (before forking) and has been used by many people on many packages.

Basically what I'm worried about is converting depdendencies to new formats (esp. if by hand) and installer tasks. PEAR has built-in support for doing pre/post install tasks as well as replacements of special tokens in source files. If these steps are skipped in your non-PEAR installer then things are going to break.

As I posted earlier, PEAR is typically called by RPMified PEAR packages on install/uninstall. If "pear [un]install --register-only" runs the package's own install/uninstall scripts (I'm not sure offhand) then it should be fine. If it doesn't, then there might be a problem that needs looking into. Have you got a good sample package in mind that I could use to test? Thanks Tim