Re: Re: php, pear and rpm

On Fri, 2 Aug 2002, Tomas V.V.Cox wrote: > > Since rpm-4.1 (next version) there will be in official rpm script to > > generate dependencies in pear packages, which I made for PLD. > You coded our xml dependencies format in C for RPM? :-O no, I didn't needed to do that :) rpm allows to run external scripts to find dependencies. Take a look at this scripts. One finds what is provided by file, second finds what is required. Script is not very nice - needs a lot of fixes, for sure. But works really nice. Every class that my clients use are working without any troubles. > > This is just information - other linux distributions will be more > > interested in the future in regular and good made tgz packages. > I agree that it's a problem to have different installed package > databases, but we really encourage distrib packagers to use the pear > script or at least the php4/pear/PEAR/* libs for it. sure - I will if there will be replacement for attached script :) I would really like to have all needed functions in some pear class. This would be really great. Now package.xml have non-automatic dependencies. This is not good, many things are missing (I'll prepare such a list in a near future, when I'll have some free time). > If you are not fast enough to create RPMs, a user could have the problem > that need to install a package that depends on others and the pear > command will not find the right directories/dependencies. This is users choice. And user has to solve it. We will not suply 2 databases for sure. Never. None distro will... PLD is very fast in making packages :] > Your work could be so easy as just: > 1) All Pear packages depends on the php-cli/php package what for? If it will not suply functions helpfull in making dependencies I will not make this dependency. I don't need it now. > 2) All Pear packages depends on the PEAR package (at installation time > you could set the target dirs: php_dir, doc_dir, bin_dir, etc according > to the distrib layout) This is done by rpm-macros. > 3) The RPM package should only contain the sources from the tgz (or a > tar if you consider CPIO enough :-) downloaded from the web and in the > .spec just a "pear install -s package.(xml|tar)" look above :) We don't want second database. to use that we need few things: 1. skip all pear-packages-database things. This is not needed 2. install without dependencies. Every rpm-package is build on builder which does not need to have installed pear packages (what for? only to make package?) 3. override in install all the pear variables - php_dir, doc_dir, bin_dir some of this is done. > If you need to get some data from packages (list, dependencies, info, > etc) we are open to create some exchange xml format. Please let us know > what other problem you've found building RPMs for Pear packages. well... look at example spec from PLD. This would give you some insight in ours needs. > > There is one thing with that connected. Why all packages with classes > > are avaible only via http with some redirects? They should be avaible > > on some http or ftp which is browsable. This might be very helpfull in > > automatic notification about new releases. > Take a look at our RSS: http://pear.php.net/rss.php It's not what I need. We've got script that checks _all_ packages we have on our repository. It looks for addresses, seek directories for newest package and reports if it's newest or not. Sure, now I'm taking care of whole pear in our distro, but when I'll have vacations someone else from PLD will try to upgrade. And this script is really helpfull. Tell me - why not to expose it on some ftp or browseable http? -- --------------------------------- pozdr. Paweł Gołaszewski --------------------------------- CPU not found - software emulation...