Sorry I'm a Perl programmer and a dam good one :-). I never drank the Python Coolaid and I don't think I ever will. I fundamentally dislike the language its too fragile in the name of enforcing "better code formatting practices". Franky I've seen many a Python script that was just as bad and ugly as the worst Perl scripts I've seen. Perl has served me well even though its not as popular right now. On Tue, Feb 11, 2014 at 10:27 AM, Rich Megginson <rmeggins@xxxxxxxxxx> wrote: > On 02/11/2014 08:16 AM, Paul Robert Marino wrote: >> >> I would have no problem doing that. >> The more I look at it I may just use it as a template for creating a >> new set of Perl based replication management tools. > > > Part of the reason for dropping mmr.pl is Perl :P > > We have a new project for creating a management framework, including > replication management, in python. > http://port389.org/wiki/Upstream_test_framework > It started out as the basis for a test framework, but it is now separate > (lib389). > > If you are planning to do something from scratch, and you can hack python, I > suggest you take a look. > > >> >> >> >> Ive also been thinking of some other tools I would like to make in >> addition. >> for example I would like to make a password integrity check hook >> script for Heimdal Kerberos which would utilize 389 servers password >> change functionality that way 389 server can manage the password >> policy but in addition programs which don't use SASL but instead use >> the users password field for authentication can function without >> having to put the Kerberos database in the LDAP server. >> >> Ill send out an email to the user list once I create the github repo >> >> On Mon, Feb 10, 2014 at 11:09 AM, Rich Megginson <rmeggins@xxxxxxxxxx> >> wrote: >>> >>> On 02/09/2014 02:29 PM, Paul Robert Marino wrote: >>>> >>>> I just noticed on the wiki that it says mmr.pl is deprecated because >>>> its "it is too buggy and has no maintainer" >>> >>> >>> There is no dedicated source code repo for it. >>> There is no place to file bugs/tickets against it. >>> There is no one to fix the bugs/tickets. >>> >>> >>>> I'm just curious if there is a punch list of the bugs I might be >>>> willing to tackle them if so. >>> >>> >>> Not that I know of, just various emails/irc messages over the years. >>> >>> >>>> Ive always found it to be a useful tool >>>> and I prefer not to click my mouse a hundred times when a command line >>>> script could do the job. >>>> I'm not saying I would definitely be willing to become the maintainer >>>> on a long term basis because I have too many project on my plate as it >>>> is, just that I would be willing to take some time to do any updates >>>> and bug fixes as I have time and possibly be willing to act as an >>>> temporary maintainer for a brief period of time. >>>> >>>> The code is fairly strait forward and at the least I could make the >>>> option parsing a lot more robust and the error messages far more >>>> helpful. >>>> The coding style is outdated and could use probably prototyping on the >>>> subroutines. >>>> Further more it might be useful to accept a config file and or >>>> environment variables for some of the information for example I hate >>>> putting passwords on the command line. >>>> I can also see that there are a lot more options that would be nice to >>>> be able to tune. >>>> but if there is a bug list I would be happy to spend some time on it >>>> and see how many I could run through in a short period of time. >>>> A quick search of bugzilla.redhat.com didn't seam to show any thing as >>>> far as I could tell >>> >>> >>> It would probably be easiest to make a github repo for mmr.pl and use >>> that >>> for tracking changes, bugs/tickets, documentation. >>> >>>> -- >>>> 389-devel mailing list >>>> 389-devel@xxxxxxxxxxxxxxxxxxxxxxx >>>> https://admin.fedoraproject.org/mailman/listinfo/389-devel >>> >>> >>> -- >>> 389-devel mailing list >>> 389-devel@xxxxxxxxxxxxxxxxxxxxxxx >>> https://admin.fedoraproject.org/mailman/listinfo/389-devel >> >> -- >> 389-devel mailing list >> 389-devel@xxxxxxxxxxxxxxxxxxxxxxx >> https://admin.fedoraproject.org/mailman/listinfo/389-devel > > > -- > 389-devel mailing list > 389-devel@xxxxxxxxxxxxxxxxxxxxxxx > https://admin.fedoraproject.org/mailman/listinfo/389-devel -- 389-devel mailing list 389-devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-devel
