On Dec 16, 2010, at 1:13 PM, Eric MSP Veith wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Heya, > > On Thursday 16 December 2010, Jeff Johnson <[email protected]> wrote: >> There's a minor issue with an unexpanded AutoFu macro on head >> and the rpm-5_4 branch. > > oops, sorry, my fault. Forgot to commit that file. :-( >
;-) Happens all the time, no worry. > Is there a good way to get a terse output from CVS on what has changed? I.e. > not as convoluted as "cvs status" is? > cvs -n up My only usage case for "cvs status -v" to discover branch names. Sticky versions/dates are displayed with status, but those get tricky too. >> I still dunno what you are doing with Ruby AutoFu and s >> I don't quite know what is needed. > > I've ripped out all the Ruby guessing AutoFu as we decided in another mail > thread. Putting the nonstandard Ruby include dirs into CPPFLAGS should not > be a problem for packagers. I'll put a notice in the INSTALL file and that's > it. > > Perhaps I'll introduce a --with-ruby-inc-dirs switch sometime. I couldn't > help but notice that the Python part takes great care to detect all possible > versions of python and all not-so-standard paths. Is that becoming a > candidate for ripout too, because it introduces a build-time dependency on > Python, too, just as it would with Ruby? > Python was just first, doesn't mean correct. Yes the python AutoFu is all rather Baroque'n for hysterical reasons, nothing else. Keep it KISS: AutoFu is annoying to maintain. >> What I would do is on the rpm-5_3 branch (but we differ >> between targeting riby-1.9.x or not). > > Yep, keep it clean. The code I produce currently (i.e., bindings) will be > tested with 1.8.7, too. Embedded Ruby is a completely different beast... > It's on my TODO list, too. > Good. BTW, you might want to also check-in your changes on rpm-5_4 (and perhaps on rpm-5_3 but check w Per Oyvind first). No hurry, but rpm-5_4 and rpm-5_3 end up getting snapshots and monthly releases, unlike head. 73 de Jeff ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List [email protected]
