Sponsored link
Vyatta –
Linux & Open Source
Alternative to Cisco –
Advanced Routing,
Firewall, VPN, QoS..
Free Download ->
| |||||||||||
|
| |||||||||||
The Great Package Management ExperimentThe Great Package Management ExperimentPosted Sep 25, 2003 17:00 UTC (Thu) by zooko (subscriber, #2589)In reply to: The Great Package Management Experiment by torsten Parent article: The Great Package Management Experiment I use GNU stow on my Debian system, when I want to build something from source: ./configure --prefix=/usr/local/stow/bindlywhoop-v1.2 It doesn't do dependency management for you, but for some reason I rarely need it. Perhaps the things that I want to hack on and compile from source don't usually have dependencies.
(Log in to post comments)
The Great Package Management Experiment Posted Sep 28, 2003 23:17 UTC (Sun) by torsten (guest, #4137) [Link] ./configure --prefix=/usr/local/stow/bindlywhoop-v1.2 This method is defective. The path is hard-coded into some of the libraries and binaries. When you move the directory to another prefix, the package will fail (some packages fail, some don't).
The Great Package Management Experiment Posted Oct 4, 2003 14:11 UTC (Sat) by csh (guest, #15725) [Link] The proper way to use something like stow is this: % ./configure --prefix=/usr/local When you install, you use this command: % make prefix=/usr/local/stow/<package>-<version> Then when you stow the program, it will have normal paths like you would expect. If you aren't using a package with the GNU auto stuff, you'll have to do this step manually. I used to maintain my own system, and a set of patches for different packages to handle the dual nature of a "stowed" install.
|
|||||||||||