here you go this is a sample of my array contents for @array1
/usr/share/release_info/Solaris_8/C/S8FCSreleasenotes
/usr/share/lib/pub/UTF-8
/usr/share/lib/pub/ascii
/usr/share/lib/pub/eqnchar
/usr/share/lib/pub/greek
/usr/share/lib/pub/iso
/usr/share/lib/setterm/en_US.UTF-8/conf.file
/usr/share/lib/mailx/mailx.help
/usr/share/lib/mailx/mailx.help.~
/usr/share/lib/tabset/3101
/usr/share/lib/tabset/beehive
/usr/share/lib/tabset/hds
/usr/share/lib/tabset/hds3
/usr/share/lib/tabset/std
/usr/share/lib/tabset/stdcrt
/usr/share/lib/tabset/teleray
/usr/share/lib/tabset/vt100
/usr/share/lib/tabset/wyse-adds
/usr/share/lib/tabset/xerox1720
/usr/share/lib/terminfo/3/386AT
/usr/share/lib/terminfo/3/386AT-M
/usr/share/lib/terminfo/3/386at
/usr/share/lib/terminfo/3/386at-m
/usr/share/lib/terminfo/3/300
/usr/share/lib/terminfo/3/3045
/usr/share/lib/terminfo/3/31
/usr/share/lib/terminfo/3/3101
And here is @file2 sample content.
/usr/share/release_info/Solaris_8/C/S8FCSreleasenotes
/usr/share/lib/pub/UTF-8
/usr/share/lib/pub/ascii
/usr/share/lib/pub/eqnchar
/usr/share/lib/pub/greek
/usr/share/lib/pub/iso
/usr/share/lib/setterm/en_US.UTF-8/conf.file
/usr/share/lib/mailx/mailx.help
/usr/share/lib/mailx/mailx.help.~
/usr/share/lib/tabset/3101
/usr/share/lib/tabset/beehive
/usr/share/lib/tabset/hds
/usr/share/lib/tabset/hds3
/usr/share/lib/tabset/std
/usr/share/lib/tabset/stdcrt
/usr/share/lib/tabset/teleray
/usr/share/lib/tabset/vt100
/usr/share/lib/tabset/wyse-adds
/usr/share/lib/tabset/xerox1720
/usr/share/lib/terminfo/3/386AT
/usr/share/lib/terminfo/3/386AT-M
Basiclly what I am trying to get out of this is a quicker way to build packages for Solaris boxes. With that said the output we want is just the differences in the two files. @file1 is an array of what was in /usr prior to the compile and make install of the software. @file2 is a list of /usr after the compile ad make install. Now it would sound easier to just use "sdiff" , but the issue I have ran into is that when you run sdiff you get output that looks like this
/usr/local/lib/security/libgcj.security /us
+r/local/lib/security/libgcj.security
> /us
+r/local/lib/libisc.so.7.0.0
> /us
+r/local/lib/libisc.la
> /us
+r/local/lib/libisc.a
> /us
+r/local/lib/libisccc.so.0.1.0
> /us
+r/local/lib/libisccc.la
> /us
+r/local/lib/libisccc.a
> /us
+r/local/lib/libdns.so.11.0.1
> /us
+r/local/lib/libdns.la
> /us
+r/local/lib/libdns.a
> /us
+r/local/lib/libisccfg.so.0.0.7
And with long file names they get cut off, this sounds like it should be easy to get around, but when you are packaging large apps that have a lot of file like Perl and ISC's Bind this take a lot of leg work.
I hope that helps with what I want to do here please let me know if you need any more info.
-
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 How to display code and escape characters
are good places to start.