Skip Menu |

This queue is for tickets about the CPAN CPAN distribution.

Report information
The Basics
Id: 30449
Status: resolved
Priority: 0/
Queue: CPAN

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Wishlist
Broken in: 1.9203
Fixed in: (no value)



Subject: Add is_interactive flag to distroprefs
It would be nice to have an is_interactive flag for the three distroprefs phases pl, make, and test. I don't expect an implementation for this flag (yet). But there could be need for such a flag, for example, to let automated installers skip building a distribution flagged like this, and let human installers do the job later. (Note that not everything can be handled by Expect, like GUI tests. Which leads to a new idea: add support for X11::GUITest and Win32::GuiTest :-)
A field in a spec that does not define what it is doing? A field for private use that we promise we will never use? Looks like you want a private field so that you can use the distroprefs files in other context? If so, we need a field where other users of distroprefs files can put their act together, right? Please elaborate if I misunderstand you.
Subject: Re: [rt.cpan.org #30449] Add is_interactive flag to distroprefs
Date: 06 Nov 2007 00:00:34 +0100
To: bug-CPAN [...] rt.cpan.org
From: Slaven Rezic <slaven [...] rezic.de>
"Andreas Koenig via RT" <bug-CPAN@rt.cpan.org> writes: Show quoted text
> <URL: http://rt.cpan.org/Ticket/Display.html?id=30449 > > > A field in a spec that does not define what it is doing? A field for > private use that we promise we will never use? Looks like you want a > private field so that you can use the distroprefs files in other context? > > If so, we need a field where other users of distroprefs files can put > their act together, right? > > Please elaborate if I misunderstand you. >
I thought of an "official" field which might be used by CPAN.pm in a future version. A small sketch: distropref defines: match: distribution: Foo is_interactive: 1 CPAN.pm configuration specifies: o conf skip_interactive 1 Which means that the distribution Foo won't be build with this setting. The user could decide to change the flag later to install the distributions which are interactive. But it would also be quite OK to have a general-purpose field for user-defined data (and a "=" in the Kwalify schema to accept all keys). Then just document how a user could use just the distroprefs matching in CPAN.pm for his own scripts and the wishlist item could go into a separate module or script. -- Slaven Rezic - slaven <at> rezic <dot> de tkrevdiff - graphical display of diffs between revisions (RCS, CVS or SVN) http://ptktools.sourceforge.net/#tkrevdiff
I think this can be implemented in terms of the "env" match (see #34104). So no need for actions left. Regards, Slaven