Re: non-standard package management

Bundling modules into your own distribution has worked great for us. What I use now is based on the build system in the Krang CMS. The CPAN sources are bundled with the software, and there is a build script that builds and installs them all to a local lib directory, making them available to all programs withing the distribution and avoiding any issues of updating system libs. With this approach, you can even have multiple copies with dependencies on different versions of the same modules installed on the same machine.

Comment on Re: non-standard package management

Replies are listed 'Best First'.
Re^2: non-standard package management by bluto (Curate) on Oct 13, 2005 at 19:21 UTC
With this approach, you can even have multiple copies with dependencies on different versions of the same modules installed on the same machine. This is a great idea in general. There are other benefits as well, esp if you don't have access to the target machine (e.g. you really need the most up to date module and a sysadmin you are dealing with may balk at installing it for you because it could break someone else's code; sysadmins with their own fiefdoms may not want to bother installing any extra stuff in addition to your modules; you want to give a normal user the ability to install/use your module; etc).	[reply]
Re^3: non-standard package management by johnnywang (Priest) on Oct 13, 2005 at 19:41 UTC
Lucky bluto, yours is the 500,000th post on PM!	[reply]
Re^4: non-standard package management by bluto (Curate) on Oct 14, 2005 at 15:19 UTC
Lucky? I don't really believe in it. Now if there's a big cash prize, it must be destiny; otherwise fate laughs at me once more. :-) Actually, congrats to PM and the folks that post here, since I've learned a lot from this place.	[reply]