[petsc-dev] broken builds

Matthew Knepley knepley at gmail.com
Tue Aug 30 14:47:56 CDT 2011


On Tue, Aug 30, 2011 at 7:38 PM, Jed Brown <jedbrown at mcs.anl.gov> wrote:

> On Tue, Aug 30, 2011 at 14:34, Satish Balay <balay at mcs.anl.gov> wrote:
>
>> All --download-package=reinstall can do is install the new one over
>> the old one. This can can still break if the new one doesn't
>> completely overwrite the old one.
>>
>
> Installing without keeping a log of exactly what was installed is totally
> the wrong model. All package managers have a manifest and can remove
> packages. PETSc should be able to do that too (eventually).
>

Right. This model ONLY works if you control all the packages. We don't. We
use other people's crusty stuff, and if you think
rm -rf does not scale, try managing all these packages yourself. It will
make you as big an asshole as the guys at Debian.

   Matt

-- 
What most experimenters take for granted before they begin their experiments
is infinitely more interesting than any results to which their experiments
lead.
-- Norbert Wiener
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20110830/3729a887/attachment.html>


More information about the petsc-dev mailing list