[Bug crypto/27649] Addition of --standalone-crypto configure option

[raif at swiftdsl dot com dot au]

------- Comment #17 from raif at swiftdsl dot com dot au  2006-07-14 05:53 
-------
(In reply to comment #16)
> (In reply to comment #7)
> > 
> > > We only have a few dependencies on
> > > gnu.classpath.debug, gnu.classpath.Configuration, gnu.classpath.ByteArray 
> > > etc.
> > > in most of these packages which we could remove?
> > 
> > gnu.classpath.debug.* can be jarred in its own jar.
> > 
> > ByteArray is only used by RSACipherImpl and can probably be relocated to
> > gnu.java.security.util.
> > 
> Also, there seems to be a dependence on gnu.java.io.Base64InputStream in
> gnu.java.security.provider. Any suggestions on handling this?

my Eclipse shows me:

1. the only class, in gnu.java.security.provider, which uses this class is
X509CertificateFactory.

2. the static method in that class is not used by any class in the standalone
candidate security packages.

one obvious --and simple-- option is to (only) duplicate the
input-stream-related methods of that class in a (gnu.java.security.provider)
package-private class.  keeping the same name means we only have to remove the
import line from the dependant class (X509CertificateFactory).


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27649