On Fri, Dec 07, 2012 at 05:02:26PM -0500, PJ Eby wrote: > If the packages have files in conflict, they won't be both installed. > If they don't have files in conflict, there's nothing important to be > informed of. If one is installing pexpect-u, then one does not need > to discover that it is a successor of pexpect. In the specific case of pexpect and pexpect-u, the files don't actually conflict. The pexpect package includes a "pexpect.py" file, while pexpect-u includes a "pexpect/" directory. These conflict, but not in the easily detectable sense. -- Andrew McNabb http://www.mcnabbs.org/andrew/ PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4