Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is the desired behaviour for addOldPackage() when it creates duplicates? #47

Closed
andrie opened this issue Dec 13, 2014 · 4 comments
Closed
Labels
Milestone

Comments

@andrie
Copy link
Owner

andrie commented Dec 13, 2014

Right now, this function creates a duplicate and throws a warning

This may leave the repository in an inconsistent state.

Should we remove the duplicate?

@andrie andrie added this to the Version 0.1-2 milestone Dec 13, 2014
@achubaty
Copy link
Collaborator

achubaty commented Dec 14, 2014

The way I use it is to warn the user and allow them to remove the version of their choosing manually. Perhaps the best behaviour should be to automatically prompt the user to remove one of the versions.

@andrie andrie modified the milestones: Version 0.2.2, Version 0.2.0 Jan 28, 2015
@andrie andrie modified the milestones: Version 0.2.3, Version 0.2.2 Mar 26, 2015
@sebastian-c
Copy link
Contributor

One of the reasons I'm not using miniCRAN is because it doesn't allow archiving of packages as CRAN does. Could archiving be a solution to the duplicate problem?

@achubaty
Copy link
Collaborator

achubaty commented Jun 6, 2017

@sebastian-c I agree that archiving (see also #80) may help here. Not sure how soon I'll be able to build this.

@andrie
Copy link
Owner Author

andrie commented Jun 29, 2019

I agree that archiving is a better solution.

@andrie andrie closed this as completed Jun 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants