Depends, how clueless is the target audience?
How dependent is your software on non-standard libraries (unlike expat,libxml2,libgd...)?
Does your software require specific versions of cpan modules?
See this presentation and the mentioned solutions Seen in PerlWeekly newsletter: Carton CPAN dependency manager, maybe you use par, or cpan2rpm/cpan2deb...
| [reply] [Watch: Dir/Any] |
Depends, how clueless is the target audience?
I would say I could assume they have basic Linux knowledge and can run scripts and answer interactive questions if needed in these scripts.
How dependent is your software on non-standard libraries (unlike expat,libxml2,libgd...)?
Not sure what you meant by non-standard libraries, every CPAN dependency I have is non-XS or has a non-XS version.
Does your software require specific versions of cpan modules?
No, works with any recent versions of libraries.
See this presentation and the mentioned solutions Seen in PerlWeekly newsletter: Carton CPAN dependency manager, maybe you use par, or cpan2rpm/cpan2deb...
Thanks for the heads up on Carton, didn't know this existed and I see T. Miyagawa recently started the project, this is great.
| [reply] [Watch: Dir/Any] |
I would say I could assume they have basic Linux knowledge
Linux?
Make RPMs.
| [reply] [Watch: Dir/Any] |
Ok so I've gone the route of including all non-CORE and non-XS dependencies bundled in an extlib in my distribution to make things as easy as possible for people trying to install the software, looks to be a good way.
When I started building the extlib in my development environment using cpanm -L extlib <module> etc I realized that cpanm installs everything in a local::lib compatible way, meaning everything doesn't go starting at extlib but rather extlib/lib/perl5. Therefore I would have to use local::lib "$FindBin::Bin/../extlib" in my programs instead of use lib "$FindBin::Bin/../extlib" to get use the dependencies in extlib but this brings a chicken-or-egg problem, local::lib in not in CORE :-(
Is there something I'm not thinking right here? I don't want to make to have to make an external dependency that people have local::lib already installed in their Perl tree (which could require administrator access)
| [reply] [Watch: Dir/Any] [d/l] [select] |
Is there something I'm not thinking right here?
I think so :)
If the route you have chosen is to bundle all non-CORE dependencies, and local::lib is not core, why can't you bundle local::lib?
| [reply] [Watch: Dir/Any] |
Sorry if I wasn't clear, its because one needs to use local::lib "$FindBin::Bin/../extlib" to be able to include and use these bundled dependencies therefore local::lib cannot be bundled
| [reply] [Watch: Dir/Any] [d/l] |