Re: Re: (Fwd) RE : [PEAR] How to install all downloaded packages in on
| From: | Stefan Neufeind | Date: | Sat, 10 Apr 2004 15:30:47 +0000 |
| Subject: | Re: Re: (Fwd) RE : [PEAR] How to install all downloaded packages in on | ||
| References: | 1 | Groups: | php.pear.core |
| Request: | Send a blank email to pear-core+get-260@lists.php.net to get a copy of this message | ||
On 10 Apr 2004 at 11:23, Greg Beaver wrote:
> Stefan Neufeind wrote:
>
> >Hi Gelin, this mail goes out to Greg, since he is far more competent
> >regarding the installer :-))
> >
> >
> >Hi Greg,
> >
> >have there been thoughts about something like this? It looks normal
> >to try something like this (or try *.tgz or things like that) -
> >however it only works when you
> >
> >pear install
ls *.tgz
> >
> >or tricks like that?
> >
> > Stefan
> >
> >------- Forwarded message follows -------
> >Subject: RE : [PEAR] How to install all downloaded packages in one shoot
> >Date sent: Fri, 9 Apr 2004 22:05:36 +0200
> >From: "Gelin Patrick" <Patrick.Gelin@rpn.ch>
> >To: "Stefan Neufeind" <stefan@neufeind.net>
> >
> >I'm using Windows 2000 server. I would like a script to install for example, all HTML
> >packages like this:
> >
> >pear install HTML*
> >
> >is it possible?
> >
> It's an interesting and risky idea - I guess we could add an optional
> parameter to pear search like so
>
> pear search --forinstall HTML
>
> This would return a space-separated list of package names, and so could
> be passed in like this:
>
> pear install < pear search --forinstall HTML
>
> I would prefer to implement it in this manner as you could run the pear
> search command prior to the pear install command. Otherwise, there is
> too much risk of something going haywire.
>
> Otherwise, it would be conceivable to implement wildcards at the server
> level, something that would replace "package = packagename" with
> "package LIKE packagename%" but I think this is risky
>
> If it were implemented, I would make a required param like so:
>
> pear install --withwildcards HTML*
>
> Thoughts?
Hmm, well you gave me again enough for some thouhgts on the topic. I
didn't expect the installer to pull HTML* from the server :-)) I was
mainly focusing on the local installation part - so you can install
*.tgz or HTML_*.tgz or similar, that you have downloaded before
(possibly with a download-all or similar).
Would the wildcard-installation from the server be really useful? I
mean, technically it's possible - but would it be used? Then we could
even think about adding a --interactive.to enable processing of a
search-result:
pear search --interactive HTML
=>
1. HTML_Progress
2. HTML_Table
...
What do you want to install? (choose the number(s) or enter * for
all).
Would that be an option? However, it's a completely different
approach that would possibly need a lot of more work - I know!
Regards,
Stefan