Re: [PHP4BETA] php and MS SQL Server....

Hello Stig, On 01-Mar-00 18:38:26, you wrote: >> >> Anyway, the truth is that I see a large overlap not only on Stig's >> >> effort to bring up an official database abstraction layer, but also to >> >> the whole PEAR project. Think about it how many code repositories like >> >> CPAN you know for PHP. I know David Sklar's PX for generic code, Boaz >> >> WeberDev for example code, I have developed PHP Classes repository for >> >> PHP objects, there are certainly others that I'm sorry to not recall >> >> right now. So why another code repository? >> >> >That is exactly the reason. There are too many of them out there and we >> >need a single well-managed one with an established development framework >> >around it. ie. one where all changes are logged in CVS and bugs can be >> >> CVS? Why? AFAIK CPAN does not require contributors to put their code >> under a CPAN managed CVS repository and I don't see a reason to have one. >> >> I'm afraid that if you are requiring contributors to put their code in your >> CVS repository, you are automatocally discarding many potential >> contributors that a) don't know CVS and don't want to learn it to be able >> to contribute b) already have their own CVS repository and don't want to >> have somebody else to take over it. >> >> Unless you mean to put only PHP code of core developers in the PEAR, I >> don't see much point in putting contributors code in a CVS repository. >> A simple upload form would be much simpler and would leave out many of >> the potential contributors as you only need a Web browser, not a properly >> set CVS client. >We are not going to force people to put their things in the php4 CVS No? If you are the one in charge of the plans for PEAR, you should know better, but if I got it right, what you said contradicts what Rasmus said. >repository. Right now this is the way it is done, true, but it won't be >this way for long. We are going the CPAN route and letting people >distribute their packages from whatever site they like, but at the same >time we will be offering a central place where you can find/download >them, a set of rules/guidelines for quality and consistency and an index >so there will hopefully not be too many wheel re-inventions. The only new thing I see there is code approval which I'm afraid will leave many contributors out, being that a good or a bad thing. Other than that we already have several central places with code repositories with slightly different scopes. >> Wouldn't it be more objective to first approach the authors of the existing >> PHP repositories and suggest the necessary improvements? I have been >> getting many improvement suggestions and as time as allowed I have been >> implementing many of the good ideas that have been passed to me. >I think what Rasmus means is that the fact that there are a gazillion >repositories out there makes it chaotic, as well as the fact that a lot Actually it didn't sound like he meant the number of existing code repositories is chaotic. He said the code repositories out there *ARE* chaotic. To me it sounded very arrogant in the sense that it seemed he was saying that only PEAR won't be chaotic and all the rest is so useless that there is really a need to do PEAR even if that means redoing everything. Maybe he didn't mean that way, but that's what I understood. I feel this totally unfair, if Rasmus doesn't want to use the code in the existing repositories, fine with me, but passing an incompetence certificate this way to all the developers of these repositories doesn't sound very constructive, especially when it comes from the mentor of PHP. >of them are not well organized (I'm pretty sure he wasn't talking about I suspected that he never entered in mine to start with so he could appreciate instead of put all of us down. >yours in particular) and many only give you the code in "display source" >format, which means you have to cut and paste from your browser. That >is not how I want to install software on my systems. Some do, but for instance in mine you may get the code the way you like. Code is gathered in packages of individual files and if you prefer to download it, you may even choose to download them in either .tar.gz or .zip formats. >Now compare that to what CPAN offers: >* a nice set of tools for configuring builds, installing, uninstalling >etc. >* an organized package name space >* rules for coders to give better consistency and robustness >* dependencies between packages >* an index of package names and what they provide >* download mirrors >In the light of this comparison, I definitely think the description >"chaotic" fits the current state PHP viewed as a whole when it comes to >code repositories. So, you decide it is best to scrap everybody else's effort doing your own instead of reusing each other's efforts. Never mind. This seems to be a pretty much decided issue between yourselves. Go ahead. Regards, Manuel Lemos Web Programming Components using PHP Classes. Look at: http://phpclasses.UpperDesign.com/?user=mlemos@acm.org -- E-mail: mlemos@acm.org URL: http://www.mlemos.e-na.net/ PGP key: http://www.mlemos.e-na.net/ManuelLemos.pgp --