On Thursday 28 November 2013 08:05:09 Gabor Szabo wrote: > Creating an in-house .deb have more chances but if it is an upgrade and > it gets installed on top of an existing version of a module it might > break something else. Is it possible to create a .deb that would > install in a separate directory? Like local::lib? > > Having a per application local::lib sounds like to easiest solution, > but maybe only because I never created a .deb The main drawback is that maintenance will be more difficult if you have several applications to maintain, each with its own local::lib (funny thing: my fingers did actually type local::lost...). Tracking the content of several local::lib tree is not fun. A while ago I used to install new modules with cpan in /usr/local. Then, the module ended being packaged by Debian (that was before I began to contribute to Debian). So I happily installed the new version from Debian. Still my application was using the old version because modules in SITEDIR are loaded before modules in VENDORDIR and I had forgotten about the old install with cpan. After being bitten by the same issue several times, I wiped /usr/local/ and always use dh-make-perl to create my own debian packages. Hope this helps
Attachment:
signature.asc
Description: This is a digitally signed message part.