Hi,
I'm struggling with a new CentOS6 installation and turns out that mozldap tools aren't packaged anymore and all my scripts scream out loud because wraping and base64 encoding.
I've been reading lots of old petitions of adding wrapping and encoding, testing patches and trying to understand denials.
Without being a (truly) developer the only reason I can understand about not implementing this is complexity and lack of time/resources, but seems that some devs already sended patches for those modifications.
So I'm really lost: why could be wrong adding a feature that is asked again and again and will help lot of sysadmins make their life better?
I know about pipes and string manipulation, but why refusing a non default option that don't break anything?
This is specially dramatic for base64 manipulation. mozldap has(had?) a parameter (-e) that "minimize base-64 encoding of values", I don't really know how does it determines if a value should be decoded or not, but it Just Works! In my script-ldap-world i just want to display names, surnames and some description with accents (à, è,...) and some catalan letter (ç). And that's the reason I use decoding 99.99% of times. No photos, blobs or any other exotic embeded object.
So please, I mean PLEASE!
Could you add a non wrapping and a decoding option to ldap tools?
I can't pay my mortage and world if falling down, but I see the light and the end of some patches.
abosch
Angel Bosch wrote:
all my scripts scream out loud because wraping and base64 encoding.
Personally I consider using command-line tool ldapsearch to produce input data for shell scripts somewhat broken.
I think even if you're not a developer you should learn a decent scripting language and use LDAP and LDIF modules of that instead of shell scripting. Choose one available for your platform and which meets your needs.
E.g. Python scripts tend to be much smaller than comparable shell scripts. And you can implement much better error handling anyway than with shell scripts.
Ciao, Michael.
Angel Bosch wrote:
Hi,
This is the Developer's list. Your post is off topic and you should be ashamed of yourself for posting it here.
An option for LDIF wrapping was released in 2.4.24, 2011-02-10. You should be ashamed of yourself for asking for something that has already been available for over a year and a half.
Work smarter.
I'm struggling with a new CentOS6 installation and turns out that mozldap tools aren't packaged anymore and all my scripts scream out loud because wraping and base64 encoding.
I've been reading lots of old petitions of adding wrapping and encoding, testing patches and trying to understand denials.
Without being a (truly) developer the only reason I can understand about not implementing this is complexity and lack of time/resources, but seems that some devs already sended patches for those modifications.
So I'm really lost: why could be wrong adding a feature that is asked again and again and will help lot of sysadmins make their life better?
I know about pipes and string manipulation, but why refusing a non default option that don't break anything?
This is specially dramatic for base64 manipulation. mozldap has(had?) a parameter (-e) that "minimize base-64 encoding of values", I don't really know how does it determines if a value should be decoded or not, but it Just Works! In my script-ldap-world i just want to display names, surnames and some description with accents (à, è,...) and some catalan letter (ç). And that's the reason I use decoding 99.99% of times. No photos, blobs or any other exotic embeded object.
So please, I mean PLEASE!
Could you add a non wrapping and a decoding option to ldap tools?
I can't pay my mortage and world if falling down, but I see the light and the end of some patches.
abosch
De: "Howard Chu" hyc@symas.com This is the Developer's list. Your post is off topic and you should be ashamed of yourself for posting it here.
sorry for the noise, I knew this is the developer's list but after seeing all lists:
openldap-announce OpenLDAP announcements list openldap-bugs OpenLDAP bugs discussion list openldap-commit OpenLDAP source repository 'commit' list openldap-devel OpenLDAP development discussion list openldap-fortress OpenLDAP Fortress Discussion list openldap-technical OpenLDAP Technical Discussion list
I thought this belongs here because the nature of the discussion. If you want me to move this thread to another list, please let me know.
An option for LDIF wrapping was released in 2.4.24, 2011-02-10. You should be ashamed of yourself for asking for something that has already been available for over a year and a half.
I was using lastest Centos 6.3 packages and I assumed that there was no wrapping option, sorry about that. I see now that Centos is packaging 2.4.23. That was close. I'm really happy to see that it was finally included upstream and I can't wait to see it on packages.
I think rest of the complain is still valid, though. Decoding values i still an issue, and the suggestion of Michael that best way is learning other languages instead of using ldapsearch reaffirms my pov. How broken can be a simple search such as
FULLNAME=`ldapsearch -x -LLL "(uid=$1)" gecos | grep "^gecos: " | cut -d" " -f2- `
?
I really thought that we could start a healthy discussion about what and when a widely requested feature should be included. And judging from amount of posts/discussions I've found digging last weeks I'm pretty sure that isn't the opinion of a single undocumented obtuse sysadmin.
Instead of being double-ashamed because of my ignorance, I'm really proud of being part of the free software community and being able to address to people I admire and respect profundly. Even when I'm wrong and even more when I hardly find the right words to explain my boss that this "creppy guy with a violin" is the main developer of this huge project.
àngel
ps: english is not my native language, excuse my strange composition
Angel Bosch wrote:
De: "Howard Chu" hyc@symas.com This is the Developer's list. Your post is off topic and you should be ashamed of yourself for posting it here.
sorry for the noise, I knew this is the developer's list but after seeing all lists:
openldap-announce OpenLDAP announcements list openldap-bugs OpenLDAP bugs discussion list openldap-commit OpenLDAP source repository 'commit' list openldap-devel OpenLDAP development discussion list openldap-fortress OpenLDAP Fortress Discussion list openldap-technical OpenLDAP Technical Discussion list
I thought this belongs here because the nature of the discussion. If you want me to move this thread to another list, please let me know.
I really thought that we could start a healthy discussion about what and
when a widely requested feature should be included. And judging from amount of posts/discussions I've found digging last weeks I'm pretty sure that isn't the opinion of a single undocumented obtuse sysadmin.
Healthy discussion in an email list requires that all parties are first willing and able to read, before writing. You have clearly demonstrated that you ar incapable of doing either.
Every list has a charter which is displayed for you before you join. You obviously ignored that text instead of reading it.
http://www.openldap.org/lists/
Instead of being double-ashamed because of my ignorance, I'm really proud of being part of the free software community and being able to address to people I admire and respect profundly.
You are not participating in the community, you are merely injecting noise.
The words of Isaac Asimov seem apt here.
http://www.goodreads.com/quotes/84250-anti-intellectualism-has-been-a-consta...
“Anti-intellectualism has been a constant thread winding its way through our political and cultural life, nurtured by the false notion that democracy means that 'my ignorance is just as good as your knowledge.'”
Your ignorance is nothing to be proud of. Read the list charters and respect the community organization, otherwise you deserve no respect in return.
-
Angel Bosch -
Howard Chu -
Michael Ströder