develop_rc.pl - a development startup script.
Copyright (C) 2001, 2002 Mark Veltzer; All rights reserved.
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111, USA.
MANIFEST: develop_rc.pl PROJECT: meta VERSION: 0.02
develop_rc.pl
"AEGIS - the best project manager this side of the sahara..." As usual - take heed... This is the standard text to be a Meta developer. Place this text in a fixed location (~/.develop_rc /etc/develop_rc etc...) and source it at startup. some explanation on this file: This file exists because when we want to work on the baseline we have to set a few environment variables for the command line to work (we do work on the command line...). setting environment variables is not done from perl or other language scripts but rather from a shell script (the same one your'e using - currently bash2) because: 0. its not a practice to change your parent process data (it seems to me that you cant realy do that without the concent of your parent process). 1. its difficut. 2. its non standard. 3. I hate it. 4. Its impossible. Therefore we wrote this script. This script should be "sourced" as this is the only way to change the env variables of the calling process. Routines here are characterised by the fact that they change the environment parameters of the calling shell. A rule of thumb about putting routines here should be: if the routine is supposed to deal with environment parameters it should be here if not - write a perl script instead. The routines here change the runtime affecting values of variables - not the compile time ones...
Important for developers:
It is important that all the interactive stuff be done AFTER the basic path settings since they may run a few executables and those will need to path settings in order to run...
display help message
display pod options snipplet
display manual page
quit without doing anything
run a gtk ui to get the parameters
show license and exit
show copyright and exit
show description and exit
show history and exit
where is your aegis located
extra path for the shell runner
extra path for the dynamic linkder
extra path for the man pager
extra path for the info pager
extra path for the XML catalogs
extra path for the SGML catalogs
extra path for the sgml path
what is the binary platform you are working on
what is the dll platform you are working on
what is your shell
do you want to set PATH for tools
do you want to set LD_LIBRARY_PATH for tools
do you want to set MANPATH for tools
do you want to set INFOPATH for tools
do you want to set XML_CATALOG_FILES for tools
do you want to set SGML_CATALOG_FILES for tools
do you want to set SGML_SEARCH_PATH for tools
do you want to set SGML_PATH for tools
do you want to set CLASSPATH for tools
do you want to set PERL5LIB for tools
do you want to set PYTHONPATH for tools
do you want perl baseline executables settings (this is for libs and bins)
do you want to set the CDPATH for development
do you want to cd to your change on login
do you want ls baseline coloring
do you want ls standard coloring
do you want --long opt for ls coloring
do you want aegis type (Peter) shortcuts (only valid for bash)
do you want to set your AEGIS_PROJECT from your aegis prefs
do you want to set your AEGIS_CHANGE from your aegis prefs
do you want to set the BL environment variable to point to the baseline
do you want to set the CH environment variable to point to the change
do you want to set the PS1 environment variable for the shell
do you want to set the PAGER environment varialbe
do you want to set the MANPAGER variable
where is your aegis profile located
do you want verbosity
no free arguments are allowed
None.
Name: Mark Veltzer Email: mailto:veltzer@cpan.org WWW: http://www.veltzer.org CPAN id: VELTZER
0.00 MV move tests to modules 0.01 MV finish papers 0.02 MV md5 issues
Error(3), File::Basename(3), Meta::Baseline::Aegis(3), Meta::Ds::Ohash(3), Meta::Utils::File::File(3), Meta::Utils::Opts::Opts(3), Meta::Utils::Output(3), Meta::Utils::System(3), POSIX(3), strict(3)
-get the $- variable from the shell as input (the shell has it) and use it to make checks whether this script runs interactivly or not...
-make routine in here more accessible in that users could change their platform / architecture in the middle of a shell session.
-make options to put the development stuff ahead of everything and the reverse.
-make stuff here more generic (all the variables are handled pretty much the same...).
-make the coloring work again (the code is commented).
-remove the functions here which have to do with paths, evnrionment and the like and use my modules instead.
-add an option to set default posgresql and mysql env variables here (like default database name and other stuff).
To install Meta::Init, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Meta::Init
CPAN shell
perl -MCPAN -e shell install Meta::Init
For more information on module installation, please visit the detailed CPAN module installation guide.