Sponsored Content
Operating Systems Linux Red Hat Local installation of package in Red Hat / Fedora Linux Post 303011566 by drysdalk on Friday 19th of January 2018 07:53:51 PM
Old 01-19-2018
Hi,

I'm not 100% sure what you mean, sorry. The package will have had its files extracted underneath wherever you ran the cpio command. You might be able to just run /path/to/wherever/bin/whatever and it might just work, but equally it may not. As I mentioned previously, many packages are not designed to be re-locatable, and might misbehave or fail in unexpected ways as a result of not having their binaries, libraries and other support files in the locations they expect to find them. I'm not myself familiar with Erlang at all, so can't really give any package-specific advice here.

If it comes to it, then as I say you can always download the source of the package (assuming it has source code available, almost all packages do generally speaking) and compile it yourself, specifying exactly the directory you want to install the resulting binaries in. You don't normally have to be root or need to have sudo access to compile most things, if user permissions and access rights are ultimately your real problem here.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

red hat linux installation boot floppy disk

Hi, My dear friends, I am trying to install red hat linux. I have downloaded its disc1. On the instructions page, the next stage is to make the boot disk, so that I can boot from the floppy. However, I am unable to locate the boot image iso file. I tried on google, but I got a few files which... (3 Replies)
Discussion started by: linuxpenguin
3 Replies

2. Linux

Installation Problem on Red hat linux 9

Hi, I am trying to install our new acquired Red Hat linux 9 on Compaq Proliant ML370. However, l has already configured the raid 0+1. The linux installation starts from the CD, its allows for the selection of Language, keyboard but l am stocked at choosing the installation package media. I... (4 Replies)
Discussion started by: kayode
4 Replies

3. UNIX for Dummies Questions & Answers

Problem Red Hat 9 Installation

I have a problem with a red hat 9 install on a compaq laptop. I installed the OS and everything tests ok but It boots to a blank screen instead of the GUI login I wanted. What can I do to correct this instead of installing all over. I tried the rescue option several times and tried to run... (2 Replies)
Discussion started by: vedder191
2 Replies

4. Red Hat

The Red Hat Cluster Manager Installation and

Linux RedHat Cluster Manager InstallationAdministrationGuide (0 Replies)
Discussion started by: merlin
0 Replies

5. UNIX Desktop Questions & Answers

Does Red Hat Fedora support Nvidia card 8800GTX and 260 card?

Does Red Hat Fedora support Nvidia card 8800GTX and 260 card? Does any Linux OS support Nvidia card? (1 Reply)
Discussion started by: sito
1 Replies

6. Red Hat

Installation of Red Hat enterprise edition?

HI All I am new to lunix operating system.I Wnt to move to Lunix.So would u pepole please tell me the documentatiion for installation os lunix on my personal computer Thamnks&Regards, I.venu. (1 Reply)
Discussion started by: infovenu231
1 Replies

7. Red Hat

download package for red hat linux 5

I try to do virtual guest in red hat linux 5. But I have no red hat netowrk account . I want to download below package xen kernel-xen package So, where I can get them ?? Any advice ??? (9 Replies)
Discussion started by: chuikingman
9 Replies

8. Red Hat

Fedora or Red Hat Man Pages

Is there a website that has either the Fedora or Red Hat Man Pages? Something similar to this with Ubuntu? Ubuntu Manpage: Welcome (4 Replies)
Discussion started by: cokedude
4 Replies

9. Red Hat

Does Red hat linux 9 has audit rpm package?

Dear All I have a old system run in Red hat Linux 9.. And if it's possible, I want to install the audit rpm package in the Red hat Linux 9. But I can't find the audit-*.rpm file in the Red hat Linux 9's CD..? Can any help me to conform Red hat Linux 9 doesn't support audit? Any... (0 Replies)
Discussion started by: nnnnnnine
0 Replies

10. Red Hat

Red Hat 6 yum install no package availiable

I have installed Red Hat Enterprise Linux 6.1 server, it is registered but not subscribed. If I install using yum every time it is showing that no package available, how to resolve it? (2 Replies)
Discussion started by: ainstin
2 Replies
DH_STRIP(1)							     Debhelper							       DH_STRIP(1)

