> So md5 is available in SUNWperl584core package. Some questions I have.

Hopefully I'll be able to pair them with answers!


> If I want to port two other encryption routines along with crypt-cbc, Is  
> there anything I need to follow other than OSR ?

Oh yes, there is. There is the PROCESS. It's not easy if someone is not
sitting next to you, so you'll have more questions in time.

Integration:
https://opendorfl.czech/twiki/bin/view/OPENdorfl/OSSPackagesSolarisRPE_Process

Packaging:
https://opendorfl.czech/twiki/bin/view/OPENdorfl/OSSPackagesSolarisRPE



> What kind of naming convention I should follow while registering package  
> name ? Should these packages also be prefixed with SUNW ?

Yes SUNW is necessary. For example XML::Parser is SUNWperl-xml-parser
and SUNWperl-xml-parser-devel-share (later are man pages). However this
does not reflect that it's 5.8.4 XML::Parser and not 5.10 XML::Parser,
so if I let my imagination go wild, then perhaps

SUNWperl58-crypt-cbc


> Which C-Team will be reviewing this ?

That depends why you want to integrate the module. I guess that it's not
something core Solaris can't live without, so SFW gate (and c-team)
feels appropriate.


> To which consolidation does these kind of encryption packages come under ?

I'm afraid I can't answer this question. So far I thought that we can't
deliver (strong) encryption, and it's separate package (SUWNcrypto or
something like that?). But I heard that for ON and OpenSolaris this is
different. I myself would be like if someone could explain the situation
to us.


> Or let me know whom(/alias) can I contact to find these answers. This  
> info I will need when I register the package.

Generally this is appropriate alias.

Good luck!

-- 
        Vlad

Reply via email to