| 1 |
On Saturday 23 September 2006 22:36, Ciaran McCreesh wrote: |
| 2 |
> How would it know what other files are required? For example, if |
| 3 |
> libexpat.so.0 were to rely upon /usr/share/expat-0/config , how would |
| 4 |
> the package manager know not to clobber that file? Or are you |
| 5 |
> suggesting leaving (or reparenting, if you prefer) all a package's |
| 6 |
> files, not just the .so files? |
| 7 |
|
| 8 |
i'm talking about just libexpat.so.0 ... keep the file around long enough to |
| 9 |
update the system |
| 10 |
|
| 11 |
> Or a related question: what proportion of breakages will be fixed |
| 12 |
> merely by keeping .so files and nothing else around? Will implementing |
| 13 |
> this prevent enough breakages to make it worthwhile? |
| 14 |
|
| 15 |
of course it will when you look at core things like openssl, acl, openldap, |
| 16 |
etc... if you remove anyone one of these packages completely, you risk |
| 17 |
breaking everything (coreutils and many system packages use libacl) or all |
| 18 |
your network capabilities (sshd/ssh no longer usuable; now you require |
| 19 |
on-site service to fix ... hopefully you have packages cached cause wget no |
| 20 |
longer works either) |
| 21 |
-mike |
Archives