without zip and unzip glftpd installation is not complete and while it can still be installed without, it should either depend or take advantage of USE flags for user to specify preference.
Steps to Reproduce:
you can use glftpd just fine w/out zip
it can be used fine, but the zip file zipscript functionality hinges on the zip and unzip binaries being copied to the glftpd bin dir.
it is not a fully functional install without them.
therefore some type USE flag to determine the installers preference of using a functional zipscript or not would be the best solution.
well, i disagree
adding a USE flag is cruft
sites that run w/out zipscript dont need zip
that's the same logic as sites that run without ssl smpt don't need ssl built into postfix, yet there is still a USE flag to specify user preference... and that listof examples goes on ad infinitum.
If a specific package has a certain component that will be enabled or disabled based on the pre-existence of other binaries provided by other packages isn't the whole point of portage to enable automated handling of those dependencies?
You do realize I'm talking about glftpd built-in zipscript functionality and not some random botscript...
Please, could you fix this? The reason in Comment #3 why glftpd does not depend on zip/unzip is just foolish.
Reopenning since others besides myself seem to feel SpanKY's reasoning is flawed.
This ebuild should either depend on or have a USE flag for zip functionality.
glftpd has builtin zipscript functions that will not function without the zip libraries being present. This means that a standard, unaltered, non-custom glftpd installation is incomplete without them.
This is not cruft; this is what portage is designed for.
if zip was a global/standard USE flag i'd add it, but i'm not going to bother as a local USE flag
Then is honestly should have a solid depend on the zip and unzip packages... it's an INCOMPLETE install without those libs, wether the end-user employs them or not.
This is an absurd arguement...