10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have the following line in the script
unset _SET_ENV_AA
unset _SETENV
but where I can check the value for this environement variable (2 Replies)
Discussion started by: stew
2 Replies
2. Red Hat
Hi all,
Does anyone know how to change PROC_MEM_RES?
We have a DB server with quite a few oracle instances (RAC) and we are getting critical alerts for PROC_MEM_RES.
Anyone know how to increase the current setting or what we should do about it?
Thanks in advance.
john (2 Replies)
Discussion started by: jonnyd
2 Replies
3. Shell Programming and Scripting
I have a script with a $PASSWORD variable. I unset it right after using it, just to minimize the chance it could be left around for a snooper. That worked just fine... until I used a password with a value of "P@ssw0rd" Now, unset (even with -f, even with the variable enquoted) tells me: unset:... (1 Reply)
Discussion started by: jnojr
1 Replies
4. Web Development
(Above from Apache docs).
On my system, using:
SetEnvIf User-Agent Mozilla IsBad=1
Order allow,deny
Allow from all
Deny from env=IsBad ...I see that environment variable is set (using phpinfo()) but the page is still served. No errors in the Apache logs. (1 Reply)
Discussion started by: gnurob
1 Replies
5. Shell Programming and Scripting
greetings,
i have a sh script that calls a python script. the sh script sets an env variable BIN:
export BIN=bin64i need to get that BIN variable's value and use it within this python script. anyone know how to do this? thanx in advance. (5 Replies)
Discussion started by: crimso
5 Replies
6. Homework & Coursework Questions
Use and complete the template provided. The entire template must be completed. If you don't, your post may be deleted!
1. The problem statement, all variables and given/known data:
Basically, the prompt is make a makefile with various sub makefiles in their respective subdirectories. All code... (1 Reply)
Discussion started by: Tatl
1 Replies
7. Shell Programming and Scripting
I have a shell script I want to run that will set environment variables based on the value of an input variable submitted when the shell script is called. For example:
$ mgenv.sh prod
This would set environment variables for prod
$ mgenv.sh test
This would set environment variables... (1 Reply)
Discussion started by: brtaylor73
1 Replies
8. UNIX for Advanced & Expert Users
Hi All,
May be this is a very simple question...
$ b=8
$ readonly b
$ echo $b
8
$ b=90
-bash: b: readonly variable
$ unset b
-bash: unset: b: cannot unset: readonly variable
I m not able to change the readonly mode of variable b
Please help me out..
Thanks
Nidhi (2 Replies)
Discussion started by: Nidhi2177
2 Replies
9. AIX
Hi,
I have installed ODWEK software on AIX box and set the environment variables like: PATH,LIBPATH,LD_LIBRARY_PATH,CLASSPATH.
My question here is do I need to reboot the system to take these changes or is there anyother workaround. I heard that there is 'export'. But I don't know how far it... (1 Reply)
Discussion started by: srangu
1 Replies
10. AIX
Hi,
I have installed ODWEK software on AIX box and set the environment variables like: PATH,LIBPATH,LD_LIBRARY_PATH,CLASSPATH.
My question here is do I need to reboot the system to take these changes or is there anyother workaround. I heard that there is 'export'. But I don't know how far it... (1 Reply)
Discussion started by: srangu
1 Replies
ExtUtils::MakeMaker::Tutorial(3pm) Perl Programmers Reference Guide ExtUtils::MakeMaker::Tutorial(3pm)
NAME
ExtUtils::MakeMaker::Tutorial - Writing a module with MakeMaker
SYNOPSIS
use ExtUtils::MakeMaker;
WriteMakefile(
NAME => 'Your::Module',
VERSION_FROM => 'lib/Your/Module.pm'
);
DESCRIPTION
This is a short tutorial on writing a simple module with MakeMaker. Its really not that hard.
The Mantra
MakeMaker modules are installed using this simple mantra
perl Makefile.PL
make
make test
make install
There are lots more commands and options, but the above will do it.
The Layout
The basic files in a module look something like this.
Makefile.PL
MANIFEST
lib/Your/Module.pm
That's all that's strictly necessary. There's additional files you might want:
lib/Your/Other/Module.pm
t/some_test.t
t/some_other_test.t
Changes
README
INSTALL
MANIFEST.SKIP
bin/some_program
Makefile.PL
When you run Makefile.PL, it makes a Makefile. That's the whole point of MakeMaker. The Makefile.PL is a simple program which loads
ExtUtils::MakeMaker and runs the WriteMakefile() function to generate a Makefile.
Here's an example of what you need for a simple module:
use ExtUtils::MakeMaker;
WriteMakefile(
NAME => 'Your::Module',
VERSION_FROM => 'lib/Your/Module.pm'
);
NAME is the top-level namespace of your module. VERSION_FROM is the file which contains the $VERSION variable for the entire
distribution. Typically this is the same as your top-level module.
MANIFEST
A simple listing of all the files in your distribution.
Makefile.PL
MANIFEST
lib/Your/Module.pm
File paths in a MANIFEST always use Unix conventions (ie. /) even if you're not on Unix.
You can write this by hand or generate it with 'make manifest'.
See ExtUtils::Manifest for more details.
lib/
This is the directory where your .pm and .pod files you wish to have installed go. They are layed out according to namespace. So
Foo::Bar is lib/Foo/Bar.pm.
t/ Tests for your modules go here. Each test filename ends with a .t. So t/foo.t/ 'make test' will run these tests. The directory is
flat, you cannot, for example, have t/foo/bar.t run by 'make test'.
Tests are run from the top level of your distribution. So inside a test you would refer to ./lib to enter the lib directory, for
example.
Changes
A log of changes you've made to this module. The layout is free-form. Here's an example:
1.01 Fri Apr 11 00:21:25 PDT 2003
- thing() does some stuff now
- fixed the wiggy bug in withit()
1.00 Mon Apr 7 00:57:15 PDT 2003
- "Rain of Frogs" now supported
README
A short description of your module, what it does, why someone would use it and its limitations. CPAN automatically pulls your README
file out of the archive and makes it available to CPAN users, it is the first thing they will read to decide if your module is right
for them.
INSTALL
Instructions on how to install your module along with any dependencies. Suggested information to include here:
any extra modules required for use
the minimum version of Perl required
if only works on certain operating systems
MANIFEST.SKIP
A file full of regular expressions to exclude when using 'make manifest' to generate the MANIFEST. These regular expressions are
checked against each file path found in the distribution (so you're matching against "t/foo.t" not "foo.t").
Here's a sample:
~$ # ignore emacs and vim backup files
.bak$ # ignore manual backups
# # ignore CVS old revision files and emacs temp files
Since # can be used for comments, # must be escaped.
MakeMaker comes with a default MANIFEST.SKIP to avoid things like version control directories and backup files. Specifying your own
will override this default.
bin/
SEE ALSO
perlmodstyle gives stylistic help writing a module.
perlnewmod gives more information about how to write a module.
There are modules to help you through the process of writing a module: ExtUtils::ModuleMaker, Module::Install, PAR
perl v5.12.1 2010-04-26 ExtUtils::MakeMaker::Tutorial(3pm)