On Wed, 07 Feb 2007 23:39:39 +0100 Luca Capello wrote: > ATM I don't really see any reason to create a separate package just > for tf-tool, because libthinkfinger + tf-tool (binary and manpage) > should generate a package around less than 50K in size. In case new > tools will be added, we can split the package. > > Is a strong reason against this?
Is tf-tool to be used by the user directly? If so, I would place it in an own package. If it's only a binary used in scripts/whatever - ship it in lib*. The point is, the user might want to read something about the tool he is using. There is a manpage and /usr/share/doc/<package>/, the last one would be ugly for libthinkfinger, because user would expect packagename==binaryname. Hope you understand what I mean ;) By the way, are there any prerelease packags for testing? This UPEK-blob gets on my nerves ;) Regards Evgeni -- ^^^ | Evgeni -SargentD- Golov ([EMAIL PROTECTED]) d(O_o)b | GPG/PGP-Key-ID: 0xAC15B50C >-|-< | 0C04 F872 0963 ADC9 AA83 882B 24A0 1418 AC15 B50C / \ | http://www.die-welt.net - [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
