Textmate Rpm Spec File

The following are some example.spec files I created to demonstrate how to deal with a more recent libudev version and the different naming of libcrypto on Fedora, via the use of compatibility symlinks. I do this in post install for maximum compatibility as the resultant rpms could also be used on systems where libudev and libcrypto naming matches what Opera expects.To fetch all the.spec files: git clone the version of Opera you wish to repackage in your sources directory (usually /rpmbuild/SOURCES). Tweak the Version field in the.spec file(s).To repackage Opera stable: rpmbuild -bb opera-stable.specTo repackage Opera beta: rpmbuild -bb opera-beta.specTo repackage Opera developer: rpmbuild -bb opera-developer.specNote: I have only done limited testing on the most recent versions of Fedora, OpenSUSE, PCLinuxOS and Mageia.

I'm trying to write a single rpm spec for RHEL/CentOS/SL 5 and 6. This spec is for python app, so there is no differences in build process. But on RHEL/CentOS5 I need to add one additional dependen. Apache-archiva, 2.2.4, The Build Artifact Repository Manager. Buildifier, 3.0.0, Format bazel BUILD files with a standard convention. Buildkit, 0.7.1. Pkgdiff, 1.7.2, Tool for analyzing changes in software packages (e.g. RPM, DEB, TAR.GZ). That lack it. Rmate, 1.5.8, Edit files from an SSH session in TextMate.

This is stupid but I have no choice, what I have is single folder with 6 subdirs full of files. What I need to do create a tar file and slap this tar file into an RPM so when the RPM runs it takes the tar and untars it to a folder of my choice (which I'll set in the spec file).Is this possible? Or is this stupid? The RPM doesn't need to make or build or do anything but extract the tar file. I've told the boss we should merely give them a tar but nope I have to build a RPM (- View image here: -?)So I've been trying to get rpmbuild working on a SUSE Enterprise server this morning. So far I've got it building a package.src.rpm which when I run extracts a tar file. You need to use $RPMBUILDROOT env variable%prep%setup -n CSFixcd /usr/src/packages/SOURCEStar -xvf CSFix.tar.rm CSFix.tarmkdir $RPMBUILDROOT/opt/testcp -R CSFix $RPMBUILDROOT/opt/testcd $RPMBUILDROOT/opt/test/CSFixchown -R root.root.chomod -R a=rX,g-w,o-w.also in the%files macro you can control permissionsdefaultattr(root, root, 777), something like that, I don't have a spec file handy to check it on.

PC Pitstop - PC Performance RootsPC Pitstop began in 1999 with an emphasis on computer diagnostics and maintenance. Using Microsoft’s Internet Explorer along with ActiveX technology, we could provide free diagnostic and maintenance tools that didn’t need to be installed. As times changed and PC Pitstop grew, we transitioned to a software subscription model to not only provide better and more secure diagnostic and maintenance tests, but turn our focus towards computer security with PC Matic. During the early days of the dot com boom, our online PC maintenance tools were skyrocketing.

You need to use the%files area though, it makes your rpm uninstall correctly. Originally posted by Otterz:You need to use $RPMBUILDROOT env variable%prep%setup -n CSFixcd /usr/src/packages/SOURCEStar -xvf CSFix.tar.rm CSFix.tarmkdir $RPMBUILDROOT/opt/testcp -R CSFix $RPMBUILDROOT/opt/testcd $RPMBUILDROOT/opt/test/CSFixchown -R root.root.chomod -R a=rX,g-w,o-w.also in the%files macro you can control permissionsdefaultattr(root, root, 777), something like that, I don't have a spec file handy to check it on. You need to use the%files area though, it makes your rpm uninstall correctly.ooooh awesome thanks.The%file is correct, I've tested it on a SUSE box and it worked fine (very surprised that it did) So I'm wondering if the /./ was misleading? I was looking in it on an Ubuntu box's archive managerFrom memory a cat of the.tmp rpmbuild file the $RPMBUILDROOT was being set.Anyway your suggestion are very nice, I'll use that or something like that for the beta build next week. I need to fix the file perms and owner anyway!Cheers!