[petsc-dev] I hate nagupgrade

[Jed Brown]

Barry Smith <bsmith at mcs.anl.gov> writes:
>    I don't understand? Is there a bug in the current code? If the user
>    has write access to the $PETSC_DIR directory it will print a nag at
>    most once every 24 hours. 

I think Karl is saying that new installations are typically up-to-date
or the user explicitly chose a different version (like picked an old
tarball on the website).  Connecting to the server to check whether to
nag is superfluous at that stage.  Later (on recompilation or building
user code), the nagging is relevant, but I don't think it's worth the
side-effects.

>    Otherwise it will print a nag every time they do a make with the
>    PETSc makefiles. Is it not working for you?

Is it useful to nag every time when PETSC_DIR is not writeable (like a
system install)?  That seems annoying, is that what happens?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20141112/70477ab4/attachment.sig>