Hi, On Saturday, 5. April 2008, Graham Barr wrote: > Begin forwarded message: > > Transaction: Ticket created by [EMAIL PROTECTED] > > Queue: perl-ldap > > Subject: suggestion for the position of CR character in > > Net::LDAP::LDIF entry > > Broken in: (no value) > > Severity: (no value) > > Owner: Nobody > > Requestors: [EMAIL PROTECTED] > > Status: new > > Ticket <URL: http://rt.cpan.org/Ticket/Display.html?id=34689 > > > > > > > Hello, > > > > after some testing and playing around with Net::LDAP::LDIF and the > > back_perl "database" from OpenLDAP I found that some entries will > > not be > > accepted by the latter if I use an entry (or a list of them) > > produced by > > the LDIF module. The cause of this is the "CR" at the beginning of > > each > > entry/DN and the missing empty line at the end. > > > > I know that this doesn't break RFC2849 and so is not the problem of > > Net::LDAP::LDIF. But for compatibility reasons I suggest to print the > > "\n" character not before but after each entry. This produces the same > > output as by ldapsearch and will be accepted by the perl backend from > > OpenLDAP. > > Anyone see any issue with doing this?
I don't think this should hurt. (Don't forget to add an \n to the version line as well) CU Peter -- Peter Marschall [EMAIL PROTECTED]
