In my spec files, I use the built-in macros and then, with a test account (not root) and a customized ~/. Rpmmacros, I change the default prefix: %_prefix %{_home} Works fine You can even create a test rpm database: $ rpmdb --initdb --dbpath /home/test/var/lib/rpm and put this in your . Rpmmacros: %_dbpath /home/test/var/lib/rpm %_rpmlock_path %{_dbpath}/__db.000.
In my spec files, I use the built-in macros and then, with a test account (not root) and a customized ~/. Rpmmacros, I change the default prefix: %_prefix %{_home} Works fine. You can even create a test rpm database: $ rpmdb --initdb --dbpath /home/test/var/lib/rpm and put this in your .
Rpmmacros: %_dbpath /home/test/var/lib/rpm %_rpmlock_path %{_dbpath}/__db.000.
We decided to use virtualization instead and ignore the problem. The rpmdb tip lookus useful though, thanks. – Serbaut Nov 12 '09 at 20:39 Are either of you accomplishing this sort of work with Maven?
I'm looking for someone who might be able to point me at a better tutorial for using the Maven RPM Plugin. – Brian L. Oct 25 at 15:22.
Probably a better solution anyway since running a test environment on the same machine as production is not safe/secure I guess. Note that especailly the %{? Testrel} macro is the interesting thing.
It enables you to update things simultaneously for both versions, but if you wish to keep something specific to one version or the other you still can. It also doesn't require any changes to the database, custom macros in ~/.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.