Hi, We'd like to simplify deployment of new blades and I need to package some of proprietary libs we are using, and obviously I don't have sources for them. Can anybody point me into good direction how to make packages from binaries? I have basic knowledge about building rpms, but it seems to be source oriented. Thanks in advance -- Tomasz Napierala System Administrator Allegro Team http://www.allegro.pl/
On 8/10/07, Tomasz Napiera?a <zen at allegro.pl> wrote:> Hi, > We'd like to simplify deployment of new blades and I need to package some of > proprietary libs we are using, and obviously I don't have sources for them. > Can anybody point me into good direction how to make packages from binaries? I > have basic knowledge about building rpms, but it seems to be source oriented.For the most part, you build them the same as you do normal rpms, you just use a dummy %build section, unless you actually have to work on the files. Take a look at some of the spec files at http://dag.wieers.com/packages/ particularly the w32codec, or the acroread plugin. -- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell
Tomasz Napiera?a wrote:> Hi, > We'd like to simplify deployment of new blades and I need to package some of > proprietary libs we are using, and obviously I don't have sources for them. > Can anybody point me into good direction how to make packages from binaries? I > have basic knowledge about building rpms, but it seems to be source oriented.The process is basically the same as building from source files - except that you don't have to do anything in the %build stage - in fact you could also miss out the %prep stage if you don't need to extract files from a tar archive etc. Normally just a case of putting files where you want them in the %install stage. The 'noarch' rpms normally don't build anything - so they could be a good starting point - the crontabs spec file is a simple example - although if you are generating platform specific RPMS, you won't want the 'BuildArchitectures: noarch' line. James Pearson
On Fri, 2007-08-10 at 14:07 +0200, Tomasz Napiera?a wrote:> We'd like to simplify deployment of new blades and I need to package some of > proprietary libs we are using, and obviously I don't have sources for them. > Can anybody point me into good direction how to make packages from binaries? I > have basic knowledge about building rpms, but it seems to be source oriented.In addition, you might want to consider using the NoSource directive in your spec files so that others can benefit from your efforts without you mistakenly adding the binaries in the (N)SRPMs. http://www.redhat.com/archives/rpm-list/2004-February/msg00057.html -- Ignacio Vazquez-Abrams <ivazqueznet at gmail.com> -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.centos.org/pipermail/centos/attachments/20070811/3f5ca805/attachment-0001.sig>