Information About These Packages and The Repository
Dependencies
I have manually worked out the following dependencies for the packages; there may be others I have missed. These do not include the inter-dependences among the samsungmfp packages.
samsungmfp-driver depends on cups (or cupsys), ghostscript (or gs), libstdc++5, and sane
samsungmfp-configurator-qt3 depends on libqt3-mt, libstdc++5, libtiff4, and libpng3; it also may require Java and certainly requires Xorg, but they aren't hard dependencies
samsungmfp-configurator-qt4 depends on libqtcore4 (or libqt4-core), libqtgui4 (or libqt4-gui), libqt4-qt3support, libqt4-svg, libstdc++5, libtiff4, and libpng3; it also may require Java and certainly requires Xorg, but they aren't hard dependencies
Differences in Installation from the Samsung Installer
I use entirely the /usr/lib/ directory instead of /usr/lib64/, as per Debian standard
The packages do not include the installer/uninstaller pieces
I did not include the .directory, .menu, or most .desktop files, and the .desktop entry included is filed under the normal freedesktop structure rather than Samsung-specific
/usr/bin/lpr is left intact, the link to slpr is in /usr/local/bin so that the packages don't conflict and the standard lpr is still available
The modprobe.conf file is not created, the proper modprobe.d/ structure is used
A link is included to libtiff4.so when needed, such that libtiff3 is not required at all
libpng3 is required to address problems that occasionally occur with the Configurator and AMD64 architectures, because an inappropriate reference to a library name was compiled in; although this does not appear to be a problem with i386, I have left the libpng3 dependency in anyway (it just creates a link to libpng12)
All the Configurator pieces are English-only, I don't know if Samsung provides alternative languages in their country-specific archives
I did not include the duplicate ppd/cms files in /opt/Samsung/mfp/share/ppd/, as they are just a 15 MB waste of space; only the pdd/cms files in /usr/share/cups/samsung/ are needed
Making Your Own Packages
I have provided the directory structure, control files, and scripts I use to build these packages here. Basically just unpack the archive, unpack the Samsung Unified Linux Driver archive (directly from Samsung) such that cdroot is present in the samsungmfp directory, and run the "assemble_smfp_packages.sh" and "build_smfp_packages.sh" scripts. The assemble script would work as a starting point for building packages for non-Debian distributions, while the build script is specific for dpkg. Note that apt will not install the created .debs without having them in a repository, and dpkg won't resolve the necessary dependencies. Gdebi may be able to install the created packages locally.
Why These Packages Will Never Be Official
I don't have access to the source code, so paths are compiled in and I am constrained by them; use of /opt and the /usr/bin/lpr issue preclude ever making a well-behaved package (from an official standpoint)
No source code, so Debian (and sites for hosting software such as Sourceforge) won't touch this
Because there's no point in "Debian-izing" the packages completely, I am not following Debian standards for changelogs or copyright files, nor did I include man pages