Praise teh sed

Since my talk with Robin on Thursday regarding the autogenerated userinfo.xml, I finally found some time today to get all the info’s I need out of userinfo.xml.

Since I don’t really want to manually enter all those mail addresses from userinfo into LDAP manually, I figured sed might be my best friend. *BUT* sed ain’t easy .. But thanks to Fabian and Gilles, I learned something new about sed today ..

Basically I searched for a way to transform userinfo.xml into a datafile for ldapedit.

As most of you know, userinfo.xml would look like this:

So the first step would be to simply use egrep on userinfo.xml to filter only the things I needed ..

That looks more like a processable list to me. Now I only needed to convert the into dn, the into mail and be done with it.

This is what I applied on top of the above filter:

And that’s it, I just need to check the dn’s for all the users, and when I’m done with that, finito!

2 thoughts to “Praise teh sed”

  1. Hope this isn’t a repeat; my first attempt to post failed.

    It shouldn’t be necessary to combine grep and sed this way. sed can do the grep part, which will save you a pipe and some time and effort if you do this command over a large file or group of files.
    I might have this somewhat wrong, but you could put those commands in an external file called userinfo.sed, and invoke it with the -f flag; something like:

    userinfo.sed:
    ,(username=|),{
    s/.*$/,ou=devs,dc=gentoo,dc=orgnadd: mail/
    s/.*/mail: /
    ,,d
    , ,d
    }p

    sed -nf userinfo.sed userinfo.xml

    On the other hand, sed is not usually the best choice for modifying xml. Far from it, in fact. XSLT was built for mangling xml and does it much more consistently and reliably than sed ever will. I’m not prepared to give an example of doing this transformation with XSLT at the moment, but I guarantee it’s the right way to go here.

  2. Mmkay, try this xslt:

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.