Norm ,
SFW cosolidation is fine. As I heard, md5 is available in SUNWperl584core package. So, It will be perl 5.8.4. Does the package get updated when perl version is updated to 5.10 ? Also, Could you send me the link where I can follow procedure to be followed to get ECCN since the package is Encryption module. Thanks Spoorthy Norm Jacobs wrote: > > Yes, since Perl seems to be migrating into SFW, it probably makes > sense to bring Perl modules into SFW with it, unless they are tightly > bound to something in another consolidation or use private interfaces > in another consolidation. John integrated Perl 5.10 into the SFW > gate earlier this week, so it should show up in build 122 and live > along side 5.8.4 until 5.8.4 can go away. Were I planning on > delivering a Perl module into Solaris any time soon, I would be > delivering it on top of 5.10 now. > > -Norm > > Alan Coopersmith wrote: >> Probably SFW, since that's where perl 5.10 is integrating and future >> perl >> modules will go, and it's not a GUI or something that otherwise belongs >> in Desktop or X. You'll want to coordinate with John Sonnenschein, >> who >> is doing the Perl 5.10 integration. >> >> -Alan Coopersmith- alan.coopersmith at sun.com >> Sun Microsystems, Inc. - X Window System Engineering >> >> Spoorthy H.S wrote: >> >>> Thanks for the info.. It would be great if anyone in the alias >>> answer me >>> on which consolidation these encryption packages should go.. >>> >>> -Spoorthy >>> >>> Vladimir Marek wrote: >>> >>>>> 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! >>>> >>>> >>> _______________________________________________ >>> sfwnv-discuss mailing list >>> sfwnv-discuss at opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/sfwnv-discuss >>> >> >> >> _______________________________________________ >> sfwnv-discuss mailing list >> sfwnv-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/sfwnv-discuss >> >
