Re: compile-time dependencies on external sources?
On Tue, Mar 27, 2001 at 09:46:30AM -0600, Steve Langasek wrote:
> I'm the upstream maintainer on a PAM module, pam_smbpass, which I'm
> interested in packaging for Debian. The catch is that the module requires
> that a complete (well, nearly complete) copy of the Samba source code be
> available at build time. For questions of maintenance and bandwidth, I've
> chosen not to include the Samba source in the tarball; I find that
> automatically downloading the Samba code during the build process works just
> as well for upstream purposes.
Which parts of the Samba source does it use? Does it just include header
files, or does it compile and link with code there?
There is a module, libpam-smb, which sounds similar to your program, which
includes a small (216k) SMB library in the smbval/ directory.
It seems to me that if other programs are using portions of Samba's source code
in order to compile, those portions should be made into a library. The
'libsmb' subdirectory in the Samba source appears to already encapsulate the
modules that might be more broadly useful. You should file a wishlist bug
against the samba package and discuss this possibility with the maintainer, but
judging by Samba's bug list, it may not do any good.
Maybe it is time for someone to write a small NetBios library capable of
supplying shared libraries, and meeting the demands of programs like yours.
--
- mdz
Reply to: