<quote who="Silcock, Stephen">
> That looks like acceptable behaviour to me; the script was looking for a
> file that wasn't there and it told you exactly that. When you put the
> file back (or a dummy one at least) it worked OK. What exactly about the
> process do you not think is robust?
The file was in the target state (deleted). The script (and thus the package
management system, because it will put this package in a broken state)
should not b0rk because it is unable to delete a file that is "already not
there".
- Jeff
--
"In addition to these ample facilities, there exists a powerful
configuration tool called gcc." - Elliot Hughes, author of lwm
--
SLUG - Sydney Linux User Group Mailing List - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
