Re: real-world example of (smart) developers using PEAR without installation

till wrote: > Hi, > > On 9/6/07, Greg Beaver <greg@chiaraquartet.net> wrote: >> (...) >> However, I suspect that more users needing unzip-and-go will be trying >> out simple packages, and simply recommending that users try the pyrus >> installer (which will not need to be installed in order to work) for any >> complex scenario will help immensely. >> >> My goal - and this may not be clear - is to open up the net we use to >> snare users, and to hook more people into using Pyrus comfortably. I >> recommend the party line if anyone is having trouble managing an >> unzip-and-go is "use the Pyrus installer" >> >> Also, these thoughts are very new, so I would love to know angles or >> solutions I haven't considered or other potholes to navigate. > > I think it would be a great addition to Pyrus if it helps you to > create your own copy of let's say MDB2. > > pyrus make-standalone MDB2 /path/to/your/software/ > pyrus make-standalone MDB2_Driver_Mysqli /path/to/your/software > > Just an idea, but this would copy instances of the packages into > /path/to/your/software and strip it from all docs and examples. Just > the pure class code and needed directories. I was planning to do this exact thing from a different use case perspective and call it "pyrus deploy" with the idea that we can deploy a development environment either to another location on the same machine, or remotely onto a production machine using curl/ftps/some other secure protocol. > Generally - offering a single method would maybe look like a downgrade > on shortsight, but it also provides only one channel to support and > overall less problems that can happen. People who don't want to use > Pyrus probably know enough how a package works to begin with. If I understand what you're saying, I think you're saying simply supporting the install-via-pyrus method when you say single method? If so, I would say that if all that it takes from developers to support other methods is to minimize or eliminate code differences between unzip-and-go and installed-by-pyrus (which means no php_dir/data_dir replacements, and don't use include_path-dependent relative require/include), this is the maximum support one can expect. I do think new users who take the time to come to pear-general to ask for help can be easily referred to "how-to-use-pyrus" docs, which would match what you're suggesting. Greg