RE: [PEAR-DEV] Creating a PEAR repository

Hello Arnaud, thanks for your reply > Hello, > > This sounds great for PEAR, i like the idea ;) [Neo] Yes to us too, you see the current distribution is made of 46 modules and there are hundreds of external modules that could be handled by this and make the life's or users, devs and the community in general much easier, as well as lower support issues :) > A question though, what do you mean by "does pear provides stats ?", if i > understand well pear has download stats for packages but i'm not sure that > is what you mean. Could you be more specific about it ? [Neo] Sure I meant exactly that if PEAR had any downloads stats or any other included, for instance users submitting packages and that sort of reports, no big deal since they can always be added, but are quite important for us, I have checkout some modules from CVS and browse them briefly so far I gather the pearweb includes the classes that actually package and read the XML metadata in order to enter them into the database and monitor, process, still need to dig deeper, sadly so far I have not found, any documentation at all. In regards to the repository creation. Any pointer here would be great. > Again if i understand well it looks like pear would be perfect to > distribute the components. > > Regards, > > Arnaud. > [Neo] Yes indeed, just hope to find my way around meeting it up first, creating the metadata file in xml for each package is really no big deal and can also be automated, I guess what I am looking for is to get a clearer picture in how to build the repository and how does the actual process of retrieval and installation is performed in order to find the best way to integrate this into our own installer. We are all looking forward to start working in this as soon as possible and start alpha testing ;) Thanks so much in advanced for any guidance on this topics. Best Regards Cheers Sam Postnuke Development Team http://www.postnuke.com/