> > Unfortunatly I do not know enough to hack the source to tell the end > > user that they need these packages if they are not present...it's > > all too modular for me to do this... :) > > Humm.. Why not just put a small notice in the package postinst > (perhaps using debconf) telling the user that he should > install these packages to get HTTPS? > > Just a thought...
hmmm...why not just put a small notice in the package postinst telling the user that he should install kdebase-doc to get the documentation or kdebase-dev for the development files... I don't want to clutter up the postinst process (even using debconf) with things like this that can be easily stated in the README's... especially since the -crypto packages are already suggested (tho that doesn't mean much now) and will eventually go away. Ivan -- ---------------- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
