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

On 9/7/07, Gregory Beaver <greg@chiaraquartet.net> wrote: > till wrote: > > (...) > > 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. Deploy works for me as well. ;-) I think "urls" might work best here - file://, http:// (webdav), ftp:// ... ? That's a great idea. Maybe if file:// is omitted it uses a local path. > > 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? Correct, that's what I meant. > 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. Well - for unzip and go freaks, there are still many useless (we all know that they are not useless ;-)) files in the tar. So what I mean is, I don't know if the data_dir is really *the* obstacle here. Infect, I don't remember the last time I came across that. Maybe offer stripped down tar's to download for the impatient^H^H^H^unzip and go people? Till