> =head1 DESCRIPTION
>
> Many other programs have so called "resource configuration" files (at
> least that's what I call them) that are loaded and interpretted upon
> program startup. Some example programs that have this ability include
> bash, mutt, and python. Perl should do the same.
>
> A C</etc/perlrc> file could be used to set system-wide defaults that
> the system administrator would like to promote. For instance,
> C</etc/perlrc> could turn on stricture or warnings.
>
> This RFC proposes that Perl 6 support 2 "rc" files: a per-user file
> located in the user's home directory C<~/.perlrc> and a global "rc"
> file, C</etc/perlrc>, that affects all instances of perl running on
> the machine.
>
> Note that this is couched in terms of a Unix-ish filesystem. Perl
> should support the analogous concept for the other platforms on which
> it compiles.
If we consider anything like this, I'd like to get away from the shell's
sequential processing model.
As use user, I would sometimes like to override the system defaults -
saying, no, do *not* use this library that's in the systemwide defaults,
I have a replacement module for that.
To support this, we'd have to load both files and integrate their
meaning, then execute.
Also, we should support inclusion of sub-files. In our environment, we
have a three-level sheel include file:
/etc/profile
$HOME/.profile -> symlink to a shared profile for this type of user
which includes $HOME/.custom/.profile -> really for this user
This three-level scheme is very useful, let's support it from the
start...
Hildo
