Suggestion: If you're going to send patches with new features - make the patches for HEAD, not for 2.0.X - this feature, if it were to get in this form AT ALL would not get in to 2.0.X. With regard to the actual patch: you just eject the cdrom w/o asking - that could have negative effects if a user was not expecting it. Why not just prompt the user and let them prepare the next media - that way you're not bound to cdrom/dvd. If someone is loading the units off of compact flash or floppy disk or zip drive, then the code would be more generic and more well-suited to them. Also - why not have yum-arch take multiple disks when you tell it to talk to removable media? Then you can have 1 repository for all N disks. So the header.info ends up looking like: 0:name-1.1-1.i386=DISKLABEL/path/to/name-1.1-1.i386.rpm then have tag the repo as removable in yum.conf [redhat9fromcd] name = Red Hat Linux 9 from CD baseurl=removable:///mnt/cdrom/ Then have it look at the disklabel - if it is not the one it needs then it asks for a new disk. If all the disklabels are the same then you have a problem, clearly, but then so does your vendor :-D -sv
