rpm has a design fault that causes it to fail to allow packages larger than 2 gigs (or 8gb, I think, depending on the version of rpm/cpio).
FPM can solve this.
My current proposal is to split the data up into chunks (smaller than the limit), putting each chunk into an rpm by itself, then producing a metapackage that requires all of the chunk packages and includes a post-install script that re-assembles the chunks. Should also include a pre-uninstall script that removes the assembled stuff.
The idea is that you end up with a few RPMs:
mypackage.rpm
mypackage-chunk0.rpm
mypackage-chunk1.rpm
...
mypackage-chunkN.rpm
And you just 'yum install mypackage' and just does the right things to get your large package installed.
rpm has a design fault that causes it to fail to allow packages larger than 2 gigs (or 8gb, I think, depending on the version of rpm/cpio).
FPM can solve this.
My current proposal is to split the data up into chunks (smaller than the limit), putting each chunk into an rpm by itself, then producing a metapackage that requires all of the chunk packages and includes a post-install script that re-assembles the chunks. Should also include a pre-uninstall script that removes the assembled stuff.
The idea is that you end up with a few RPMs:
And you just 'yum install mypackage' and just does the right things to get your large package installed.