> How do you correctly handle issues like the recent package rename of > apache (net-www -> www-server) under paludis. I'm guessing that in > portage some kind of update gets applied to the database so that the > change is transparent. With paludis I'm getting errors about the > package being present in world but not existing.
Once I figured out what had happened (no being tuned into wheverver the announcement was made) I just put a symlink in net-www, pointing to www-server. I suppose that will persist until the next paludis -s. One could have a script run after the sync to handle all of these tasteless little fix-ups, no? Paludis uber goober, Chris _______________________________________________ paludis-user mailing list [email protected] http://lists.pioto.org/mailman/listinfo/paludis-user
