conda-forge.github.io
conda-forge.github.io copied to clipboard
Tools + Docs: Renaming of feedstocks
It is currently relatively complex to rename a feedstock. It would be great if that were made simpler through tooling and documentation.
https://github.com/conda-forge/dec2-feedstock/issues/1
Any particular place you want this in the docs? My hope is that I can write something, which will most likely be wrong, and everyone can correct it to something that works.
@CJ-Wright - you could definitely put together a PR for docs at https://github.com/conda-forge/conda-forge.github.io/tree/master/src. I'm definitely up for documenting this wart, and then we can look at streamlining the process after.
Ok, @pelson do you mind assigning me so I can keep track of this issue? A PR is on its way.
Cleared you @CJ-Wright as the doc PR went in. Though if you are wanting to do more here, by all means feel free to.
That's fine.
@viniciusdc I see this has recently been added the Docs label. I know some work was done here in #420. Apparently some more work could be done as per https://github.com/conda-forge/conda-forge.github.io/pull/420#issuecomment-324423199. Please, assign me to look into this.
We no longer rename feedstocks. Instead we archive them and create a new feedstock with a new name.
Okay @beckermr
We no longer rename feedstocks. Instead we archive them and create a new feedstock with a new name.
@beckermr May I close this one?
We could document the new procedure if we wanted but otherwise yes, feel free to close.
We no longer rename feedstocks. Instead we archive them and create a new feedstock with a new name.
Great, then for the sake of conclusion of this issue: this section is outdated https://conda-forge.org/docs/orga/guidelines.html#renaming-packages and we should advertise that we no longer rename packages?
Yeah change the docs and add the new procedure.
@viniciusdc , Can I take this issue?
@pelson @viniciusdc, I have opened an issue to update the Renaming Packages/feedstocks section in the docs with the new process. So, may be we can close this issue now?