Even though it's bad, there's still occasions when the module cannot be
installed at all without user input, or OPTIONAL input can be used to
enhance the installation process.
It is wroth keeping for these cases.
On 08/09/2007, via RT <bug-Module-Install@rt.cpan.org> wrote:
Show quoted text>
>
> Queue: Module-Install
> Ticket <URL:
http://rt.cpan.org/Ticket/Display.html?id=29216 >
>
> That does seem like it might be better (the linking to deeper, common
> installation). Do you plan on removing the current prompt_script
> function in future versions?
>
> On Fri Sep 07 03:12:17 2007, adamkennedybackup@gmail.com wrote:
> > Anything that asks the user for information is inherently wrong.
> >
> > Personally, I would install the CGI application to the system
> directories
> > and then add a seperate little setup tool to copy/link the
> script/modules
> > into the CGI directory.
> >
> > That way you can even run it multiple times to install it to multiple
> > places.
> >
> > Adam K
> >
> > On 07/09/07, via RT <bug-Module-Install@rt.cpan.org> wrote:
> > >
> > >
> > > Fri Sep 07 00:53:02 2007: Request 29216 was acted upon.
> > > Transaction: Ticket created by ASHLEY
> > > Queue: Module-Install
> > > Subject: Feature request: some kind of prompt_script which asks
> for
> > > PATH
> > > Broken in: (no value)
> > > Severity: Wishlist
> > > Owner: Nobody
> > > Requestors: ASHLEY@cpan.org
> > > Status: new
> > > Ticket <URL:
http://rt.cpan.org/Ticket/Display.html?id=29216 >
> > >
> > >
> > > I would love to use Module::Install for distributing small web apps
> and
> > > CGIs. If it could prompt for the path to place the script, it would be
> > > perfect for this as well as modules. Perhaps nice if there were just a
> > > general mechanism for prompts?
> > >
> > > If this is already in there somehow and just not on the top of the
> docs,
> > > I apologize. I'd love to see it in the POD if it does already exist.
> > >
> > > Thank you for the great stuff already here!
> > >
> > > -Ashley
> > >
> > >
>
>
>
>
