Hello, I'm quite new to HP-UX and I stumbeled upon some strange behaviour from tar.
I have a script like this:
find -mtime $days -type f|xargs tar cvf tarfile.tar
and it make me a tar file with files that has been changed in $days.
When i run 'tar tf tarfile.tar' it give me output like... (5 Replies)
Hi,
On my Unix Server in my directory, I have 70 files distributed in the following directories (which have several other files too). These files include C Source Files, Shell Script Source Files, Binary Files, Object Files.
a) /usr/users/oracle/bin
b) /usr/users/oracle... (1 Reply)
Hi Guru,s/Geek,s
I need help to create RPM names from rpms.
Example :
a2ps-4.14-6.fc10.i386
perl-Email-Find-0.10-2.fc10.noarch
directfb-1.2.7-2.fc10.i386
libid3tag-0.15.1b-7.fc10.i386
apr-util-1.3.7-1.fc10.i386
libquicktime-1.0.3-4.fc10.i386
The Desired Output is :
a2ps... (2 Replies)
Hi All,
I had created a installer (RPM), but later I came across that Netbeans (netbeans-6.9-ml-linux), Flex Builder Linux Alpha (flexbuilder_linux_install_a4_081408.bin) and JDK (jdk-6u20-linux-i586-rpm.bin) dont provide any RPM but they provide a huge binary executable shell script.
My... (0 Replies)
How to make RPM not write to RPM database if RPM fails to deploy?
IE I create an rpm spec file that contains the following
if
then
exit 1
fi
My rpm will fail at deployment, but if I do rpm -qa , I can see the rpm in the rpm db (3 Replies)
I would like to package my developed application and deploy it using RPM to my users. Understand that RHEL5 has the following directories created:
/usr/src/redhat/BUILD
/usr/src/redhat/RPMS
/usr/src/redhat/SOURCES
/usr/src/redhat/SPECS
/usr/src/redhat/SRPMS
Using KDevelop as my... (0 Replies)
I would like to package my developed application and deploy it using RPM to my users. Understand that RHEL5 has the following directories created:
/usr/src/redhat/BUILD
/usr/src/redhat/RPMS
/usr/src/redhat/SOURCES
/usr/src/redhat/SPECS
/usr/src/redhat/SRPMS
Using KDevelop as my... (0 Replies)
I m referring below article for creating rpm.
Installation and Setup Rpmbuild Tutorial
As per the document i will need rpmdevtools and rpmlint to begin with.
However i have yum installed and whenever i run them i get below output.
# yum install rpmdevtools rpmlint
Setting up Install Process... (0 Replies)
i would like to package up an rpm from pre-installed files, say i have a program called "widget" installed under "/opt/widget"
/opt/widget/bin/*
/opt/widget/lib/*
/opt/widget/etc/*
/opt/widget/log/*
and i want to create an rpm from those already installed files, what would the spec file... (2 Replies)
Discussion started by: melixir
2 Replies
LEARN ABOUT DEBIAN
dh_installman
DH_INSTALLMAN(1) Debhelper DH_INSTALLMAN(1)NAME
dh_installman - install man pages into package build directories
SYNOPSIS
dh_installman [debhelperoptions] [manpage...]
DESCRIPTION
dh_installman is a debhelper program that handles installing man pages into the correct locations in package build directories. You tell it
what man pages go in your packages, and it figures out where to install them based on the section field in their .TH or .Dt line. If you
have a properly formatted .TH or .Dt line, your man page will be installed into the right directory, with the right name (this includes
proper handling of pages with a subsection, like 3perl, which are placed in man3, and given an extension of .3perl). If your .TH or .Dt
line is incorrect or missing, the program may guess wrong based on the file extension.
It also supports translated man pages, by looking for extensions like .ll.8 and .ll_LL.8, or by use of the --language switch.
If dh_installman seems to install a man page into the wrong section or with the wrong extension, this is because the man page has the wrong
section listed in its .TH or .Dt line. Edit the man page and correct the section, and dh_installman will follow suit. See man(7) for
details about the .TH section, and mdoc(7) for the .Dt section. If dh_installman seems to install a man page into a directory like
/usr/share/man/pl/man1/, that is because your program has a name like foo.pl, and dh_installman assumes that means it is translated into
Polish. Use --language=C to avoid this.
After the man page installation step, dh_installman will check to see if any of the man pages in the temporary directories of any of the
packages it is acting on contain .so links. If so, it changes them to symlinks.
Also, dh_installman will use man to guess the character encoding of each manual page and convert it to UTF-8. If the guesswork fails for
some reason, you can override it using an encoding declaration. See manconv(1) for details.
FILES
debian/package.manpages
Lists man pages to be installed.
OPTIONS -A, --all
Install all files specified by command line parameters in ALL packages acted on.
--language=ll
Use this to specify that the man pages being acted on are written in the specified language.
manpage ...
Install these man pages into the first package acted on. (Or in all packages if -A is specified).
NOTES
An older version of this program, dh_installmanpages(1), is still used by some packages, and so is still included in debhelper. It is,
however, deprecated, due to its counterintuitive and inconsistent interface. Use this program instead.
SEE ALSO debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
9.20120909 2012-04-24 DH_INSTALLMAN(1)