I recently downloaded at last chromium svn (bloody 2.5GB of data), i can succesfully build it for both architectures, how can i pack it into an rpm file?
I build it with make -r -j4 chrome BUILDTYPE=Release, the output goes to a folder out/Release/ , in that folder i’d like to omit the obj/ folder (lots of files, size of hundreds of MiB). How can i make an rpm from that?
I’d like to publish it for people to test out the chromium build but i don’t know at all how to build bloody rpm or spec file. Any help would be appreciated please.
If it will ease it up i could create an rpm file for those depot tools if you want. Where would you like them to be installed on the system?
I know it’s a bit against “normal” builds but i guess it will be faster than to write extensive spec files for those depot tools. I could create an rpm file for source too, just tell me where should they be installed after rpm -i on OBS.
I’ve been using check install for a while, … and never noted that set of arguments before. Neat. I’ll have to try it.
A caution on the rpms built by checkinstall. Overall, they are not as good as rpms created the long way (which I do not know how to do) and you could read of people struggling with the checkinstall created rpm. Checkinstall tends to be best with rpms on one’s own PC.
I use checkinstall, so I can copy it to other PC’s on my LAN (where I keep the same configuration across all PCs) and if I have to do a re-install (rarely happens) than I do not have to rebuild … I just pull out the rpm I created for myself.
Well the thing is oldcpu, that while i built succesfully the browser i had no makefile to “make install”, so i was left with already built files which i can use and other people. So what i did is i put those built files where i’d like them to be after normal rpm installation, created the desktop file, symlink to exececutable. So while building may fail at all i can always add custom files/directories for it to be included in the rpm file (thanks to --inspect). So while normally the output of building chromium was in /home/<user>/Programs/chromium/src/out/Release/ i just copied it to /opt/google/chrome/ and then with --inspect i added it to the files that will be included in the rpm and --exclude=/ excludes every file from being included into rpm BUT i will include the directories myself won’t i :)??
So in practice i can make an rpm out of any file/directory, i just need one package that contains a Makefile to be able to invoke make because without that i can’t create rpm from the file/directory
Ok I finally have it build by hand, there is a lot of prep work to do
including install of the 32bit versions of some rpms and creating
softlinks to the libraries as per their script. Having to do that and
the softlinks for the fonts pretty well excludes it from using the OBS
at the moment as far as I can see
That being said, I’m goinf to build a new 64bit 11.1 machine and run a
further test to see if I’ve missed anything and document the build
environment I used. Then it’s just a matter of updating the source,
bzipping it, dumping in /usr/src/packages/SOURCES along with a spec
file and it should be good to go…
You just need to rename the Release directory, add the Author and
License file directory before bzipping it up.
Since it’s only the build file and other bits and not the true source
(2+ GB) I think you should write a short text file on how you built it
on your machine and the add to the Release directory before bzipping,
then update the %doc part of the %files section with the name so it
gets added to your rpm.
The whole build process could also be automated via a cron job to
update the source, build a new release, copy files, bzip and build the
rpm as well which may be worth looking at
Note technically, I think someone could ask you for your build
environment source as well, but that is unlikely…