Re: Re: Pkg

From: Date: Wed, 11 Sep 2002 07:17:55 +0000
Subject: Re: Re: Pkg
References: 1 2 3  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-9012@lists.php.net to get a copy of this message
On Tue, 2002-09-10 at 13:07, Blues wrote: > On 10 Sep 2002, Stig S. Bakken wrote: > > The PEAR installer was written with RPM and other packaging systems in > > mind. You can create an RPM package where RPM installs all the files, > > and in the "post" RPM script run "pear install -r package.xml" to > > register the package as installed (and likewise "pear uninstall -r > > Package" in "postun"). > > If someone wants rpms - please take it from PLD: > ftp://ftp.pld.org.pl/PLD-1.0/i686/PLD/RPMS/php-pear-* > > These are noarch, so it will be no problem to install on other systems. > There are dependencies autogenerated. It really works. > > > When using CPAN on RedHat boxes, I often don't bother getting the RH > > packages for CPAN stuff, but use the CPAN installer directly instead. > > This isn't a very good solution though, and IMHO PEAR should play nice > > with other package systems. > > sure. > > > For people who want to make sure all their packages are maintained > > through RPM (or another system such as APT or PKG), it could be > > interesting to add a config parameter that requires that the > > -r/--register-only option is used during install. For example: > > > > mybox$ pear config-set package_manager rpm > > mybox$ pear install Foo > > pear: This PEAR installation is managed through the external package > > manager "rpm". 'register-only' option is required. > > > > If the -r/--register-only option is used, the install command goes > > through. > > If someone wants to use pear packages database what for does he need take > packages from rpm? > Thats why in my packages I'm not using pear installation. > > > This is just to remind forgetful or unknowing users that an external > > package manager is wanted. I guess there should be an option to > > override if a package really, really has to be upgraded and there is no > > RPM yet (--force or --no-package-manager). > > There is one thing missing for me in pear. > > pear --show-deps package.xml > pear --show-provides package.xml > > That will _generate_ what classes provides that package and what classes > are needed by this. > Now this things are written manually and this is not good. > > I have shell script that makes such a things, but this should written in > php and incorporated with pear command. :) The foundation for --show-deps and --show-provides is in place (check out the PEAR_Common:analyzeSourceCode() and PEAR_Common::detectDependencies() methods, both require the tokenizer extension. - Stig -- Stig Sæther Bakken, Fast Search & Transfer ASA, Trondheim, Norway http://pear.php.net/wishlist.php/ssb

« previous php.pear.dev (#9012) next »