Sometimes it will be necessary for module library creators to re-run the setup script. In this case they will have to type the name of their repository again. Is there a way for the script to determine an existing package name if the script has been run before? This would be convenient, and also help to prevent weird errors from occurring if the user doesn't type the name exactly the same.
I think it could check to see if there is a DESCRIPTION file, and if there is, the package name could be extracted from it so the user doesn't need to type it. @gsrohde do you think that would work?
Sometimes it will be necessary for module library creators to re-run the setup script. In this case they will have to type the name of their repository again. Is there a way for the script to determine an existing package name if the script has been run before? This would be convenient, and also help to prevent weird errors from occurring if the user doesn't type the name exactly the same.
I think it could check to see if there is a
DESCRIPTIONfile, and if there is, the package name could be extracted from it so the user doesn't need to type it. @gsrohde do you think that would work?