Beefy Boxes and Bandwidth Generously Provided by pair Networks
Your skill will accomplish
what the force of many cannot

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??
Monks, I'm installing ImageMagick from source on a large number of machines. I have everything automated, except there's a small tweak to /etc/ that I am still doing by hand. I was just wondering if there was a way to automate that away as well.

This install from source and tweak /etc/ process is something I have to do for a number of dependencies, not just for imagemagick, so I will wind up with a number of scripts that look kind of like the one below.

So basically I need to add a line to a conf file, but I shouldn't add it if it's already there. I can think of many ways to do it, but wonder if there's one way that is particularly sweet and easy... you know... a one liner :)

I'm thinking perl, but if there's a way to do this with bash or sed or howsoever, fine with that as well.

As a bonus, here's my automated install of ImageMagick. If anybody has comments or improvements, fire away.

Oh, and before suggesting to me that I do "apt-get -y install perlmagick", that won't work for me in my situation, because it's a locally installed perl in a delicate state.

cat #!/bin/bash su -c '( # uncomment the following line if you need to get the file #wget ' +.0-5.tar.gz' tar -xzvf ImageMagick-6.3.0-5.tar.gz cd ImageMagick-6.3.0 ./configure make make install cd - rm -rf ImageMagick-6.3.0 )' 2>&1 | tee installImageMagickOut.txt echo " ***************************************************************** image magic should be installed from source. now let's test if perl -MImageMagick works you may get errors about a missing .so file if this happens, try doing ( updatedb; locate; ) then change /etc/ to include the directory containing that f +ile then do ldconfig and try again ***************************************************************** " /usr/local/path/to/custom/perl -MImage::Magick -e ''
UPDATE: Thanks to mk for putting me on the right track :) Her solution was good, but it inserted lines rather than tacking them on at the end, which bugged me aesthetically.

I played around with her solution and some other ideas, and finally have something that I like. In the end, a combinatino of bash and perl seemed like the most natural solution to me. Hope this isn't too much of an obfu :) :

UPDATE 2: (deleted update 1) For those that still care, VSarkiss pointed me towards a less boneheaded way of doing this. My final result:

$ cat #!/bin/bash ./ if [ ! -f /etc/ ]; then echo /usr/local/lib >> /etc/ ldconfig fi result=`/usr/angebote/perlroot/bin/perl -MImage::Magick -e ''` if [ -n "$result" ]; then echo result: $result exit echo "seems there was a problem configuring shared libraries for imag +e magick running /usr/angebote/perlroot/bin/perl -MImage::Magick -e '' r +esulted in error $result if you got an error about a missing .so file, try doing ( updat +edb; locate; ) then change /etc/ to include the directory containing + that file then do ldconfig and try again " fi $ cat #!/bin/bash # if we aren't reading from the subdir, start doing so # if the result of the grep is a zero length string config_from_subdir=`grep 'include /etc/\*.conf' /etc/ld.s +o.conf`; if [ -z "$config_from_subdir" ]; then echo 'include /etc/*.conf' >> /etc/ fi mkdir -p /etc/ $

In reply to quick way to add a line to a file, if it's not already present (automating tweaking of /etc/ for installing Image::Magick) by tphyahoo

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (3)
As of 2022-05-26 05:48 GMT
Find Nodes?
    Voting Booth?
    Do you prefer to work remotely?

    Results (93 votes). Check out past polls.