> ... 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 with the updates/...
directory using mirror. Should work fine for rawhide too.
> a 40G IDE ($99 on sale at CompUSA last week) is another
> approach.
4 x 20-gb IBM's on 3ware 4port IDE RAID. 80gb at +/- 60mb/s. :-) Plenty
of room to spare.
> Sourceforge mirrors are your friend (one can get in ...).
> Doing mirroring from cron at night from midnight to 8 am keeps
> my office mirror dialup link busy without impairing daytime
> connectivity.
ftp. and ftp2.Sourceforge seem to be only giving me about 150-200kbps these
days. I wonder when they will be completing their upgrades and migration to
exodus. (Or is it an exodus to exodus? :-). My @home service just finished
an upgrade cycle, so I've got 3 meg/second left to saturate until they sign
up more customers.
Is there an easy way to create a global dependancy tree of all the rpm
packages? Because what if I only wanted 25% of the rawhide rpms (for new
features), but liked 75% of my rh7.0 rpms because of stability? It would be
nice to know what versions were required by that 25% so I could make the
easy tradeoffs. Some kind of visual tree format would be cool, heard of any
tools like that?
Dan Browning, Cyclone Computer Systems, [EMAIL PROTECTED]
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
