09-23-2019
Quote:
Originally Posted by
mohtashims
This has dependency on coreutils.
I am writing on getting that onboarded.
... and as always that should be done, and you should stage this on a development platform and confirm how to do the install, document the install details, and test results, and have it reviewed before you move this to a production environment.
Confirming (testing) how it works on AIX6.1 is your responsibility in your own development and test environment, not ours, obviously.
This User Gave Thanks to Neo For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
When i install SSH on AIX 5.1 I get the following message
{
A prerequisite package has not been installed. Open SSH
requires Open SSL (Secure Sockets Layer). Please install
Open SSL from the AIX Toolbox for Linux CD or Toolbox website:
}
I cannot find the AIX toolbox for linux CD, also on... (1 Reply)
Discussion started by: janr
1 Replies
2. Shell Programming and Scripting
Hi Folks!
Can you help me with this find -printf command. I seem to be unable to execute the printf-command from my shell script. I'm confused: :confused:
My shell script snippet looks like this:
#!/bin/sh
..
COMMAND="find ./* -printf '%p %m %s %u %g \n'"
echo "Command: ${COMMAND}"... (1 Reply)
Discussion started by: grahamb
1 Replies
3. AIX
Hello,
we have an 7015-R40, we want to update AIX.
oslevel shows 4.3.2.0
At ibm.com we found following
AIX 4300-11 maintenance package
Recommended maintenance for AIX 4.3.3
It's possible to update the system with this file or does we need another source?
Thank you!
S. (8 Replies)
Discussion started by: Sagitario
8 Replies
4. AIX
Hi,
I have a IBM box (RS/6000) Model No.7026-6H1, currently running AIX 4.3 and now I want to upgrade in AIX 5.3 version.
Please advice Is this model supports the AIX 5.3 version and what precautions we need to take before migration
Best Regds
Bhupal Singh (3 Replies)
Discussion started by: bhupals
3 Replies
5. AIX
Hi,
I have created a relocatable AIX package named Test.
The USIL is /abc
bash-2.05b# lsusil
INSTALL PATH = /abc
COMMENTS = None
Generally if a package gets installed in "/opt/Test" and i want to relocate it to "/abc" it gets installed under "/abc/Test". This happens the way in Solaris,... (2 Replies)
Discussion started by: vibhor_agarwali
2 Replies
6. Shell Programming and Scripting
Hi, I have a scripting assignment for an intro to linux class and I'm really confused about how to do something seemingly simple.
I am supposed to Print the name of each file in the /data/dir16/subdir1 directory in the following format: "My name is: bin"
The desired output example looks like:... (1 Reply)
Discussion started by: danschmidt
1 Replies
7. UNIX for Advanced & Expert Users
Friends,
Please let meknow, How we can find the dependancies of .dstream package & .rpm package before installation ?
For AIX, We can use the inutoc . command to create the .toc file for the bff package, What about Solaris & Linux ? (0 Replies)
Discussion started by: yb4779
0 Replies
8. AIX
Hi Everyone
I'm preparing for upgrading an application. The application upgrade documents say the following. its AIX 5.3 Server.
How do I find if my AIX supports the X11 windowing environment?
Thanks. (1 Reply)
Discussion started by: rocker_me2002
1 Replies
9. AIX
Please send me link for XVFB Source package for AIX (3 Replies)
Discussion started by: prathap.g
3 Replies
10. Shell Programming and Scripting
command:
$ printf 'u1u1.%*s' 7
so if i run the above command on a linux box, i get the expected output of:
jserver@jserver-VirtualBox:~$ printf 'u1u1.%*s' 7
u1u1. jserver@jserver-VirtualBox:~$
jserver@jserver-jserver:~$
it puts 7 spaces after the u1u1.
but when i run it... (4 Replies)
Discussion started by: SkySmart
4 Replies
LEARN ABOUT OSX
cpanplus::hacking
CPANPLUS::Hacking(3pm) Perl Programmers Reference Guide CPANPLUS::Hacking(3pm)
NAME
CPANPLUS::Hacking - developing CPANPLUS
DESCRIPTION
This document attempts to describe how to develop with the CPANPLUS environment most easily, how certain things work and why.
This is basically a quick-start guide to people who want to add features or patches to CPANPLUS.
OBTAINING CPANPLUS
Checkout CPANPLUS from its GIT repository at https://github.com/jib/cpanplus-devel <https://github.com/jib/cpanplus-devel> .
INSTALLING CPANPLUS
CPANPLUS follows the standard perl module installation process:
perl Makefile.PL
make
make test
make install
CONFIGURING CPANPLUS
When running "perl Makefile.PL" you will be prompted to configure. If you have already done so, and merely wish to update the "Makefile",
simply run:
perl Makefile.PL JFDI=1
This will keep your configuration intact. Note however, if there are changes to the default configuration file "Config.pm-orig", you should
either delete your current config file and reconfigure, or patch your config file from the new entries in "Config.pm-orig".
RUNNING CPANPLUS FROM DEVELOPMENT ENVIRONMENT
If you'd rather not install the development version to your "site_perl" directory, that's no problem. You can set your "PERL5LIB"
environment variable to CPANPLUS' "lib" directory, and you can run it from there.
RUNNING CPANPLUS TESTS
Tests are what tells us if CPANPLUS is working. If a test is not working, try to run it explicitly like this:
perl -I/path/to/cpanplus/lib t/XX_name_of_test.t 1
The extra '1' makes sure that all the messages and errors (they might be errors we're testing for!) are being printed rather than kept
quiet. This is a great way to find out the context of any failures that may occur.
If you believe this test failure proves a bug in CPANPLUS, the long output of the test file is something we'd like to see alongside your
bug report.
FINDING BUGS
Sometimes you might find bugs in CPANPLUS' behaviour. If you encounter these in a development snapshot, we'd appreciate a complete patch
(as described below in the "SENDING PATCHES" section.
If it's way over your head, then of course reporting the bug is always better than not reporting it at all. Before you do so though, make
sure you have the latest development snapshot, and the bug still persists there. If so, report the bug to this address:
bug-cpanplus@rt.cpan.org
A good "patch" would have the following characteristics:
Problem description
Describe clearly what the bug is you found, and what it should have done instead.
Program demonstrating the bug
Show us how to reproduce the bug, in a simple of a program as possible
[OPTIONAL] A patch to the test suite to test for the bug
Amend our test suite by making sure this bug will be found in this, and future versions of CPANPLUS (see "SUPPLYING PATCHES")
[OPTIONAL] A patch to the code + tests + documentation
Fix the bug, update the docs & tests. That way your bug will be gone forever :)
SUPPLYING PATCHES
Patches are a good thing, and they are welcome. Especially if they fix bugs you've found along the way, or that others have reported.
We prefer patches in the following format:
o In "diff -u" or "diff -c" format
o From the root of the snapshot
o Including patches for code + tests + docs
o Sent per mail to bug-cpanplus@rt.cpan.org
o With subject containing "[PATCH]" + description of the patch
You will always be informed if a patch is applied or rejected, and in case of rejection why that is (perhaps you can tweak the patch to
have it accepted after all).
perl v5.16.2 2012-10-11 CPANPLUS::Hacking(3pm)