http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8402
M. Tompsett <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from M. Tompsett <[email protected]> --- What populates C4/Installer/PerlDependencies.pm? The part that isn't in PerlDependencies.pm are the various applications/commands that need installing as well, which I see are in other sections. I agree there needs to be consistency, but what about the bigger picture of the perl dependencies required for a git install? I noticed you did a "sudo aptitude" command-line. Is this preferred over a: sudo dpkg --set-selections < install_misc/{OS}.packages sudo dselect way of doing it? aptitude may not be installed by default, and yes, neither is dselect. Also, notice I said {OS}.packages? The library names may be different between debian-based OSes, and this is why I like "apt-file" for finding a reasonable name. Check out bug 8517 for a script I wrote which uses koha_perl_deps.pl to add missing items to {OS}.packages. I believe a newer incarnation of it is in the release-tools git repo. As long as apt-file is installed and up to date and PerlDependencies is correct. It can be used to determine missing pieces and add them into the .packages file. Does PerlDependencies.pm get updated more accurately than debian/control? Perhaps the solution isn't to delete debian/control which is likely used to build packages where as install_misc/debian.packages is used for a git install, but rather make sure they are both updated from what may be the source: PerlDependencies.pm? Just some related brainstorming. :) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
