AM 2.) the PEAR-Installer create a package file of the 'your'
AM format from the XML package file
maybe would be better. Let's see what other people think.
I forgot a possiblity, one task of the installer should be to
store data of the
installed pear-packages in flat-file database. This
I definitely agree that this would be a cool thing to have. Today PEAR
packages do all of this with PHP code, a more tightly integrated package
concept would be very nice. Comments below.
Stanislav Malyshev wrote:
Below is the proposal for PHP packaging extension. The intentions is for
PHP
PEAR has already a XML-based package file format, which is already used
for installation and information retrieving.
Is it documented somewhere?
Also, I fear that XML would be too slow for time-critical operation like
including files on runtime, but I might be mistaken.
--
Stanislav Malyshev,
Is it documented somewhere?
The DTD is in php4/pear/package.dtd
Also, I fear that XML would be too slow for time-critical operation like
including files on runtime, but I might be mistaken.
Could be possible.
Solutions:
1.) creating a c-function, which parses the xml-file
2.) the
AM Also, I fear that XML would be too slow for time-critical operation like
AM including files on runtime, but I might be mistaken.
AM Could be possible.
AM Solutions:
AM 1.) creating a c-function, which parses the xml-file
The problem is that I do not want to create dependency on any XML
AM 2.) the PEAR-Installer create a package file of the 'your'
AM format from the XML package file
maybe would be better. Let's see what other people think.
I forgot a possiblity, one task of the installer should be to store data of the
installed pear-packages in flat-file database. This is'nt
package_load(Name)
package_is_loaded(Name)
package_set_path(path)
+1
3. The package definition file has format like the following:
PEAR has already a XML-based package file format, which is already used
for installation and information retrieving.
--
PHP Development Mailing List