NAME
dh_strip - strip executables, shared libraries, and some static libraries SYNOPSIS
dh_strip [debhelperoptions] [-Xitem] [--dbg-package=package] [--keep-debug] DESCRIPTION
dh_strip is a debhelper program that is responsible for stripping executables, shared libraries, and static libraries that are not used for debugging. This program examines your package build directories and works out what to strip on its own. It uses file(1) and file permissions and filenames to figure out what files are shared libraries (*.so), executable binaries, and static (lib*.a) and debugging libraries (lib*_g.a, debug/*.so), and strips each as much as is possible. (Which is not at all for debugging libraries.) In general it seems to make very good guesses, and will do the right thing in almost all cases. Since it is very hard to automatically guess if a file is a module, and hard to determine how to strip a module, dh_strip does not currently deal with stripping binary modules such as .o files. OPTIONS
-Xitem, --exclude=item Exclude files that contain item anywhere in their filename from being stripped. You may use this option multiple times to build up a list of things to exclude. --dbg-package=package This option is a now special purpose option that you normally do not need. In most cases, there should be little reason to use this option for new source packages as debhelper automatically generates debug packages ("dbgsym packages"). If you have a manual --dbg-package that you want to replace with an automatically generated debug symbol package, please see the --dbgsym-migration option. Causes dh_strip to save debug symbols stripped from the packages it acts on as independent files in the package build directory of the specified debugging package. For example, if your packages are libfoo and foo and you want to include a foo-dbg package with debugging symbols, use dh_strip --dbg-package=foo-dbg. This option implies --no-automatic-dbgsym and cannot be used with --automatic-dbgsym or --dbgsym-migration. -k, --keep-debug This option is a now special purpose option that you normally do not need. In most cases, there should be little reason to use this option for new source packages as debhelper automatically generates debug packages ("dbgsym packages"). If you have a manual --dbg-package that you want to replace with an automatically generated debug symbol package, please see the --dbgsym-migration option. Debug symbols will be retained, but split into an independent file in usr/lib/debug/ in the package build directory. --dbg-package is easier to use than this option, but this option is more flexible. This option implies --no-automatic-dbgsym and cannot be used with --automatic-dbgsym. --dbgsym-migration=package-relation This option is used to migrate from a manual "-dbg" package (created with --dbg-package) to an automatic generated debug symbol package. This option should describe a valid Replaces- and Breaks-relation, which will be added to the debug symbol package to avoid file conflicts with the (now obsolete) -dbg package. This option implies --automatic-dbgsym and cannot be used with --keep-debug, --dbg-package or --no-automatic-dbgsym. Examples: dh_strip --dbgsym-migration='libfoo-dbg (<< 2.1-3~)' dh_strip --dbgsym-migration='libfoo-tools-dbg (<< 2.1-3~), libfoo2-dbg (<< 2.1-3~)' --automatic-dbgsym, --no-automatic-dbgsym Control whether dh_strip should be creating debug symbol packages when possible. The default is to create debug symbol packages. --ddebs, --no-ddebs Historical name for --automatic-dbgsym and --no-automatic-dbgsym. --ddeb-migration=package-relation Historical name for --dbgsym-migration. NOTES
If the DEB_BUILD_OPTIONS environment variable contains nostrip, nothing will be stripped, in accordance with Debian policy (section 10.1 "Binaries"). This will also inhibit the automatic creation of debug symbol packages. The automatic creation of debug symbol packages can also be prevented by adding noautodbgsym to the DEB_BUILD_OPTIONS environment variable. However, dh_strip will still add debuglinks to ELF binaries when this flag is set. This is to ensure that the regular deb package will be identical with and without this flag (assuming it is otherwise "bit-for-bit" reproducible). CONFORMS TO
Debian policy, version 3.0.1 SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHOR
Joey Hess <joeyh@debian.org> 11.1.6ubuntu2 2018-05-10 DH_STRIP(1)
All times are GMT -4. The time now is 07:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy