On 3/8/07, Chris Frey <[EMAIL PROTECTED]> wrote: > > I've tested the build on a RHEL4 system just now, and rpm-4.3 chokes > on the %if statements for some reason. I also had to tweak the autoconf
I have a CentOS4 system (server parts only) and see that it's even more dumb than I thought; a new patch is on the way, I made the initial macro definitions as lowly basic as possible, which makes it a lot more portable. Basically RHEL4 doesn't know an empty macro definition is '0', unlike newer systems. OK tests on my FC6 box and a CentOS4 box, all working for the basics. Patch #1676900 against CVS. > I didn't like the barry base package, as it seemed a bit wasteful to me, > and we need the license in every package anyway. Since libbarry is > really the common package that all the others depend on, I've moved > the common documentation files there, and moved some of the more techy > ones into libbarry-devel. Coolness - I was a bit on the "well what do I do?" front as well about that whole point, whatever is cleaner and works out. I thought having to install 'barry' to get 'libbarry' was lame myself... :) BTW: the second paragraph of %description -n libbarry now goes over the 80char boundry, you should hard wrap it after "You most" and yank up the following line. Makes the display of rpm -qi(p) pretty. -te -- some live, some die in the way of the samurai ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
