On 11.02.2025 10:40, Rolf Turner wrote:
On Mon, 10 Feb 2025 21:55:07 +
Bernd.Gruber wrote:
Hi,
I have a quick question. I have an older package (dartR) that is now
superseded by a series of new packages.
Still we noticed that several users have not updated yet and moved to
the new pac
If as your install page says, there are only trivial differences in the
code that uses the old and new packages, why force people to reinstall by
disabling their code with what you term a shell? Surely a package startup
message would be enough, and better than disabling your users' previously
(hop
On Mon, 10 Feb 2025 21:55:07 +
Bernd.Gruber wrote:
> Hi,
>
> I have a quick question. I have an older package (dartR) that is now
> superseded by a series of new packages.
>
> Still we noticed that several users have not updated yet and moved to
> the new package. Hence the question:
>
>
Does the old package give incorrect results? Or does it just give slower
results? What makes the new one better?
Unless the old one is actually wrong, as a user, I would be unhappy with it
being replaced by a shell. I have this obsession with reproducibility. So,
if you force me to change to the n
Hi,
I have a quick question. I have an older package (dartR) that is now superseded
by a series of new packages.
Still we noticed that several users have not updated yet and moved to the new
package. Hence the question:
Is it okay to submit a "shell" package under the name of the old package t
