I've sent the following to Jaap Karssenberg [EMAIL PROTECTED]:
I'd like to propose a new version of File::BaseDir that adds two new
functions.
I've attached a tarball to http://rt.cpan.org/Ticket/Display.html?
id=30138
This proposed version adds two new functions:
xdg_config_resource
* demerphq <[EMAIL PROTECTED]> [2007-10-19 23:10]:
> On 10/19/07, A. Pagaltzis <[EMAIL PROTECTED]> wrote:
> > * demerphq <[EMAIL PROTECTED]> [2007-10-19 18:50]:
> > > How does one use this then? Where is it documented?
> >
> > http://module-build.sourceforge.net/META-spec-blead.html#configure_requi
On 10/19/07, A. Pagaltzis <[EMAIL PROTECTED]> wrote:
> * demerphq <[EMAIL PROTECTED]> [2007-10-19 18:50]:
> > How does one use this then? Where is it documented?
>
> http://module-build.sourceforge.net/META-spec-blead.html#configure_requires
So how do i use this with MakeMaker?
Yves
--
perl -M
* demerphq <[EMAIL PROTECTED]> [2007-10-19 18:50]:
> How does one use this then? Where is it documented?
http://module-build.sourceforge.net/META-spec-blead.html#configure_requires
--
*AUTOLOAD=*_;sub _{s/(.*)::(.*)/print$2,(",$\/"," ")[defined wantarray]/e;$1}
&Just->another->Perl->hack;
#Arist
On Oct 19, 2007, at 9:45 AM, Eric Wilhelm wrote:
See also: the
freedesktop stuff.
http://search.cpan.org/perldoc?File::BaseDir
Thanks, that is useful.
It seems like something like this would be good:
$color_table = File::BaseDir::xdg_config_files('Colors.txt');
what I'd really like is
On Oct 19, 2007, at 9:33 AM, Eric Wilhelm wrote:
my $lookup_tables = {
'LookupTables/Colors.txt' =>
"$support_files_install_dir/Colors.txt",
'LookupTables/Smells.txt' =>
"$support_files_install_dir/Colors.txt",
};
Typo?
Yeah, sorry for the confusion. Sh
On 10/19/07, Eric Wilhelm <[EMAIL PROTECTED]> wrote:
> # from David Cantrell
> # on Friday 19 October 2007 04:00:
>
> >The more alert of you will have noticed that there is a bootstrapping
> >problem in using this from within a Makefile.PL - relax, it will come
> >with a script to bundle itself in
# from Matisse Enzer
# on Friday 19 October 2007 09:21:
>Finally, I am no longer sure it is such a bad thing to have non-
>modules directly in @INC. I am currently undecided about this.
I don't think it is a "bad thing" across the board, but in most cases it
is not a "good thing".
If (and only
# from Matisse Enzer
# on Friday 19 October 2007 09:21:
> my $lookup_tables = {
> 'LookupTables/Colors.txt' =>
> "$support_files_install_dir/Colors.txt",
> 'LookupTables/Smells.txt' =>
> "$support_files_install_dir/Colors.txt",
> };
Typo?
--Eric
--
"Left to thems
# from David Cantrell
# on Friday 19 October 2007 04:00:
>The more alert of you will have noticed that there is a bootstrapping
>problem in using this from within a Makefile.PL - relax, it will come
>with a script to bundle itself in an inc/ directory.
Or use configure_requires.
--Eric
--
perl
On Oct 18, 2007, at 4:28 PM, Jonathan Rockway wrote:
Eric Wilhelm wrote:
If we're voting, I would prefer to avoid having non-modules in @INC.
I agree. How about using Module::Install to install files to a known
location (auto), and then File::ShareDir to get at those files?
I've had more
NB: this has been sent to several mailing lists. Watch those replies!
Dave Golden and I have been hacking on Devel::CheckLib, which should be
on a CPAN mirror near you soon. It's similar to Devel::CheckOS, in that
it will let module authors specify dependencies which aren't just other
perl modul
12 matches
Mail list logo
