Mike Kupfer writes:
> >>>>> "Darren" == Darren J Moffat <Darren> writes:
>
> >> Okay, but I'm unable to figure out from that list what Rainer should
> >> do with SUNWcryptoint. What do you recommend?
>
> Darren> What problem is being caused by the way it is handled today ?
>
> It's impossible for external developers to get a clean package build.
>
> If SUNWcryptoint is in usr/closed/pkgdefs, you (well, external
> developers) get complaints about the dprov driver files, which are in
> the proto area but not listed in any package.
Exactly: even the sources are delivered. And just removing the sources
from the open tree to avoid a build warning seems the wrong approach.
> If SUNWcryptoint is in usr/src/pkgdefs, you get complaints about the
> certs, which are listed in the package but aren't in the proto area.
>
> This hasn't been an issue because until now nobody has tried to make
> open-only package builds work properly. But that's precisely what
> Rainer is working on to clean up.
The road I've usually taken in such cases was to split the single package
with both open and closed components into two (or more). This seems to be
the correct way here, too. It's pretty obvious that the keys and certs
cannot be delivered, so they should go into a package of their own. Even
if this split happens, keys/certs and the dprov will be delivered at the
same time, only not in a single package. I wouldn't expect this to be a
problem, though. I'm just looking for a good name for the new package:
SUNWdprov might be used for the dprov driver (for lack of a
better/descriptive name), and the certs could remain in SUNWcryptoint.
Rainer
-----------------------------------------------------------------------------
Rainer Orth, Faculty of Technology, Bielefeld University
_______________________________________________
opensolaris-code mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
