Re: Rawhide development process

2001-01-08 Thread Edward S. Marshall
On Sat, 6 Jan 2001, R P Herrold wrote: > ... or run the 'mirror' package, and a mirror, and look at the > (perhaps weekly-- as I recall the RawHide archive is freshened > on Fridays) mirror run report, which lists each new package as > it is pulled in, and optionally deleted off ... Combine that

Re: Rawhide development process

2001-01-06 Thread db
> ... or run the 'mirror' package, and a mirror, and look at the > (perhaps weekly-- as I recall the RawHide archive is freshened > on Fridays) mirror run report, which lists each new package as > it is pulled in, and optionally deleted off ... Thanks for the idea. (duh). I've always done this

Re: Rawhide development process

2001-01-06 Thread R P Herrold
On Sat, 6 Jan 2001, db wrote: > Or is it more of "query the rpms yourself" to > find out what the current development status is. ... or run the 'mirror' package, and a mirror, and look at the (perhaps weekly-- as I recall the RawHide archive is freshened on Fridays) mirror run report, which lis

Rawhide development process

2001-01-06 Thread db
I'm probably not looking in the obvious places, but is there a running changelog for the current rawhides? (Like: "01/06/2001: updated to 2.4.0 proper from -test12", etc.). Or is it more of "query the rpms yourself" to find out what the current development status is. I like the comments that so