On May 23, 2011, at 11:13 AM, Robert Xu wrote: > On Mon, May 23, 2011 at 08:52, Jeff Johnson <n3...@mac.com> wrote: >>> $ cvs diff -u -r0 -r1.1 suse.in >>> --- /dev/null 2011-05-23 14:22:00.000000000 +0200 >>> +++ suse.in 2011-05-23 14:23:41.823771836 +0200 >>> @@ -0,0 +1,378 @@ >>> +%distribution @RPMCANONVENDOR@ Linux >>> +%vendor novell >>> +%bugurl http://bugzilla.novell.com >>> +%disturl http://software.open@RPMCANONVENDOR@.org >>> +# >>> +# Below is the rpm-suse_macros contained in rpm-4.9.0-122 (Build factory) >>> +# _suse_install_post is defined in macros.brp in the brp-checks-suse >>> +# rpm >>> + > > And I was just patching the macros.in of RPM5 to use this... OK, that > saves me some trouble and allows me to just use --vendor=suse for > that. >
In general, its gonna be easier to exchange info if you
build @rpm5.org code from cvs, not from tarballs and patches.
We do monthly releases, tick,tock, next release of rpm-5.3.whatever is on
June 1st, and likely rpm-5.4.1 will also be attempted this month.
So the starting point (rpm-5_4 is "development", rpm-5_3 is "production",
rpm-5_2 and rpm-5_1 are "legacy" branches) is
cvs -d ':pserver:anonym...@rpm5.org:/v/rpm/cvs' get -r rpm-5_4 rpm
See rpm/INSTALL.developer to get oriented on what to do next.
Your workflow SHOULD be something similar to
cd rpm
./devtool checkout
./devtool opensuse
... install build pre-requsites and/or adjust the %opensuse build
options ...
make
cd tests
make clean check
Post any patches and or questions here and I can likely help instantly because
I will have sufficient context from cvs to answer precisely.
I can also easily send along "rpm -qa" from my opensuse VM if
you need help finding build prerequsites (I forget when I set it up, last
October
iirc).
Finding out all the vendor deranged package names always takes longer than than
any other chore (for me).
hth
73 de Jeff
smime.p7s
Description: S/MIME cryptographic signature
