AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:
CFG:
PT:0
S:andy.sharp@lsi.com
RQ:
SSV:mhbs.lsil.com
NSV:
SSH:
R:<larry.scheer@lsi.com>,<brian.stark@lsi.com>
MAID:2
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 10 Feb 2010 15:06:02 -0800
From: Andrew Sharp <andy.sharp@lsi.com>
To: Larry Scheer <larry.scheer@lsi.com>
Cc: Brian Stark <brian.stark@lsi.com>
Subject: for the love of tarballs
Message-ID: <20100210150602.390033c8@ripper.onstor.net>
Organization: LSI
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Hi Larry,

I just got off another mega-conference call with IBM, joy-joy.

We have to put together a tarball of all of our source code the
involves open source, and up and deliver it to someone, somewhere,
somehow.  And put together a list of all the open source we use.  I
suspect the latter might already exist somewhere.  If you don't know
where that list might be lurking, Jonathan might have put something
together back in the due diligence days last year.

So, just a list of of the packages in our rootfs, as well as the stuff
from the tree that isn't packaged, like the kernel and samba and ldap.
And then tar all that shite up in one big tarball.  You can skip major
directories that are completely proprietary, like sm-fs and a dozen+
others, but if in doubt, just throw it in.  If it's not a directory we
ship, don't include it.  Don't include the binary packages themselves,
those can just be listed.  For packages that we modify, include the
package version in the list and the patch we apply.

I'm guessing this would take about a week?

Thanks,

a
