I have this part down... I know how to add new CD's, and how to
give them meaningful names.
http://www.linux-mandrake.com/en/demos/Spotlight/RpmDrake/
It is pretty clear about how things are SUPPOSED to work.
The thing is, rpmdrake on my system DOES NOT work this way.
It lets me insert the CD and give it a new name. Then it acts as
though it is rebuilding the database of available packages, but
when the "available to install" package tree comes up,
it is EMPTY.
Thanks for the thoughts, though...
Yeah, I found out about the kicking back CD's if the wrong one
was inserted, but, I still wanted it to ask for a meaningfully named
CD. For that matter, I think it would be a great feature upgrade to
allow the user to see which CD the item was on, so that if you
didn't have the full set of CD's, you wouldn't have to try adding
a package to see what disk it was on.
What I really want to know, is how to put the original library back,
since obviously the database was pre-existing as it contained the
options for a 4 CD set when I only had 2 CD's in my set.
Kevin Bulgrien
At 11:42 AM 9/26/00 -0400, you wrote:
>Kevin,
> Errors I have made suggest a couple of possibilities for you. Pardon
>that I present scenarios rather than give exact answers. I don't know the
>exact answer, but perhaps something here will suggest a solution. I hope
>others on this list will also answer because I'm sure that there is a lot
>that I'm overlooking.
>
> If/when you do reinstall Linux, when adding RPM to the database of
>available packages (in RPMDRAK-configure (new)CD) it will kick a suggested
>name up before it rebuilds the CD database. Edit this box to a title more
>meaningful to you, the new name will be used in the future.
> Since there is nothing otherwise wrong with Linux, in RPMDRAK configure
>each CD again, using a more meaningful name. RPM programs available on each
>disk you do this for will be listed twice, but one will have a meaningful
>name.
> If you select an RPM package to install, stick in disks one at a time
>when it asks for a disk (assuming that you don't know exactly which disk it's
>asking for). If the disk you insert is the wrong one it will kick it out and
>ask again. When you find the one that works you now know it's ID and can
>write it on the jewelcase you store it in (I understand writing on the CD is
>a "no no"). -Gary-
